4 ms·
> Either make your web apps fallback to HTML + CSS So make two Web apps with the same functionality, basically?
by emodendroket 12y ago
> Either make your web apps fallback to HTML + CSS
So make two Web apps with the same functionality, basically?
- insin 12y agoOr make one app with an isomorphic base which gets progressively enhanced when JavaScript runs on the client.
- emodendroket 12y agoYes, but if you're doing a true "SPA" then "progressive enhancement" really does just mean having two versions of everything.
- insin 12y agoNot any more - once you can prerender the "SPA" on the server and use the same codebase to rehydrate it on the client and take over - which you can do today with React and soon with Ember - then with the right setup the "progressive enhancement" bit can be "am I on the client now? let's do some extra stuff" implemented as part of the same component. e.g. here's a form that uses the same React component to render on the server, to handle regular form submissions and render redisplay when invalid and to progressively enhance with live validation and ajax form submission when JavaScript is available on the client: https://isomorphic-lab.herokuapp.com/add-thing https://isomorphic-lab.herokuapp.com/add-thing
- thomasfoster96 12y agoI'm Sure a lot of single page app features have a simple fallback - things like tabs, sliders, carousels and most navigation can be done with just html + css.