There is an argument for HTML5 that runs: because it can run across multiple devices, HTML5 can help you slash the costs of developing new apps. Now, rather than dealing with the time and cost of developing native apps, you can simply write once and deploy everywhere (near as damn it).
Now, I’d dearly love to simply agree with this. But, as with so many things in tech, the reality is not quite so clear cut.
Over on his blog, my boss has been talking about the reasons why people build applications. This leads me to think, the motivation for building an app and the skill set of its current developers will ultimately determine if HTML5 is a less expensive option.
But, of course, the cost argument is a powerful one. So let’s look at four ways in which HTML5 may save you money:
So is HTML5 the cheap option? In the final analysis, the answer is: Yes. No. Maybe. It depends. Not the most satisfying I know but probably the closest to the truth.
I’d love to know what you think.
Are you being pushed to HTML5 for cost reasons?
Are you happily going that way anyway?
Do you think cost is irrelevant?
Let me know.