HTML
<canvas>
<video>
<datalist>
<audio>
<picture>
Slide 30
HTML 5 document conformance requirements
should be designed so that web content can
degrade gracefully in older or less capable user
agents, even when making use of new elements,
attributes, APIs and content models.”
“
—HTML Design Principles
Slide 31
principles.adactio.com
Slide 32
principles
goals
patterns
Slide 33
HTML
<canvas>
<video>
<datalist>
<audio>
<picture>
Slide 34
How well does it work?
Slide 35
How well does it fail?
Slide 36
Slide 37
Slide 38
Slide 39
service workers
Slide 40
Slide 41
How well does it work?
Slide 42
Slide 43
How well does it fail?
Slide 44
web components
shadow DOM
custom elements
Slide 45
HTML
<canvas>
<video>
<datalist>
<audio>
<picture>
ajax
responsive web design
progressive web app
the extensible web
Slide 55
service worker
manifest file
progressive web app
HTTPS
+
+
Slide 56
Slide 57
Slide 58
Slide 59
Who benefits?
Slide 60
developers
users
Slide 61
sass
less
git
gulp
npm
jQuery
bootstrap
angular
react
ember
Slide 62
What are the assumptions?
Slide 63
So
!
ware, like all technologies, is inherently
political. Code ine
v
itably reflects the choices,
biases and desires of its creators.”
“
—Jamais Cascio
Slide 64
Slide 65
$
e street finds its own uses for things.”
“
—William Gibson
Burning Chrome
Slide 66
Slide 67
Technolog y is neither good nor bad;
nor is it neutral.”
“
—Melvin Kranzberg
Slide 68
Slide 69
Slide 70
What Technolog y Wants
e Inevitable
Slide 71
amish
$
e Amish have the undeserved
reputation of being luddites, of people
who refuse to employ new technolog y.
$
e Amish are steadily adopting
technolog y — at their pace.
$
ey are slow geeks.”
“
—Kevin Kelly
-ish
Slide 72
Slide 73
How well does it work?
How well does it fail?
Who benefits?
What are the assumptions?