The whole idea of progressive enhancement is using the power that the web platform gives us for free — specifically, HTML, CSS and JavaScript — to provide a baseline experience for the people who visit our sites and/or apps, and then build on that where appropriate and necessary, depending on the capabilities of the technology that they are using.
These capabilities can and do vary hugely
https://andy-bell.co.uk/how-a-minimum-viable-experience-produces-a-resilient-inclusive-end-product/
@andy great piece. Also an approach that scales. At work we’re building a Python/Flask SaaS app for clients with a progressive enhancement mindset. We’ve found that the server-side rendered, minimum viable experience is actually more than enough for a lot of the features we’ve designed so far; it’s resilient, responsive, and blazing fast. No need to add any JS overhead - yet - but if that point ever comes, we know it’s to *enhance* rather than require
@ravi that’s bloody great to hear