zlacker

>>jaffat+(OP)
I think push notifications and offline support are the real killer features that Apple currently doesn't support.

It's kind of funny as a web developer because for the longest time Apple seemed to be the one pushing the mobile web forward but now that web apps are reaching for feature parity with native, Apple's initial momentum seems to be ancient history.

It seems Apple still thinks of the mobile web as a content delivery platform rather than an application platform. Their proprietary additions (mostly CSS) largely focused on making things prettier, their rationale for opting out of standard features (e.g. autoplay) often only work under the assumption that the only use for those features would be in the context of traditional content pages.

You want an app? Develop for our walled garden we tightly control to offer our users the best possible experience. If you want it on the web, stick to creating content our users can consume in Mobile Safari, our app for reading websites.

>>pluma+E2
> It seems Apple still thinks of the mobile web as a content delivery platform rather than an application platform.

Apple wants in-app purchases. Why deliver full flexed apps in the web were people pays using PayPal or VISA if you can force people to use your store?

This is the reason Apple killed Flash and is the reason why they may kill any other web technology.

>>kartan+g5
Conversely, Apple is in a perfect position to spearhead a web micropayment API standard, and has total control over the browser and thus the way users' use it.

>>detaro+M8
They have already released Apple Pay for the Web.

>>Classy+gd
My post clearly was missing the word "standard", which I've now added. Running in as many browsers as possible once something is completed is important for these things.