Over the next few days I’ll be writing about HTML5 – what it is, and is not, and why some of the issues it faces are irrelevant for Business and Enterprise.
HTML5 has a lot riding on its shoulders, and there are many misconceptions about what it can and cannot do, and why you’d choose to use it as a technology. There are many things that, as of this writing, just don’t completely work. For the most part, these flaws are well known and will probably be fixed in time by the various browsers but there are other problems of expectation that are not really technology problems, so won’t be fixed as such.
The common expectations are that :
- HTML5 works the same in all browsers
- HTML5 works the same on all devices
- HTML5 development is cheap – ’cause it’s the web, right ?
- An HTML5 web app can do everything a native app can
- Instant updates are better than software upgrades
- Developers will eventually flock to HTML5, leaving native apps behind
- Hybrid apps will solve HTML5’s deficiencies
What I’ll be attempting to explain in the posts to follow :
- The ins-and-outs of these expectations
- Why none of the above actually matter for an Enterprise application
- What does matter for an Enterprise considering a mobile application
First post in this series, addressing points 1 and 2 is now available