In the beginning, progressive enhancement was simple: HTML layered with CSS layered with JavaScript. That worked fine when there were two browsers, but in today's world of multiple devices and ...
In the beginning, progressive enhancement was simple: HTML layered with CSS layered with JavaScript. That worked fine when there were two browsers, but in today's world of multiple devices and multiple browsers, it's time for a progressive enhancement reboot. At the core is the understanding that the web is not print - the same rules don't apply. As developers and consumers we've been fooled into thinking about print paradigms for too long. In this talk, you'll learn just how different the web is and how the evolution of progressive enhancement can lead to better user experiences as well as happier developers and users.
This deck is a conference-agnostic one, suitable to be shown anywhere without site-specific jokes!
"Anyone who slaps a this page is bestviewed with Browser X label on a Webpage appears to be yearning for the badold days, before the Web, when you hadvery little chance of reading a documentwritten on another computer, anotherword processor, or another network." Tim Berners-Lee, 1996
"An escalator can never break; it can only become stairs." Mitch Hedberg, Comedian http://www.flickr.com/photos/midiman/336647596/ http://www.flickr.com/photos/midiman/336647596/
BehaviorPresentation Content
JavaScript CSS HTML
A-GradeJavaScript CSS HTML
C-Grade HTML
Progressive Enhancement 1.0
Were having some problems
Development takes too long http://www.flickr.com/photos/athomeinscottsdale/4507847940/
Too many bugs http://www.flickr.com/photos/kaibara/4632384645/
http://www.flickr.com/photos/drb62/4990651560/ Our pages are slow
Why?
We got confused
Web page : ?
Web sites look like print
Web page : Printed page
1) WEB PAGE : PRINTED PAGE :: (a) dairy : diary (b) spider : author (c) web browser : book (d) digital photo : print photo (e) cell phone: text message
http://www.flickr.com/photos/chrisschroeder/4096627359/ Every printed book is exactly the same
We became obsessed with identical experiences across all browsers http://www.flickr.com/photos/joanna8555/5554285729/
http://www.flickr.com/photos/denisdervisevic/5327974794/ People got angry if you suggested otherwise
Quality?
Professional?
Consistency?
Unity of messaging combinedwith brand identification while setting user expectations appropriately?
1) WEB PAGE : PRINTED PAGE :: (a) dairy : diary (b) spider : author N (c) web browser : book G R O (d) digital photo : print photo (e) cell phone: text message W
http://www.flickr.com/photos/ramdac/377087239/
We started the analogy in the wrong spot
Web page : ?
N GWeb page : Printed page R O W
Web browser : Web page
1) WEB BROWSER : WEB PAGE :: (a) telephone : call (b) computer : email (c) printed book : printed page (d) television : television show (e) mailbox : letter
Old browsers are like black & white TVs http://www.flickr.com/photos/stevestein1982/4047834684/
New browsers are like HD TVs http://www.flickr.com/photos/lge/3988988400/
TV already solved this problemhttp://www.flickr.com/photos/navdeepraj/504596529/
This would be silly Yet this is what web developers have been doinghttp://www.flickr.com/photos/navdeepraj/504596529/
Do web sites need to look exactly the same in every browser?
1) WEB BROWSER : WEB PAGE :: (a) telephone : call (b) computer : email (c) printed book : printed page (d) television : television show (e) mailbox : letter
Progressive Enhancement 1.0 JavaScript CSS HTML
Progressive Enhancement 2.0 OMG CSS OMG JS Nice CSS Nice JS Base CSS Base JS HTML
1–4 of 4 previous next Post a comment