-
First-generation apple products are never a wise investment.
-
-
I agree with the author 90% - there is definitely a weird design paradox where recent designs are compromising UX for UI (or function for form, if you prefer). But I’d disagree with the author that all text should be black and backgrounds white - there’s a lot of room within the accessibility guidelines for a reason and we shouldn’t abandon typographic experimentation within a new medium. Web isn’t print, though there’s still a lot we can learn from it.
-
Experiment, sure! But at the end of the day, if you’re designing an app that needs to be used day in day out by people with all kinds of physical capabilities and challenges, have a care!
(For instance, if you’re Bob Web Developer, and you want to design the most rockin' hipster theme for Bob’s blog, then by all means, go to town with the feathery low contrast unreadable type, but if you’re GOOGLE and you’re redesigning GMail, used by bazillions of people, then maybe keep it readable? :)
-
Instead it’s the other way around; Bob does everything they can to make their blog accessible so as many people as possible will read it and still only gets 2 regular readers, while Google does whatever they want because people will (have to) use it anyway.
-
I think you may have missed my point - accessibility guidelines allow for a huge range of design experimentation and innovation (IE, stuff that is not feathery/low contrast). In no way, shape, or form am I advocating for low contrast experiments, especially from a player as large as google, especially on existing applications that aren’t broken.
I’m saying the author was being hyperbolic in the last paragraph when they plead with designers to ‘keep your type black’. There’s more than enough room within common accessibility guidelines to have colored type and still make it work for everyone, including the colorblind.
-
-
-
Could this be solved with a vcs like git? I have Working Copy on my iphone, git on my desktop and laptop, and can run portable git on other computers; any time I make a change, I could “git commit && git push”.
Slightly more cumbersome than auto-saving to dropbox, but a lot more resistant to messing up than other methods.
I don’t really think git’s conflict resolution will work that much better on the todo.txt format in particular, though it’s certainly a step up in safety.
Tangential to your point, butI believe dropbox actually uses a standard vcs under the hood. Last time I checked it was Mercurial, though that’s just scuttlebutt I’ve read around the web.