Where the design community meets.
CEO / UX Designer at WHITEFUSION Joined about 4 years ago
Thanks all for the Raindrop.io recommendations...I've already gotten my Instapaper bookmarks imported in and it looks fantastic. I've been wanting something like this for a long time....definitely going to sign up for the PRO option.
Thanks Joel for your reply, and I'm glad to hear you're getting signups and good feedback. By personal data, I don't mean in a "security/privacy" scary sense, I just mean that, if I were to use Buckets to save sites instead of the combo of browser bookmarks and Instapaper which I currently use, I'd want to make sure I'm not going to lose all of that functionality and data in, say, a year. A free product is more likely to go under than a paid product (not that paid products don't go under either).
Case in point: Stache was a cool visual bookmarking tool that came out a few years ago. I used for a little while. Fast forward to late last year:
At the moment, I believe the apps still function, but who knows how long that will last.
Anyway, I'm glad to hear that you're considering a pro model. I'll definitely check Buckets out further once that happens. :)
This looks great! What I'm about to say please don't construe as any sort of criticism of your app per se. The problem for me is I've been burned so many times by web apps that go unsupported and then close down...at this point I'm essentially unwilling to put any personal data into an app that might not be around a while. If you were charging regular users and had an obvious business model, I might give it a shot figuring that as long as you're making money from users, it'll probably be around in one form or another. However, since it appears totally free, I'm just not going to risk it. Again, this isn't an issue with Buckets specifically...I would say this about any free tool that asks me to put tons of valuable personal data into it as part of its use case.
Yes, I do design sketches (wireframes & mockups) in Adobe Comp with 9.7" iPad Pro + Pencil. I think Comp is an amazing app, despite some of its strange limitations due to perhaps less than full blown resources at Adobe. It has quickly become a major part of my workflow.
I wrote a long response to this on a similar thread on HN, but the gist of it was: the meme that's now floating around that Apple doesn't care about professionals is only true if you define "professionals" as a very narrow class of users who have certain expectations regarding things like variety of connectivity options, extreme performance characteristics (like needing more than 16GB of RAM), whatever.
Meanwhile, there are plenty of professionals, like myself, who will continue to happily use MBPs to get their work done. I make a living using a MBP, and I do quite a few "pro" tasks on it: web design, programming, music production, video editing, etc. Nothing in this update suggests I'll have a problem doing any of those things -- on the contrary, everything I do will actually get much better. I think the Touch Bar is really a fantastic development, the best UI upgrade to the macOS experience in years. I look forward to using it in person.
When people think about remote work, they often default to the WFH concept. Some guy/gal sitting around in their pajamas in their bedroom working on their laptop when they aren't feeding their cat or playing video games.
Now I know quite a few people that WFH, however unlike that silly stereotype they have a real office room set up as a professional workspace, and it works great for them. For me, my house's floor plan coupled with the fact I have two small children makes that unpractical.
The next well-known "upgrade" from that idea is to work at a café/coffee shop. I don't really consider that an upgrade, in fact in some ways it's a downgrade. Don't get me wrong—I love working for an hour or two at a café some days. Always a good idea to get out and about and enjoy the freedom to work different places.
However, I really feel strongly that if you are a working professional and doing a lot or all of your work remotely, you need a real office. And if that office isn't at your house, then it needs to be somewhere else. And that's where cowork spaces come in. Some are set up with open floor plans so it's sort of like working at a café only (hopefully) quieter and more ergonomic. In my case, I rent a private office with a door that's located at a cowork space, and that works very well for me. I don't really care for open floor plans. I like my privacy while working and the ability to focus without distraction from anyone else. I also like the fact I can have other non-design/development-related gear like musical instruments or camera equipment or whatever else I want at hand that might be creative or otherwise.
So big, big thumbs up for cowork spaces/private offices. I really encourage every freelancer I meet to give it a serious consideration.
Interesting. Apparently I should be charging a lot more money for websites. :)
I think there needs to be some clarification here on the difference between a flat-file-based CMS like Kirby or Grav, and an actual static site generator like Jekyll, Middleman, Hugo, Hexo, etc. Craft CMS uses a database and so that's way-ay-ay different.
At this point, I only choose to use a static site generator (in my case, Jekyll) for building sites. I am convinced of the merits of a workflow where your source files are in a Git repo, you can kick-off a simple build phase, and the result is a set of output files (HTML, CSS, JS, images, etc.) that can be served directly by a CDN.
Not only do you have very little cost involved, but you also have maximum flexibility in terms of backup and content longevity. Your source files will last for decades, and your output files will work anywhere in any browser long into the future (just like you can today open an HTML file made in the early 90's and it'll still load just fine).
You don't need to set up a database anywhere, you don't need to manage a complex development environment (in the case of local Jekyll development, installing Ruby + Jekyll is pretty darn simple).
I use Netlify for my site hosting, so it takes care of the Jekyll build "in the cloud" and works with any sort of custom plugin or gem (Ruby package) I might want, and deploys to a CDN in seconds. I just make a change to a text file in my Git repo, commit and push, and only a minute or so later, my site is built and updated world-wide. I can even use Git2Go on my iPad or iPhone along with a text editor like Ulysses or Textastic -- don't need a full-blown Mac or PC to edit my site! I love it.
A for effort, but I really don't care for the scroll effect. I don't like sites that hijack the scrollbar. Parallax-y stuff is fine, but I expect a scroll to be smooth and continuous.
Looking great. I'm a big fan of San Francisco on iOS/macOS and like seeing more web sites/apps allow its use.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.