The Truth About HTML5 – Part #2 (MobileFever)

I recently wrote the second part of my HTML5 article: The Truth About HTML5, over at the mobilefever website.

In this part called: The Industry Bear Hug I review the massive adaption of HTML5 done by different software and hardware companies which is turning into a serious threat to the HTML5 vision:

HTML5 Bear Hug

Here's part of it:

1. Giants like Google, Apple and Microsoft have practically (although not officially) dumped their own technologies (Google Gears, Silverlight) in favor of HTML5. They are investing in making their browsers and micro browsers 100% certified for HTML5. Microsoft will even bring native “off-browser” support for HTML5-based widgets in Windows 8 (demonstrations have already been shown – see image below).

Native Html5 code side by side with Excel native application - Windows 8

2. Software companies developing Internet browsers are adding HTML5 support. Some of them (such as Mozilla) are aiming high with HTML5, and going to enrich the language beyond the standard capabilities, in order to try and turn their browsers into a web-based operating systems (we all know ChromeOS, the same goes with WebTops running Mozilla FireFox, etc.). The goal is eventually to compete with native apps by allowing web applications to do things they cannot do running inside existing browsers.

3. MEAP companies are adopting the “hybrid” approach where HTML5 applications are running inside proprietary containers “theoretically” closing some additional capabilities which are not yet part of the standard HTML5 functional standard (such as specific hardware integration etc.).

4. Industrial devices manufacturers (building rugged or niche devices) are in the process of building their own proprietary HTML5 containers (mostly running on top of Android and Windows Embedded) to allow easier integration with their own proprietary hardware (barcode scanners, printers, etc.)

5. Mobile applications vendors are developing web apps using HTML5, and whenever they encounter a technical limitation they usually adopting (or build) a native container that will complete the missing functionality while “wrapping” and “hosting” the original web app. (There are plenty of containers, native wrappers such as PhoneGap, which are providing web access to some native resources).

As you can see, there are many contenders in this HTML5 race. Unfortunately, each category is taking a different course, resulting in a fragmentation.

Read more about HTML5 fragmentation threat over at MobileFever

More Articles About HTML5:

Mobile Spoon Predicts: By 2013, Html5 Will Rule Enterprise Mobility
How to build a mobile web app that looks and feels like a native one?
Html5 – The Only True Cross Platform Technology for Mobile Devices


Technorati Tags: ,