HTML5: No Threat to Native App Dominance

he question for many is not if but when HTML5 will replace native apps. This report (the second of three in a series) finds that HTML5 apps are not the future. Facing business, technical, and revenue challenges HTML5 apps will never gain mainstream popularity. However, a third type of app might bridge HTML5 and native apps in an effective way to keep the app ecosystem engine revved while increasing developer support across platforms.

1 Executive Summary
2 What is HTML5?
3 HTML5 - What it can and cannot do
3.1 Capabilities in summary
4 Company Strategies
4.1 Google Profile
4.2 Apple Profile
4.3 Microsoft Profile
4.4 Facebook Profile
4.5 Mozilla
4.6 Adobe
5 The business case against pure HTML5 stores and apps
6 HTML5 and ringmark
7 Making HTML5 and Native live together
7.1 Adobe/PhoneGap
7.1.1 What is PhoneGap?
7.1.2 Background (from the company)
7.1.3 Investors
7.1.4 Native API Support
7.1.5 Supported Platforms
7.1.6 Apps built using PhoneGap
7.1.7 The future
7.2 Sencha
7.2.1 What is Sencha?
7.2.2 Background
7.2.3 Investors
7.2.4 Native API Support
7.2.5 Supported Platforms
7.2.6 Apps built using Sencha
7.2.7 The future
7.3 Marmalade
7.3.1 What is Marmalade?
7.3.2 Background (from the company)
7.3.3 Investors
7.3.4 Native API Support
7.3.5 Supported Platforms
7.3.6 Apps built using Marmalade
7.3.7 The future
7.4 Appcelerator
7.4.1 What is Appcelerator?
7.4.2 Background (from the company)
7.4.3 Investors
7.4.4 Basic functionality
7.4.5 Native API Support
7.4.6 Supported Platforms
7.4.7 Apps built using Appcelerator
7.5 Brightcove
7.5.1 What is Brightcove's solution?
7.5.2 Background (from the company)
7.5.3 Investors
7.5.4 Basic functionality
7.5.5 Native API Support
7.5.6 Supported Platforms
7.5.7 Apps built using AppCloud
7.5.8 The future
8 The case for hybrid apps
9 Conclusions and Recommendations
9.1 Conclusions
9.2 Recommendations
9.2.1 Carriers
9.2.2 Media Companies
9.2.3 OEMs
9.3 Contact the author of this report: