What lies ahead of HTML5_Ooop Munich 2013_Krzysztof Szafranek

3,232 views

Published on

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,232
On SlideShare
0
From Embeds
0
Number of Embeds
2,083
Actions
Shares
0
Downloads
14
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

What lies ahead of HTML5_Ooop Munich 2013_Krzysztof Szafranek

  1. 1. What Lies Ahead for HTML5?Krzysztof Szafranek @szafranekWooga GmbH
  2. 2. [ˈkʂɨʂtɔf ʂafranˈɛk] Web application & game developer Wooga (Roche, Nokia)Let me start with the most technically difficult part of the presentation.
  3. 3. How many of you would consider yourself developers?How many of you have used HTML5?
  4. 4. I think the biggest mistake that we made, as a company, is betting too much on HTML5 as opposed to native... because it just wasnt there.Last year’s quote that caused a lot of confusion
  5. 5. The language < >
  6. 6. Next iteration of the HTML languageMarkup language for structuring and presenting content for the World Wide Web.
  7. 7. <video><audio>
  8. 8. <canvas>
  9. 9. New form elements <input type=date><input type=color>How many of you have implemented a date picker?Less code to improve site’s usabilityFaster site
  10. 10. The buzzword[5]
  11. 11. 3DWebGLDemo: 3D race car
  12. 12. Mediavideo, audioScreenshot: mobile YouTube
  13. 13. OfflineScreenshot: Twitter mobile
  14. 14. CSS3
  15. 15. NetworkWebSockets, server-sent events, XHR2Screenshot: Facebook chat
  16. 16. DevicesMicrophone, cameraDemo: speech recognition
  17. 17. HTML5 has already wonIf you have a website built in the last 3 years, most likely you’ve been using HTML5 already.
  18. 18. http://html5awesome.com/
  19. 19. mobile[15]Mobile doesn’t necessarily mean phone!
  20. 20. Black Friday 30 2012 22.5 15 7.5 16.26 9.84 2011 2012 0 % of sales done through mobileSource: http://www-01.ibm.com/software/marketing-solutions/benchmark-reports/benchmark-2012-black-friday.pdf
  21. 21. Black Friday 30 201222.5 15 24.04 7.5 14.33 2011 2012 0 % of traffic coming from mobile
  22. 22. I think the biggestmistake that wemade, as a company,is betting too muchon HTML5 asopposed to native...because it justwasnt there.
  23. 23. ... we actually have morepeople on a daily basisusing mobile WebFacebook than we haveusing our iOS or Androidapps combined.So mobile Web is a bigthing for us.
  24. 24. Web or native?
  25. 25. Native
  26. 26. Native
  27. 27. Native Performance
  28. 28. Native
  29. 29. Native
  30. 30. Native Access to device features
  31. 31. Native
  32. 32. Native
  33. 33. Native Distribution through an app store
  34. 34. Native
  35. 35. Native
  36. 36. Native Payments
  37. 37. Native
  38. 38. Opportunity cost
  39. 39. m.guardian.co.uk Amazon HTC LG Sony RIM Apple Samsung Nokia 3.3m daily page viewsApple 80%Samsung 8%RIM 6%HTC 5%Nokia 1%http://www.guardian.co.uk/info/developer-blog/2012/dec/11/fragmented-world-mobile-traffic-data
  40. 40. DiscoverabilityDiscoverability in the AppStore,over 700 000 apps.
  41. 41. Development cost1.3 million Android devices is being activated every single day.Source: http://techcrunch.com/2012/09/05/eric-schmidt-there-are-now-1-3-million-android-device-activations-per-day/
  42. 42. Web
  43. 43. Web
  44. 44. WebYou already have it
  45. 45. Web
  46. 46. Web
  47. 47. WebCheaper to build
  48. 48. Web
  49. 49. WebOpen standards not controlled by one company
  50. 50. Web VendorindependenceOpen standards not controlled by one company
  51. 51. WebOpen standards not controlled by one company
  52. 52. Web
  53. 53. WebEasy updates
  54. 54. Web
  55. 55. Web
  56. 56. WebFuture proof
  57. 57. Web
  58. 58. Discoverability
  59. 59. Payments
  60. 60. “Standards”
  61. 61. Hybrid
  62. 62. Hybrid Native HTML5wrapper inside
  63. 63. Hybrid
  64. 64. Hybrid
  65. 65. Hybrid Access to App store devicedistribution features
  66. 66. Hybrid
  67. 67. Hybrid
  68. 68. Hybrid Cross Notplatform native!
  69. 69. Hybrid
  70. 70. The story of[30]
  71. 71. Hybrid: HTML5+PhoneGapOver 20x less than my current game in Objective C
  72. 72. Hybrid: HTML5+PhoneGap 22k lines of JSOver 20x less than my current game in Objective C
  73. 73. AppStore, worldwideReleased as opensource
  74. 74. github.com/wooga/Pocket-Island
  75. 75. JavaScript!
  76. 76. JavaScript!•Development speed
  77. 77. JavaScript!•Development speed•Developer talent
  78. 78. JavaScript!•Development speed•Developer talent•Community
  79. 79. “Write once,run everywhere”
  80. 80. “Run everywhere” – either a lie or programs that worked equally badly everywhere
  81. 81. Sound, multitouch...Sounds has been fixed in Safari 6, multitouch is being standardized right now.
  82. 82. Performance12 FPS instead of 60
  83. 83. ConclusionsThe web wasn’t the best platform for making mobile games in 2012.[40]
  84. 84. “Every new generation brings radical new features, and the Web will always be behind on those. So the cutting edge is native.” Ian Hickson, editor of the HTML specDo you really need the cutting edge?Are you willing to pay for it?
  85. 85. Games
  86. 86. Games
  87. 87. Games
  88. 88. Games
  89. 89. Games
  90. 90. Operating system!
  91. 91. WebAPI WebSMS WebTelephony Power Management Device Storage WebPayment Camera Calendar WebBluetooth Vibration API ...https://wiki.mozilla.org/WebAPI
  92. 92. 10 years from nowIn many ways mobile web is where the desktop web was 15 years ago.But it is catching up.
  93. 93. 10 years from now The web & HTML: still around.In many ways mobile web is where the desktop web was 15 years ago.But it is catching up.
  94. 94. 10 years from now App stores: not so sure.In many ways mobile web is where the desktop web was 15 years ago.But it is catching up.
  95. 95. 10 years from nowIn many ways mobile web is where the desktop web was 15 years ago.But it is catching up.
  96. 96. Thank you!www.szafranek.net wooga.com/jobs@szafranek
  97. 97. Photo credits: Crunchies2009 John Kannenberg luisvilla

×