I hope you realize that the cookie prompt madness is because companies were (and still are; see "legitimate interest") grasping at straws to keep mining user data. Many websites offer a simple "All/Required/Personalized Cookies" choice.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 17.4 Nerfs Web Apps in the EU
- Thread starter MacRumors
- Start date
- Sort by reaction score
I am not one that knows everything about PWA'a but just looking at MS documentation on what PWA's are allowed to do seems to add up to complex technical reason to limiting the uses on a sandboxed iOS.
Overview of Progressive Web Apps (PWAs) - Microsoft Edge Developer documentation
Progressive Web Apps (PWAs) run natively on Windows 10 or later. Here's everything you need to know about PWAs, as a web developer.
learn.microsoft.com
When installed on a device, PWAs function just like other apps. For example:
- PWAs have their own application icons that can be added to a device's home screen or task bar.
- PWAs can be launched automatically when an associated file type is opened.
- PWAs can run when the user signs in.
- PWAs can be submitted to application stores, such as the Microsoft Store.
Advanced capabilities
PWAs also have access to advanced capabilities. For example:- PWAs can continue working when the device is offline.
- PWAs support push notifications.
- PWAs can perform periodic updates even when the application is not running.
- PWAs can access hardware features.
Web-related advantages
Finally, PWAs can run in web browsers, just like websites. Running like websites gives PWAs with advantages, such as:- PWAs can be indexed by search engines.
- PWAs can be shared and launched from a standard web link.
- PWAs are safe for users because they use secure HTTPS endpoints and other user safeguards.
- PWAs adapt to the user's screen size or orientation, and input method.
- PWAs can use advanced web APIs such as WebBluetooth, WebUSB, WebPayment, WebAuthn, or WebAssembly.
So possibly some of the advanced capabilities of a PWA that acts like a native app conflict with iOS security. Apple is more likely to support their web-related advantages then PWA's acting like a native app which is why they made that change in beta 2. Possibly this might be altered further either direction after Apple is satisfied that someone can't maliciously create one for data mining or something else.
Exactly how are you impacted by this? PWA's suck and no where near as good as native apps. This is the same for Java apps back in the day and not reactor. My brother used to always say "smells like Java".
Not OP but while PWAs on iOS do suck in their current iteration, they are at least marginally better than the respective sites in a Safari tab.
Apple should just stop selling their products in Europe. People will find out that are good alternatives, too.
wow just wow. Not going to buy a new apple device for a while. I don't think I'll miss much tbh, an ipad pro that forces refresh pages every time it goes to background, a watch that can't take blood pressure, a mac that is released in 2023 with 8gb of ram.
It is time, thank you Apple.
It is time, thank you Apple.
So basically the EU wanted openness for all. But Apple, even though in other ways it wants to be a very inclusive company, implements thing in the most toddlerish way it can. I love Apple, but this just looks childish now.
The EU didn't want openness for all. They wanted openness from Apple. They're the only one affected by this part of the DMA.
As far as we know all they did was disable a feature in a beta that needed to be changed under the DMA. We'll have to wait to see if they chose to re-enable it with support for multiple browser engines.
Man, I wonder why... (looking at literally every other general purpose OS in existence)
I like how you throw in "general purpose" as if it has sort of effect on the argument. Calling it "general purpose" doesn't kick in some sort of moral or legal requirement to act like Windows.
Again, the other "general purpose" OSs that you are referring to resulted in a trillion dollar malware market.
Last edited:
Trying to redevelop existing software to accommodate new regulations is not an easy task. If you don't mind a long read, here is an insightful essay from Steven Sinofsky on the topic. It covers quite a bit of history, and the process behind the EU browser ballot and its impact.
For those who've been saying "but Apple has to do this because web apps have to load in the default browser"...
No. They don't. When an app is installed as web app, by the EU regulations it is fine for that web app to continue to open in the browser it is installed in. It's up to other browsers to provide that functionality themselves. We know for a fact that this doesn't matter because both Android with Chrome and Windows with Edge have this behavior; web apps installed with the default browser can still use that browser even if another browser is set as default. That doesn't violate any rules.
This is just Apple introducing more hurdles to force people to use the App Store where they previously could use none-native alternatives. And no, this also isn't just Apple being more strict about what a PWA is and is not like someone else here mentions, in that scenario this wouldn't be restricted to the EU.
This is just Apple being a petty anti-consumer company. Again.
The DMA doesn't make any requirements that would force them to implement this. And no, they are not "the only one affected by this part of the DMA". Both Microsoft and Google are too. Heck, Microsoft has had to deal with such rules for decades prior to the DMA. And yet, they don't need to pull crap like this, because the DMA doesn't require it.
No. They don't. When an app is installed as web app, by the EU regulations it is fine for that web app to continue to open in the browser it is installed in. It's up to other browsers to provide that functionality themselves. We know for a fact that this doesn't matter because both Android with Chrome and Windows with Edge have this behavior; web apps installed with the default browser can still use that browser even if another browser is set as default. That doesn't violate any rules.
This is just Apple introducing more hurdles to force people to use the App Store where they previously could use none-native alternatives. And no, this also isn't just Apple being more strict about what a PWA is and is not like someone else here mentions, in that scenario this wouldn't be restricted to the EU.
This is just Apple being a petty anti-consumer company. Again.
The DMA doesn't make any requirements that would force them to implement this. And no, they are not "the only one affected by this part of the DMA". Both Microsoft and Google are too. Heck, Microsoft has had to deal with such rules for decades prior to the DMA. And yet, they don't need to pull crap like this, because the DMA doesn't require it.
Last edited:
Or... they interpret the rules around preferencing different than you do. Or... this is just a beta or stopgap while they update the code to support additional browsers.
Again, cynicism isn't a substitute for logic. Counter to your conclusion, it would benefit Apple more for existing web apps to continue to use Safari.
Six hours later and five pages of comments and no update to the article from MacRumors to reflect reality? Wtf.
Last edited:
That's not it. Support for PWAs on iOS was always more limited than on other platforms. Now they decided, for whatever reason, to take some features away. Some speculate that alternative browser engines could make PWAs more convenient and more discoverable for users and therfore become an alternative to regular apps.
I started using a PWA app recently in my home network. In essence it's like using a regular web app, just with a little more convenience. I would miss it for sure.
Evidently, there is a claim that OP is just wrong. The change doesn't affect PWAs at all. See post 14.
I don't know who's right. But maybe the person from post 14 just tested on a non-EU version of the beta?
Here is one blog post with a screenshot that explains why the change might be intentional (notice the wording of the dialog):
Bruce Lawson's personal site
» Is Apple breaking PWAs out of malicious compliance?
brucelawson.co.uk
Hopefully, the editorial staff will investigate and provide an update.
The EU isn't Europe.
And Apple is a business. It isn't about to kiss goodbye to a huge share of the market.
Apple making the user experience worse to petulantly strike against the EU is not a good look
Yeah but now that Apple says it's dangerous we all have to get in line to agree with them and prove our fealty to the great Apple overlords
No, they didn't. They're just making changes in a beta to comply with the DMA.
