In its very definition the web is for everybody, not just for a small group of lucky people who can afford a very expensive piece of hardware and are happy to get locked into a fixed environment governed by a single company. It has to be as flexible as possible in order to be a success on the web. HTML5, on the other hand by its very definition is a web technology that should run independent of environment, display or technology.
That is what native Apps are – they are built and optimized for one single environment and purpose and are fixed in their state – more on that later. It will not be the same for the next person. Of course the tailored suit will fit you like a glove and looks amazing but if you ever want to sell it or hand it over to someone else you are out of luck. The main problem here is that almost every single comparison misses the fact that you are comparing apples and pears (no pun intended).Ĭomparing an HTML5 application’s performance with a native App is comparing a tailored suit with one bought in a shop. The big thing everybody who wants to talk about the problems with HTML5 is performance. These lead to myths about HTML5 that get uttered once and then continuously repeated – a lot of times without checking their validity at all. The ongoing discussion about the “readiness” of HTML5 is based on a lot of false assumptions.
0 kommentar(er)
