Fluent Conf 2013 Summary

Progressive Enhancement and History API on Twitter.

Transcript

1. Summary
5. Thanks!
6. Experiences along the time
7. What happened in 2010?
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)
20. JavaScript is the core technology
22. Optimizations available only on the Server
23. Multiples URLs
25. Multiples Requests
26. Bad page-load performance
28. Moving the rendering to the Server
29. No more #!
30. Just one URL
31. Load only what we need
33. Speed up navigation between pages
34. One view, two types of requests
35. Server
37. Client
38. History API
43. Hijax
44. Be like water
45. The End
46. Questions