Your SlideShare is downloading. ×
WebDU Keynote
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

WebDU Keynote

1,142

Published on

Published in: Technology, Design
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,142
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Things to have running:Chrome – TypekitChrome – PhoneGap BuildChrome – Compass demoChrome - http://bartaz.github.com/impress.js/#/boredChromiumEdgeMiniBrowser
  • Designer?Developer?Both?jQuery?jQuery Mobile?PhoneGap?TypeKit?Adobe Edge?
  • Transcript

    • 1. HTML5 & the riseof our mobileoverlords
    • 2. Who Are You?
    • 3. A FEW RANDOMOBSERVATIONS
    • 4. HTML5 Adoption
    • 5. Chromeversion 14 October 4 th
    • 6. Chromeversion 15 October 26th
    • 7. Chromeversion 16 January 6 th
    • 8. Chromeversion 17 February 17th
    • 9. Chromeversion 18 March 28 th 2012
    • 10. Chrome version 18 LastUpdate April 30th 2012
    • 11. Gartner forecastsphones overtaking PCs as most common web browsing device by 2013
    • 12. HTML5 is not future tech
    • 13. Even when the checkmark is there, performance isn’t.
    • 14. Designing fordevices is hard
    • 15. Testing is critical
    • 16. Native AppsPros Cons• Easy to monetize • Costly to develop• Fit user expectations • Restricted in delivery
    • 17. Mobile Web AppsPros Cons• More Flexible • Harder to monetize• More Reusable • Hard to target • Lack complete device access.
    • 18. No clear cut winner
    • 19. Demo Expressive HTML
    • 20. CSS Transitions
    • 21. CSS Animation
    • 22. Canvas
    • 23. Video
    • 24. JS Frameworks that handle these things
    • 25. People want anexpressive web
    • 26. We need the medium to bemore expressive
    • 27. We need ourwork to work on more devices
    • 28. We need better tools
    • 29. WE WANT TO BEEXPRESSIVE
    • 30. Adobe DigitalPublishing
    • 31. PDF• Relatively small file size• Some flexibility• Device issues
    • 32. HTML• Tiny file size• Some flexibility• Lack of layout control
    • 33. PNG• Huge file size• Complete pixel level control of layout
    • 34. CSS PROPOSALS
    • 35. CSS REGIONS
    • 36. CSS EXCLUSIONS
    • 37. Demo CSS Regions and Exclusions
    • 38. CSS SHADERS
    • 39. Demo CSS Shaders
    • 40. I am sickand tiredof seeingonly 6-10fontsdeemed“web safe”
    • 41. WANTMANYMORE
    • 42. Tastefully thoughThose last few slides were like font vomit
    • 43. Webfonts• Webfonts are a solution to this – Require multiple formats – Require proper licensing
    • 44. TYPEKIT
    • 45. DEMO Typekit
    • 46. WE WANTTO BEEVERYWHERE
    • 47. If you haven’t tested on thedevice, then you haven’t tested
    • 48. SHADOW
    • 49. Demo Shadow
    • 50. Why do we need native?
    • 51. That last one is an Accelerome
    • 52. Access to devicecomponents and OS API’s
    • 53. Access toApp Stores
    • 54. PHONEGAP
    • 55. PhoneGap powersnative applications using HTML/JS/CSS
    • 56. PhoneGap gives access tocomponents and API’s
    • 57. PhoneGap Apps can be distributed in stores
    • 58. What do youmean by “native” apps
    • 59. UI is not native
    • 60. Demo PhoneGap
    • 61. Still not great
    • 62. PHONEGAP BUILD
    • 63. Demo PhoneGap Build
    • 64. WE NEEDBETTER TOOLS
    • 65. EDGE
    • 66. Demo Edge
    • 67. More tools are coming
    • 68. CONCLUSIONS
    • 69. Html.adobe.com
    • 70. Hiring
    • 71. Adobe wants tocreate tools thatallow you to be expressive anywhere.
    • 72. Then we want to sell those tools to you.
    • 73. 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

    ×