I&#x27;ve seen this anecdote given as rationale, but you can&#x27;t say that the &quot;web app&quot; model on iPhones failed when Safari doesn&#x27;t give you the needed functionality to make web apps.<p>For example iPhone Safari does not do push notifications, an essential ingredient if you want web apps, whereas Chrome on Android does. With Chrome on Android you can do Facebook&#x27;s Messenger without installing anything. And while iPhone Safari led the way with some useful additions, like the possibility of specifying higher resolution icons for &quot;Add to Homescreen&quot;, they dropped the ball on such improvements since iPhone 3G. In fact iPhone Safari is behind in implementing web standards. Apple also rejected Adobe&#x27;s Flash and I concede that was for good reasons, but that left a huge void in how media, like video and games, could be delivered. You know, things like HTML5 Video and WebGL came after that. You also have to take into account that the first two models (iPhone 1 and iPhone 3G) had poor resolution, poor hardware and poor battery life by today&#x27;s standards.<p>So you know, if Safari on iPhone 1 is the anchor by which you judge native apps, well of course native apps are better. You also make it sound like &quot;the people&quot; forced Apple to open their SDK. Oh come on, you can&#x27;t be that gullible. An SDK was inevitable. What&#x27;s the point of building your own OS if you can&#x27;t lock people into its APIs? That&#x27;s a lesson Microsoft taught us. The only reason for its delay was them taking the time to figure out how to control it. Do you remember when Google Voice along with other apps where rejected because they &quot;duplicated existing functionality&quot;?<p>You may not see it, but web apps have been winning for some time and there&#x27;s no end in sight. When Google Voice was rejected by Apple, Google still delivered its functionality by means of a web app. When the Google Maps integration app was replaced by Apple with their own, which I might say it is inferior and unusable in my city, for a while iPhone users used Google Maps on the web, as it&#x27;s very much usable.<p>All it takes for web apps on mobile phones to be more common is for the browser makers to implement the needed functionality. Right now the front-running in implementing web standards relevant for mobile phones is Google&#x27;s Chrome and sadly not Firefox (though I hope that will change). And I must say it works well.