1. HTML5 & the rise
of our mobile
overlords

2. Who Are You?

3. A FEW RANDOM
OBSERVATIONS

5. HTML5 Adoption

6. Chrome
version 14
October 4 th

7. Chrome
version 15
October 26th

8. Chrome
version 16
January 6 th

9. Chrome
version 17
February 17th

10. Chrome
version 18
March 28 th 2012

11. Chrome version 18 Last
Update
April 30th 2012

12. Gartner forecasts
phones overtaking
PCs as most
common web
browsing device
by 2013

16. HTML5 is not
future tech

20. Even when the
checkmark is
there,
performance
isn’t.

21. Designing for
devices is hard

22. Testing is critical

23. Native Apps
Pros Cons
• Easy to monetize • Costly to develop
• Fit user expectations • Restricted in delivery

24. Mobile Web Apps
Pros Cons
• More Flexible • Harder to monetize
• More Reusable • Hard to target
• Lack complete device
access.

25. No clear cut
winner

26. Demo
Expressive HTML

27. CSS Transitions

28. CSS Animation

29. Canvas

30. Video

31. JS Frameworks
that handle
these things

32. People want an
expressive web

34. We need the
medium to be
more expressive

35. We need our
work to work on
more devices

36. We need better
tools

37. WE WANT TO BE
EXPRESSIVE

38. Adobe Digital
Publishing

39. PDF
• Relatively small file
size
• Some flexibility
• Device issues

40. HTML
• Tiny file size
• Some flexibility
• Lack of layout control

41. PNG
• Huge file size
• Complete pixel level
control of layout

42. CSS PROPOSALS

43. CSS REGIONS

44. CSS EXCLUSIONS

45. Demo
CSS Regions and
Exclusions

46. CSS SHADERS

47. Demo
CSS Shaders

48. I am sick
and tired
of seeing
only 6-10
fonts
deemed
“web safe”

49. WANT
MANY
MORE

50. Tastefully
though
Those last few slides
were like font vomit

51. Webfonts
• Webfonts are a solution to this
– Require multiple formats
– Require proper licensing

52. TYPEKIT

53. DEMO
Typekit

54. WE WANT
TO BE
EVERYWH
ERE

55. If you haven’t
tested on the
device, then you
haven’t tested

56. SHADOW

58. Demo
Shadow

61. Why do we need
native?

62. That last one is an Accelerome

64. Access to
device
components and
OS API’s

66. Access to
App Stores

67. PHONEGAP

68. PhoneGap powers
native applications
using
HTML/JS/CSS

69. PhoneGap gives
access to
components and
API’s

70. PhoneGap Apps
can be
distributed in
stores

71. What do you
mean by “native”
apps

72. UI is not native

74. Demo
PhoneGap

75. Still not great

78. PHONEGAP BUILD

79. Demo
PhoneGap Build

80. WE NEED
BETTER TOOLS

84. EDGE

86. Demo
Edge

87. More tools are
coming

88. CONCLUSIONS

89. Html.adobe.com

90. Hiring

92. Adobe wants to
create tools that
allow you to be
expressive
anywhere.

93. Then we want to
sell those tools
to you.

94. Follow up?
• Preso will be up at
– http://slideshare.net/tpryan
• Feel free to contact me
– terry.ryan@adobe.com
– http://terrenceryan.com
– Twitter: @tpryan