Apple’s refusal to support Progressive Web Apps is a detriment to the web
1–10 of 451 posts
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#2This is definitely true. But in addition to this, it is insane that it appears that none of the big browsers has begun implementing encrypted storage via touch and so forth.
One of the main arguments i see in my organisation to create apps for our ventures is the fact that it will enable touch login. I recon it should be rather simple to duplicate / wrap the localStorage API to do this?
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#3I can see why apple is hesitant to do this. But there is definitely a middle ground.
Require the same developer registration process as they currently do for iOS apps. Then require some apple provided javascript to provide access to these needed functions. App review as before.
At that point they can do interesting things: charge per 1000 installs, enforce the use of apple pay. They can operate a business model that is slightly different, but the same at its core - tax developers for access to their user base/platform.
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#4I 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.
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#5OP builds part of this argument based on "Apple isn't responsive to my complaints about web apps."
Apple isn't responsive to complaints in general. Are they less responsive to web app complaints than other complaints? Otherwise, the argument holds no water.
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#6I 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 d…
If you're referring to the pre-App Store iPhone OS, have you considered the possibility that they were just late with the SDK?
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#7I am starting to get a vibe that there is a new breed of programmers who think that knowing just one language is good enough and learning anything else is "stifling innovation".
I don't even want to start on "PWAs work more seamlessly than native". I just cannot take person making such claims seriously.
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#8I 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 d…
> web apps are reaching for feature parity with native
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#9Google thinking webpages can be as good as native applications is a detriment to the UX.
Re: Apple’s refusal to support Progressive Web Apps is a detriment to the web
#10I 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 d…
Is there a reason for users to care about this at all? Because it seems to me that this just solves problems for developers while making the user experience worse or not as good as it could be. The same goes for Electron-based apps.