Examples for "Pitfalls and opportunities of single-page applications".
All examples are, on purpose, incomplete in various ways. For examples, loading hires images as thumbnails and on mobile is silly, but simplifies the setup enough to make it useful for demonstration purposes.
npm install to get dependencies.
node server.js or
./server.js to start development server.
npm install nodemon -g and run just
nodemon. In this case, you only have to restart manually when changing templates.
Open the displayed URL.
- Browserify, make node-style require available on the clientside
- Bones, with a focus on sharing Backbone code on client and server
- Joshfire Framework, with a focus on supporting every device with a screen
- Derby, with a focus on realtime collaborative applications
More on client+server rendering
- Yahoo announces their drinks-inspired frameworks - should be able to add Mojito to the frameworks list above sometime soon
- A Google+ engineer writes about the G+ architecture, there's still a lot to research and implement.
- Nodejs Rocket Turtle, by substack: http://substack.net/images/node_turtle.png
HTML5 history API
- Browser support for history API on caniuse.com
- Android ticket for regression on history API
- History API on iOS under 'popup security model', requires user interaction
- Interactive Browserscope user test for the history API
Client side error handling
Not yet covered by examples, but this blog post shows options for tracking those frontend errors.