Futuristic Progressive Enhancement

The web has changed beyond recognition since progressive enhancement was first presented in 2003. The rise of app culture, the explosion of web-enabled devices and a steady stream of new browser features might tempt us into abandoning it as a dated approach.

But it is because of these changes that it is more important than ever to employ progressive enhancement – it's just that our methods and tools need an update.

PDF version with notes: http://dl.dropbox.com/u/6983841/futuristic-progressive-enhancement.pdf

Transcript

1. F r Progressive Enhancement J N wb r @froots101
2. VIM
12. Classical progressive enhancement 2003
13. “T v ”
14. Content
15. presentation
16. Client-side scripting
17. Separation f r
18. Fault tolerance
20. Accessibility
21. Things have
22. Addressability
23. #!Whoops.
24. Squawk?
26. N w ! Responsibility!
27. Rock’n’Roll? or S ffl ?
28. Devices & Browsers
29. Internet Explorer Mozilla / Firebird Netscape Opera 0.6 1.5 2.2 94.4 Br w r 2003 Wikipedia.org
30. Internet Explorer Mozilla / Firebird Netscape Opera 0.6 1.5 2.2 94.4 Br w r 2003 Wikipedia.org 608 million web users www.internetworldstats.com
31. Internet Explorer Chrome Firefox Safari Desktop Opera Mobile Safari Mobile Opera Desktop Android 1.6 1.8 1.8 2.0 5.6 23.2 25.1 35.5 Br w r 2012 statcounter.com, December 2011
32. Internet Explorer Chrome Firefox Safari Desktop Opera Mobile Safari Mobile Opera Desktop Android 1.6 1.8 1.8 2.0 5.6 23.2 25.1 35.5 Br w r 2012 statcounter.com, December 2011 2.2 billion web users www.internetworldstats.com
33. Internet Explorer Chrome Firefox Safari Desktop Opera Mobile Safari Mobile Opera Desktop Android 1.6 1.8 1.8 2.0 5.6 23.2 25.1 35.5 Br w r 2012 statcounter.com, December 2011 1.2 billion b web users www.itu.int
34. Br w r Support SUPPORT TIME
35. Basic E
36. Gr Browser Support
38. binary binary S pp r
40. “There is no WebKit on mobile” — P r-P K
41. Bugs p Bugs
42. Not a level playing field
43. Feature detection
44. Client side Server side has.js
45. Polyfills
46. html5please.us
47. “Graded F r Support” – P Ir & D v M
48. OMG CSS OMG JS Nice CSS Nice JS Base CSS Base JS HTML HTML Progressive Enhancement 2.0 N Z
49. TOUCH JS No touch js TOUCH CSS No touch CSS Base JS Base JS Base CSS Base CSS HTML HTML Another possibility? F r enhancements
51. B pragmatic dogmatic
53. . J N wb r @froots101 tinnedfruit.com
54. http://www.flickr.com/photos/mager/2659619029/ http://www.flickr.com/photos/elsie/5966090679/ http://www.flickr.com/photos/donpezzano/3257999898/ http://www.flickr.com/photos/schnaars/3978316556/ http://www.flickr.com/photos/aussiegall/407522186/ http://www.dispatchwork.info/bocchignano/ http://www.flickr.com/photos/like_the_grand_canyon/2477020118/ http://www.flickr.com/photos/nathaninsandiego/5966706801/ https://twitter.com/#!/lindseybieda http://www.panoramio.com/photo/30914547 http://www.flickr.com/photos/marcelgermain/2189516138/ http://www.flickr.com/photos/kevinkrejci/98156233/ http://www.flickr.com/photos/carlc/3846080374/ Image credits