> web apps are the great savior that abstract away all the device fragmentation.
I'm not sure if you are trying to be serious or not with this. Do you really believe this is true today? That you can build a mobile experience using HTML that compares to that of a native app?
Certainly there are SOME cases where it makes sense. But for MOST apps, it simply does not. For example, let's say I wanted to build an app that used location and could run in the background. How, exactly, would I build a "web app" that worked across iPhone, iPad, and say 75% of Android devices?
And how is whatever you come up with "HTML5"?
WORA has always been, and always will be a pipe dream. HTML5 gets closer but, unfortunately, due to the dynamics of mobile the target is moving further away.
You can't build web apps that run in the background and expect any sort of browser compatibility, and you know it. That's why you picked that example, despite the fact that I freely admitted in my original comment that there are use cases for which a native app is a better choice. If you are bound and determined to hate the web, good for you.
I'm not sure if you are trying to be serious or not with this. Do you really believe this is true today? That you can build a mobile experience using HTML that compares to that of a native app?
Certainly there are SOME cases where it makes sense. But for MOST apps, it simply does not. For example, let's say I wanted to build an app that used location and could run in the background. How, exactly, would I build a "web app" that worked across iPhone, iPad, and say 75% of Android devices?
And how is whatever you come up with "HTML5"?
WORA has always been, and always will be a pipe dream. HTML5 gets closer but, unfortunately, due to the dynamics of mobile the target is moving further away.