Responsive Web Development

Designers already have all the neat tools for creating fast, interactive websites, so where is all the new stuff for developers? (For BarCamp Charleston on October 22, 2011)

Transcript

1. responsive web a fun morning/afternoon with Dirk Gadsden development
2. (IS DIRK GADSDEN) WHO?
3. human.
4. (esherido.com) web-based lifeform.
5. BORING HONORS STUDENT CLEMSON TIGER FRESHMAN BA IN COMPUTER SCIENCE college student.
6. (not very good, though) designer.
7. (pretty good at this*) * Give Fuzzco a call if you’re still not convinced. developer.
8. cofounder. (madelike.com)
9. (IS RESPONSIVE WEB DEVELOPMENT) WHAT?
10. A Brief History OF WEB DEVELOPMENT FIRST OFF,
11. and Tim Berners-Lee saw that they were good in the beginning, people made static HTML pages
12. but static pages were tedious to manage
13. and the people saw that this was quite a major improvement over boring static content so they came up with dynamic websites
14. but the people still weren’t happy
15. and they wanted interactivity and “rich media” whatever the hell that was nobody was really sure
16. and the people noticed the content took much longer to load and they had to deal with plugins and other incompatibilities but the developers did it anyway, and gave them “rich media”
17. but at least they didn’t have to read anymore
18. and they could only fully use a small portion of sites on their mobile devices
19. but they had YouTube and animated GIFs and they told themselves that’s all anbody ever really needs anyway
20. their bank websites were hard to use they were afraid of opening email but at least they had lolcats and Epic Meal Time they expected & accepted subpar user experience
21. OF THE INTERNET THIS COULD BE THE FUTURE
22. we have THE TECHNOLOGY
23. we have THE SKILLS
24. SO, DO WE PULL THIS OFF HOW?
25. IS THE ANSWER HTML5
26. IS ALREADY DOING IT
27. paper.madelike.com PAPER
28. delivering a user experience FASTER
29. load all necessary when loading the page DATA
30. use push to data in the background UPDATE
31. if the data changes on the then make it change in the as well SERVER BROWSER
32. isn’t just for games and gimmicks anymore PUSH
33. uses Pusher to deliver a user experience NO-WAIT
34. Pusher (pusher.com) lets us deliver push capability to almost every web browser under the sun.
35. CLIENT SERVER PUSHER CLIENT CLIENT
36. IN CONCLUSION
37. THE METHOD get all data on load, cache in memory deliver interface via JavaScript (using data in memory) update & retrieve data using APIs (added bonus is having a thirdy-party-ready API from the start) send updates to active clients via push (data updated in background, user never has to worry) store preferences & cache small data sets in local storage
38. the web doesn’t need to be slow
39. we can make it FAST
40. let’s get rid of WAITING
41. are you READY?
42. DIRK GADSDEN esherido.com @Esherido dirk@esherido.com madelike.com @getmadelike support@madelike.com THANKS! QUESTIONS?