Fluent Conf 2013 Summary

Fluent Conf 2013 Summary

Progressive Enhancement and History API on Twitter.

F8a70e01eddbadc5e4f9876ff34494fa?s=128

Guille Paz

July 27, 2013
Tweet

Transcript

  1. Summary

  2. None
  3. None
  4. None
  5. Thanks!

  6. Experiences along the time

  7. What happened in 2010?

  8. None
  9. None
  10. CORE functionality

  11. User should be able to navigate between section of the

    site
  12. Navigation between sections should be fast

  13. URLs should be accessible regardless of the client’s abilities

  14. Make page navigation easier and faster

  15. Render runs on Server and Client

  16. Routing model on the Client (mustache)

  17. Strong relationship between a URL and its content

  18. #Hash Navigation (hashbang)

  19. None
  20. JavaScript is the core technology

  21. 2011

  22. Optimizations available only on the Server

  23. Multiples URLs

  24. None
  25. Multiples Requests

  26. Bad page-load performance

  27. 2012

  28. Moving the rendering to the Server

  29. No more #!

  30. Just one URL

  31. Load only what we need

  32. 2013

  33. Speed up navigation between pages

  34. One view, two types of requests

  35. Server

  36. None
  37. Client

  38. History API

  39. None
  40. None
  41. None
  42. None
  43. Hijax

  44. Be like water

  45. The End

  46. Questions