FOWA2013: The rise of single page applications

7,801 views

Published on

In the last couple of years we have seen an explosion of single-page applications beyond the traditional complex applications, making its way into the mainstream and the consequent appearance of frameworks to facilitate the creation of these apps. In this session we will cover the motivations and implications of creating single-page apps, as well as the current state of the industry, the trends that are starting to arise in the field and the role of nodejs to facilitate the initial render process on the server side before handing over the control to the browser, as a way to speed up the initial rendering on mobile devices.

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
7,801
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

FOWA2013: The rise of single page applications

  1. 1. #FOWA
  2. 2. Caridy Patiño Principal Frontend Engineer at Yahoo! caridy@yahoo-inc.com @caridy
  3. 3. The Time Machine (2002)
  4. 4. Safety Not Guaranteed (2012)
  5. 5. The rise of single-page applications
  6. 6. http://www.flickr.com/photos/roddh/7998107606/
  7. 7. http://www.flickr.com/photos/diverkeith/379540273/
  8. 8. from web applications to single-page applications
  9. 9. evolution of web applications
  10. 10. urls
  11. 11. url fragments
  12. 12. websites
  13. 13. ajax
  14. 14. complex apps became popular
  15. 15. our amazing big brains http://www.flickr.com/photos/pennstatelive/8972110324/
  16. 16. http://www.flickr.com/photos/indigotimbre/66258903/
  17. 17. back/forward buttons were patched using fragments to improve usability
  18. 18. the broken web was eventually fixed
  19. 19. performance
  20. 20. we hack things to avoid disrupting the workflow with a full page reload to fulfill an action as a consequence of a user interaction
  21. 21. single-page applications
  22. 22. support for multiple states to react to user interaction
  23. 23. users can switch between different states in no time
  24. 24. ... and doing so without breaking any of the core features of the web (history, url, openness)
  25. 25. building single-page applications today
  26. 26. Rendr AngularJS Backbone EmberJS Meteor DerbyJS YAF React Mojito
  27. 27. support a chain of user interactions to fulfill an operation without a full page refresh
  28. 28. patterns
  29. 29. MV* for the win
  30. 30. url driven web applications
  31. 31. conventions over configurations
  32. 32. libraries over frameworks
  33. 33. UI data bindings
  34. 34. the /#!/ugly/ url is fading out
  35. 35. initial rendering on the server
  36. 36. nodejs as the server runtime
  37. 37. server produces the initial state of the application, then passing the control to the browser to continue function as a single page application
  38. 38. progressive enhancement, graceful degradation, and performance as a feature
  39. 39. performance as a way to enhance user experience
  40. 40. only seconds of our users’ attention
  41. 41. modown is a set of libraries and components to power single page applications
  42. 42. modown is coming soon!
  43. 43. npmjs.org/search?q=modown github.com/yui/ github.com/yahoo/
  44. 44. Thanks @caridy

×