The end of responsive images - Piccalilli
Hallelujah! Support for sizes="auto" is finally landing in Firefox and Safari! Praise be!
Building a Progressively-Enhanced Site | Jim Nielsen’s Blog
This is an excellent case study!
The technical details are there if you want them, but far more important is consideration that went into every interaction. Every technical decision has a well thought out justification.
Related links
Software can be finished - Ross Wintle
There’s quite a crossover between resilience and longevity:
- Understand the requirements
- Keep scope small and fixed
- Reduce dependencies
- Produce static output
- Increase Quality Assurance
Optimizing PWAs For Different Display Modes — Smashing Magazine
There’s really good browser support for display-mode media queries and this article does a really good job of running through some of the use cases for your progressive web app.
A pragmatic browser support strategy | Go Make Things
- Basic functionality should work on any device that can access the web.
- Extras and flourishes are treated as progressive enhancements for modern devices.
- The UI can look different and even clunky on older devices and browsers, as long as it doesn’t break rule #1.
Progressive enhancement brings everyone in - The History of the Web
This is a great history of the idea of progressive enhancement:
It is an idea that has been lasting and enduring for two decades, and will continue.
Related posts
Browser support
Here’s Clearleft’s approach to browser support. You can use it too (it’s CC-licensed).
Speculation rules
A performance boost in Chrome.
Baseline progressive enhancement
If a browser feature can be used as a progressive enhancement, you don’t have to wait for all browsers to support it.
Overloading buttons
Can you have too much semantics?
Of the web
Baldur Bjarnason has written my mind.