Top 10 Web and HTML5 Predictions for 2013

2,303 views

Published on

Top 10 Web and HTML5 predictions for 2013

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

No Downloads
Views
Total views
2,303
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
65
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide

Top 10 Web and HTML5 Predictions for 2013

  1. 1. 2013, Web & HTML5 Jonathan Jeon hollobit@etri.re.kr 13 December 20121
  2. 2. 2
  3. 3. 3
  4. 4. Computing Paradigm Source: Mary Meeker, INTERNET TRENDS, 2012/12 4
  5. 5. Computing Paradigm Source: Mary Meeker, INTERNET TRENDS, 2012/12 5
  6. 6. Computing Platforms Source: Mary Meeker, INTERNET TRENDS, 2012/12 6
  7. 7. Computing Devices Source: Mary Meeker, INTERNET TRENDS, 2012/12 7
  8. 8. Computing Devices Source: Mary Meeker, INTERNET TRENDS, 2012/12 8
  9. 9. 2016, Mobile Market http://smarterplanet.co.kr/2012/11/06/mobile/ 9
  10. 10. Top 5 Form Factors, 2015 10
  11. 11. 2014Mobile will become the most common way of accessing the Internet 11
  12. 12. 12
  13. 13. Source: 김용균, 2013 IT 산업 10대 이슈, NIPA 13
  14. 14. 2012 vs. 2013 전망 Source: 김용균, 2013 IT 산업 10대 이슈, NIPA 14
  15. 15. 2013 Predictions, Gartner 15
  16. 16. 16
  17. 17. Hype Cycle for Consumer Services and MobileApplication, 2012 17
  18. 18. Hype Cycle for Application Development, 2012 18
  19. 19. 2013년 주요 IT 트랜드 서비스 환경의 사용자 편의성 다양성 증가 요구 증가 효율적 활용 요데이터 폭증 구 증가 단말/플랫폼/서비스 경쟁
  20. 20. 20
  21. 21. Top 10 Web Trends1. HTML5 enabled devices2. HTML5 is the Vanguard3. Plan 2014 & HTML 5.14. Specializing Web App5. Flooding of Web APIs6. Emerging Web OS7. Territorial expansion8. Response Web Design9. Policy & Plan10. Rethinking the Web Ecosystem 21
  22. 22. 1. HTML5 enabled devices Source:Gartner, Inc.,, Emerging Technology Analysis: Mobile Business Intelligence, 13 July 2011
  23. 23. Windows 8 & IE 10 ?? 23
  24. 24. 2. HTML5 is the Vanguard 24
  25. 25. Why HTML 25
  26. 26. Why HTML 26
  27. 27. HTML5 is … 27
  28. 28. 28
  29. 29. 3. Plan 2014 & HTML 5.1• Goal: How to get HTML5 to Rec in 2014? – http://dev.w3.org/html5/decision-policy/html5-2014-plan.html• Plan 2014 proposes how to get there: – Charter timeline revisions: • HTML 5.0 REC: 2014Q4 • Add HTML 5.1 for further feature development – Permissive CR exit criteria to focus testing – Modularity • Address remaining open issues via extension specs • Provide opportunity for extension specs to merge back 29
  30. 30. HTML Standardization WHAT‐WG 30
  31. 31. HTML milestone 2012 2013 2014 2015 2016 2017 2018 2019 2020 CR …CR,HTML5.0 REC … … start LC LC +HTML5.1 FPWD --- … CR REC CR LC +HTML5.x FPWD --- … CR REC CR LC +HTML6.x FPWD --- … CR REC CRFPWD:First Public Working Draft   LCWD: Last Call Working Draft PR: Proposed RecommendationWD: Working Draft CR : Candidate Recommendation REC: Recommendation
  32. 32. HTML 5.1• http://drafts.htmlwg.org/html/FPWD51/Overview.html 32
  33. 33. HTML.next• The mission of the HTML Working Group is to continue the evolution of HTML.• Media Source Extensions: allow JavaScript to generate media streams for playback• Encrypted Media Extensions: enable playback of protected content extend media element to allow decryption key acquisition• Canvas 2D Context additions – Ellipses, dashed lines – text on path, SVG matrix transforms
  34. 34. HTML.next - Proposed attributescapture (proposal) Provides a hint that by default, for an input element whose type element has the value file, the file-picker control should be placed in a particular media capturing mode; possible values are camera, camcorder, microphone, and filesystem.inert (proposal) A way to disable an entire subtree, without necessarily making the elements in that subtree appear disabled (e.g., the way that controls behind a modal dialog are “disabled” without appearing that way, in traditional UIs).inputmode (notes) Specifies what type of keyboard to use for a particular input or textarea element—for example, to switch to displaying a keyboard optimized for typing in numbers rather than letters, or for typing in URLs, or for auto-capitalizing; similar to the inputmode attribute from XHTML 1.1/Basic.download (proposal) Indicates that the author intends an a element to be used for downloading a resource. The attribute may have a value; the value, if any, specifies the default filename that the author recommends for use in labeling the resource in a local file system.ping (proposal) Enables hyperlink auditing: when used on an a element, gives the URLs of the resources that are interested in being notified if the user follows the hyperlink for that element. http://www.w3.org/html/wg/next/markup/
  35. 35. HTML.next - Proposed elementscontent (Web Components) “Represents an insertion point in a shadow DOM subtree. The insertion point is replaced with the elements’ children at rendering time. The <content> element itself is never rendered.”data (proposal) For marking up machine-readable data.datagrid (proposal) Represents an interactive/sortable representation of tree, list, or tabular data in the form of rows and cells. (Might be rendered in browsers as a column-sortable “spreadsheet view” and/or collapsible/expandable “tree view”). <datagrid> was previously part of the HTML draft, but was dropped in 2008.decorator (Web Components) “Defines a new decorator. Typically, you would also give it an id attribute to make it addressable from CSS.”element (Web Components) “Defines a new custom element.”intent (Web Intents) Represents an intent registration.menuitem (Mozilla proposal) Represents a command in a menu in a Web application.reco (Web Speech) Represents a speech-input (speech recognition) control in a user interface.shadow (Web Components) “Specifies an insertion point, where the next-oldest shadow DOM subtree in element’s list of shadow DOM subtrees is rendered. The <shadow> element itself is never rendered.”template (Web Components) “Defines an inert chunk of DOM that can then be used for creating DOM instances in an unknown parsing context.”tts (Web Speech) Represents an audio stream comprised of synthesized speech output (text to speech). DOM interface inherits from HTMLMediaElement (that is, the DOM interface for the HTML <audio> and <video elements). http://www.w3.org/html/wg/next/markup/
  36. 36. HTML5 Modularity• HTML Microdata - HTML WG • Web Intents - Web Apps WG /• HTML Canvas 2D Context - HTML Device APIs WG WG • Polyglot Markup: HTML-Compatible• HTML5 Web Messaging - Web XHTML Documents - HTML WG Apps WG • HTML5: Techniques for providing• Web Workers - Web Apps WG useful text alternatives - HTML WG• Web Storage - Web Apps WG • HTML Editing APIs - HTML Editing• The WebSocket API - Web Apps APIs CG WG • HTML Media Capture - Device APIs• The WebSocket Protocol - IETF HyBi WG WG • Media Capture and Streams - Device• Server-Sent Events - Web Apps APIs WG / WebRTC WG WG • Media Fragments URI - Media• WebRTC - WebRTC WG Fragments WG• WebVTT - W3C Web Media Text • Encrypted Media Extensions - HTML Tracks CG WG• HTML+RDFa - RDFa WG • Media Source Extensions - HTML WG• DOM Parsing and Serialization - Web Apps WG• Shadow DOM - Web Apps WG
  37. 37. 4. Specializing Web App Native App vs. Mobile Web 37
  38. 38. Native App vs. Web App• Why App ? – Better Performance – Better UI – H/W Capability – Offline – Developer Support – Monetization – Enhanced Install/Update 38
  39. 39. Native App vs. Web App• Counterattack (Native App) – AppStore, Auto update, – Developer Ecosystem• Obstruction (Mobile Web) – Performance, Offline – Device Capability, Monetization• Evolution (Mobile UX)• Chain Reaction – Evolution/Mutation of Web App • Native Web App, Hybrid Web App• Future … 39
  40. 40. Native App vs. Web App Native Native App Web App Hybrid Web App Web App Web page Multi-platform support 40
  41. 41. Specializing Web App• Web App Models Running  Service  Trust model Execution model Model Context Browser  Hosted Web  Untrusted  Browsing  based Web  App Web App Context App WRT based  Packaged Trusted  Native  (Native) (Installable)  Web App Context Web App Web App 41
  42. 42. Overcome the obstructions of web app• Performance – Engine enhance (Script, Rendering) – H/W Acceleration – Web OS• Offline – HTML5 offline feature (application cache, localStorage, online/offline events)• Device Capability – Device APIs – System Application APIs – Web APIs (Web Intents, Web Push…) – Web OS• Monetization – Web Application Store & Native Web App• Developer Environment – Developer Tools – Javascript Frameworks• UI – WebGL, Web Audio API – CSS4, DOM4 – Touch Events, GamePad API … 42
  43. 43. Security Model?• Some suggestions from John Lyle, Oxford University – Install before execute – Signed manifest – Restrictions on external sources and use of secure connections – Least privilege access control like native app platforms – Interoperable access control through policies or capability tokens – Hooks for monitoring system application activity – Restrictions on inline JavaScript and dangerous functions such as eval. – Isolation expectations, e.g. sandboxed storage & inter app communication – Application lifecycle – update, uninstall, revocation of privileges – Application provenance, e.g. app store certification – User interface guarantees, e.g. to limit clickjacking – Fingerprinting, linkability and privacy considerations Source: APIs for Trusted Web Applications ‐ Lyon 43
  44. 44. 5. Flooding of Web APIs Release Date Name Status 2012‐10‐25 Web MIDI API Working Draft• 50 APIs 2012‐10‐25 HTML to Platform Accessibility APIs Implementation Guide Working Draft 2012‐10‐25 File API Working Draft 2012‐10‐23 Server‐Sent Events Last Call 2012‐10‐18 Push API Working Draft 2012‐10‐04 Web Intents Addendum ‐ Local Services Working Draft – 225 specs 2012‐10‐04 Web Audio Processing: Use Cases and Requirements Working Draft 2012‐10‐04 Network Service Discovery Working Draft 2012‐09‐20 The WebSocket API CR 2012‐09‐13 Web Cryptography API Working Draft 2012‐08‐21 WebRTC 1.0: Real‐time Communication Between Browsers Working Draft• New WG 2012‐08‐02 2012‐08‐02 2012‐07‐26 2012‐07‐26 Web Audio API Ambient Light Events User Timing Performance Timeline Working Draft Working Draft CR CR – Pointer Event 2012‐07‐26 Page Visibility CR 2012‐07‐26 Navigation Timing CR 2012‐07‐12 Proximity Events Working Draft 2012‐07‐12 JSON‐LD API 1.0 Working Draft 2012‐07‐12 HTML Media Capture Last Call – Web NFC 2012‐07‐12 2012‐07‐12 2012‐07‐10 2012‐07‐03 Pick Media Intent Pick Contacts Intent WebDriver Working Draft Working Draft Working Draft Working Draft Quota Management API – System 2012‐06‐28 Selectors API Level 2 Working Draft 2012‐06‐28 Selectors API Level 1 Last Call 2012‐06‐28 Media Capture and Streams Working Draft 2012‐06‐26 Web Intents Working Draft Application 2012‐06‐14 Web Notifications Working Draft 2012‐05‐29 Pointer Lock Working Draft 2012‐05‐29 Gamepad Working Draft 2012‐05‐24 Input Method Editor API Working Draft – Web Crypto 2012‐05‐24 Indexed Database API Last Call 2012‐05‐22 The Screen Orientation API Working Draft 2012‐05‐22 Resource Timing CR 2012‐05‐10 Geolocation API Specification PR 2012‐05‐08 Vibration API CR – Web RTC 2012‐05‐08 2012‐05‐01 2012‐05‐01 Battery Status API Web Workers HTML5 Web Messaging CR CR CR 2012‐04‐19 Web IDL CR 2012‐04‐17 File API: Writer Working Draft 2012‐04‐17 File API: Directories and System Working Draft 2012‐02‐23 Clipboard API and events Working Draft 2012‐01‐17 XMLHttpRequest Level 2 Working Draft 44
  45. 45. Web (Platform) APIs http://www.w3.org/2012/05/mobile‐web‐app‐state/ 45
  46. 46. 6. Emerging WebOS Public Implementor Internal Stable draft Standard Test pecification Working s feedback Notes draft (Last Call) (Rec) Suite draft (CR) Execution & Q4 2012 Q2 2013 Q2 2013 Security Models Alarm Q1 2013 Q2 2013 Q2 2014Phase 1 Contacts Q1 2013 Q2 2013 Q2 2014 Messaging Q1 2013 Q2 2013 Q2 2014 Telephony Q1 2013 Q2 2013 Q2 2014 Raw Sockets Q1 2013 Q2 2013 Q2 2014 Bluetooth API Browser API Calendar API Device Capabilities APIPhase 2 Idle API Media Storage API Network Interface API Secure Elements API System Settings API 46
  47. 47. Why Emerging WebOS• New Paradigm (marketing)• Challenging• Device for Web Life• Cheaper OS• Rival horse• New Era of Web• Webbing the internet & world 47
  48. 48. Firefox OSFirefox OS is a HTML 5 web-based browser, which sits on top ofAndroid kernals, with all the features on handsets basically beingaccessed through a browser – similar to Googles Chrome OS. 48
  49. 49. 7. Territorial expansion Digital signage (recent Workshop hosted by NTT) Digital publishing Two Workshops: eBooks in February 2013, Q2 2013 Digital Marketing Q2 2013 Workshop Automotive 14-15 Nov Workshop hosted by Intel and sponsored by Webinos. Privacy 26-27 Nov Workshop hosted by UC Berkeley and TRUST Science and technology center. Television Q2 or Q3 2013 Workshop Source: Jeff Jaffe, “W3C Update*”, 2012 49
  50. 50. 8. Response Web• Fragmentation is a big problem 50
  51. 51. 8. Response Web• Fragmentation is a big problem 51
  52. 52. 8. Response Web• A flexible /fluid grid• Responsive images• Media queries 52
  53. 53. 8. Responsive Web• W3C Responsive Image Community Group• Picture Elements – http://picture.responsiveimages.org/ – http://bit.ly/Uyu05L (W3C)• Goals – Respond to different screen pixel width/height – Respond to different screen pixel densities – Respond to user zoom on image resource. – …. 53
  54. 54. 9. Policy & Plan 54
  55. 55. HTML5 Leader’s Camp• 국내 인터넷 이용환경 개선과 HTML5 활성화를 위한 전문가 위원회 구성/발족 – 위원장 : 방통위 박재문 네트워크정책국장 – 위원: ETRI, KISA, 삼성전자, LG전자, SKT, KTH, MS 등 – 활동목표: HTML5 활성화 협력 및 자문 (코디네이터 : ETRI 전종홍) – http://www.facebook.com/groups/html5kr/
  56. 56. HTML5 Leader’s Camp• http://www.facebook.com/groups/html5kr/• 1차 회의 (2012.1.30, 방통위) – 인터넷 이용환경 개선 추진 실적 및 ’12년 계획 발표 – HTML5 활성화 리더스 캠프 운영 방안, 전략 수립 방안 논의• 2차 회의 (2012.3.6 ~ 2012.3.7, 곤지암리조트) – 주요 기업별 HTML5 도입 및 활성화 계획 발표 및 토의 – 국내 웹 현황과 인터넷 이용환경 개선 방안 논의 – ’12년도 HTML5 활성화 및 향후 정책 방향 논의• 3차 회의 (2012.3.28, KISA) – 차기 플랫폼에서의 HTML5 지원 계획 사례 발표 : 타이젠, 윈도우8 등 – HTML5 활성화 대책 1차 초안 검토• 4차 회의 ~ 5차 회의 (다수 회의): HTML5 활성화 대책 작성/보완• 6차 회의 (2012.10.24, 강남) – 방통위 HTML5 활성화 대책 최종안 소개 – 인크로스 다빈치 스튜디오 소개• 7차 회의 (2012. 11.21, KISA 강남아카데미) – W3C TPAC 2012, Web Automotive Workshop 결과 소개 – jQeury ASIA 2012 conference 및 Webkit community 활동 방법 소개• 8차 회의 (2012.12.12, 강남역 TOZ) – 스마트 미디어와 HTML5 현황 – SK텔레콤의 WDK 소개 56
  57. 57. Lack of Web Expert• ICT 미충원 인원 비율 Source: 이경남, ICT 인력 고용 현황 및 시사점, 2012 57
  58. 58. Lack of Web Expert• ICT 인력 부족률 Source: 이경남, ICT 인력 고용 현황 및 시사점, 2012 58
  59. 59. 10. Rethinking the Web Ecosystem 59
  60. 60. 10. Rethinking the Web Ecosystem 60
  61. 61. 10. Rethinking the Web Ecosystem• Social media & network effect• Openness & Mashup (0.61M)• Humor, Easy, Offline, Language … 61
  62. 62. Other Top 10• HTML5 & Broadcasting/TV• Web based Signage• Web RTC API• Web Crypto API• Web NFC API• Web Intents• Web Push API• Web Driver API• ePub3 & ebook• Javascript & Framework, Tools 62
  63. 63. ConclusionsMobile First & Web Platform First1. HTML5 enabled devices2. HTML5 is the Vanguard3. Plan 2014 & HTML 5.14. Specializing Web App5. Flooding of Web APIs6. Emerging Web OS7. Territorial expansion8. Response Web Design9. Policy & Plan10. Rethinking the Web Ecosystem 63
  64. 64. Thank youFor more discussion : JongHong Jeon (hollobit@etri.re.kr) +82-42-860-5333Blog : http://mobile2.tistory.com/m http://twitter.com/hollobit OR 64

×