
This is an excellent discussion of designing from the content out on a real project. Tons of sage advice in here.
This is an excellent discussion of designing from the content out on a real project. Tons of sage advice in here.
Jeremy Keith’s latest book. Free to read on any device you own. Installable as a progressive web app too (naturally).
The Nook returns with stock Android to compete with Amazon’s closed Fire ecosystem.
Ever wonder if websites can track your every move?
Privacy matters.
This is a nice overview (in French) of how Hopwork handles progressive enhancement in their SaaS product. Their back-end is Java too. It’s nice to see folks talking about how to progressively enhance products in that language; we don’t hear about that often enough.
A nice overview (in Dutch) of why you should combine progressive enhancement with RWD.
This is an excellent summary of print style recommendations from Manuel Matuzovic. I’m glad I wrote the tweet that prompted it :-)
See also:
As usual, Jason Grigsby nails it:
Done and done.
This is an excellent post about progressive enhancement from the “technical credit” (as opposed to “technical debt”) point of view.
This is an excellent missive from Nicholas covering the progressive enhancement debate.
First … progressive enhancement isn’t about having a JavaScript vs. JavaScript-disabled experience, it’s about providing the best possible user experience throughout the entire lifecycle of the web application. …
Second, progressive enhancement isn’t a strict prescription, it’s a way of thinking about the software you’re building. … Instead, it encourages you to think more deeply about the problem you’re trying to solve, and guides you towards solutions that work for the maximum number of users.
These two points are why I believe progressive enhancement is as relevant today as it has ever been. The only difference now is that we have more options for improving the user experience than ever before.
I couldn’t have said it better myself.