> In fact Safari has often been the best mobile browser
There are no other browsers on iOS. When you are using Chrome it is using UIWebView (in other words, it is forced to be a crippled Safari due to anti-competitive policy). Although recent Chrome will be using WKWebView which means at least it's same as Safari. The UI around the browser is not the browser.
> Few users cares for logging into some website from mobile Safari just to get a subpar experience over a native app (or a hybrid app),
Few users could tell any difference between native app and web app running in a browser that has modern appy capabilities, provided there is same quality of implementation. The only thing that can make the experience subpar is precisely the lack of capabilities.
>In fact Safari has often been the best mobile browser
I know. I meant across platforms. It's obviously the best on in iOS.
>Few users could tell any difference between native app and web app running in a browser that has modern appy capabilities, provided there is same quality of implementation. The only thing that can make the experience subpar is precisely the lack of capabilities.
For one, a web app adds the extra burden of a JS VM and DOM over native code. This rules out all kinds of graphic and CPU intensive apps. Actually, for any app that's not just a glorified content screen / database view, there's not even a comparison between a web and a native implementation.
Even for basically text-based content consumptions apps, like Flipboard, they had to jump through all kinds of hoops to get smooth 60 fps scrolling within a web view.
And of course there's the battery life, that's a real killer with web apps.
A future based on web apps for mobile is a regression over even 2005's state of the art in the desktop. And it's an experience similar to cross-platform apps -- that is, a "lowest common denominator" across mobile platforms.
There are no other browsers on iOS. When you are using Chrome it is using UIWebView (in other words, it is forced to be a crippled Safari due to anti-competitive policy). Although recent Chrome will be using WKWebView which means at least it's same as Safari. The UI around the browser is not the browser.
> Few users cares for logging into some website from mobile Safari just to get a subpar experience over a native app (or a hybrid app),
Few users could tell any difference between native app and web app running in a browser that has modern appy capabilities, provided there is same quality of implementation. The only thing that can make the experience subpar is precisely the lack of capabilities.