This is a pretty weird article, and fairly obviously just an advertisement for appcelerator.
So, native wins over html5- for what actual purpose? Isn't this something you evaluate on a case by case basis depending on client, need, budget, maintainability, and on and on? What prize exactly has native "objectively" won?
Isn't this the thinking that has led to the plague of "DOWNLOAD OUR APP" banners preventing me from seeing anyone's content when I'm on a mobile phone? Have native apps won so hard that nobody can bear to look at a piece of text without a round trip to the app store?
Beyond discussing if appcelerator uses this kind of post for advertising (is their blog, isn't it?). The point is valid and I am upset when this discussion is not based on real facts.
For example, currently html rendering performance is very slow but surely will be improved in the near future. My personal problem is when it's intolerable slow.
You can mostly make HTML5 "fast enough", if you know where all the sweet spots are. A comparison of a finely tuned native app, to a a naively built html5 coded up with much the same methodologies as a 1999 dhtml site, ignorant of the the constraints and allowances of the mobile platform, seems hardly fair, but that's what most people are going to see.
failure to use even easy performance wins like html5 app cache, css3 3d transforms (hardware accelerated), local storage, etc. etc.
But it's all tech, which is putting the cart before the horse. I'm a local mom and pop grocery store. Do I need an app?
So, native wins over html5- for what actual purpose? Isn't this something you evaluate on a case by case basis depending on client, need, budget, maintainability, and on and on? What prize exactly has native "objectively" won?
Isn't this the thinking that has led to the plague of "DOWNLOAD OUR APP" banners preventing me from seeing anyone's content when I'm on a mobile phone? Have native apps won so hard that nobody can bear to look at a piece of text without a round trip to the app store?