3 ms·
There is a chance that this is still a “disabled for now” feature. My understanding of the third-party browser requirements in the DMA is they have to be able
by SllX 3y ago
There is a chance that this is still a “disabled for now” feature.
My understanding of the third-party browser requirements in the DMA is they have to be able to do anything Apple’s Safari can do if they want to, and while Apple’s built out a bunch of entitlements for browsers and other DMA requirements, they haven’t done the same work for PWAs. Yet?
So given that, it would actually violate the DMA if Safari supported them but Chrome and Firefox couldn’t, and they’re not going to allow that until they’ve taken the time to figure out how they want to proceed, if at all, with allowing it for third-party browsers.
- alberto180 3y agoCrippling PWAs would benefit their baseline through their App Store or Core Technology Fee though
- SllX 3y agoPWAs aren’t exactly great on iOS to begin with, and if that was their aim, it would make more sense to disable it worldwide rather than just the EU. They may well not bring it back for all we know, but if they are going to, it’s not going to be without figuring out exactly what it is they want PWAs to be able to do and what resources they’ll be allowed access to which probably means additional APIs and entitlements for third-party browsers.
- deleted 3y ago[deleted]
- alberto180 3y agoIt works quite well for some use cases
- SllX 3y agoSure, but from the perspective of web developers advocating for PWAs it was already crippled. Now it’s just disabled in the EU.