Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yes, definitely. Good for Apple corporation. Good for their revenue.

Bad for customers. Still the same song.

I am surprised Apple did it this way? Not at all.
Is it economical? Definitely.

Is it anti-consumer? Yes. Because otherwise consumer would benefit from this change (or consumer would not feel the change at all). But as it breaks previously working feature it is anti-consumer.
You don’t really know if they’re even telling the truth … iOS is closed source so you cant know if they’re solution wouldn’t support other engines just fine.
 
  • Like
Reactions: 3530025
Apple only implemented this in the worst way (like, not actually implementing anything) so they can say „See, it‘s worse!“, and preventing them from benefiting.
 
Apple probably boasting about how much money they pump into iOS development and then 95% of that one ends up in the emoji and Vision Pro personas departments.
No wonder there is no one looking at the OS itself. Especially since the DMA was released on such short notice and no one informed Apple, who is the victim of a witch hunt!
 
To reiterate, after all the fanfare about finally supporting the Web Push API on iOS 16.4, Apple has now killed that functionality entirely for users in the EU.

Push notifications are not supported in Safari, they were only available to homescreen web apps.
 
You can follow maliciously or you can follow while keeping the feature set full.

Apple could have easily implemented support for the PWAs capabilities for 3rd party browsers. They could have added additional API to have 3rd party browser display PWAs just like Safari/Webkit does now.

Apple choose not to. They intentionally choose to be anti-consumer.
“Easily” says the obvious former Apple engineer.
 
  • Like
Reactions: sbailey4
Apple is just asking to have a hammer brought down on them for these type of behavior.

Apple entire security argument is complete BS. Apple is just being petty over losing basically pennies.
Safari uses deep private API to wrap these links into being treated as apps consisting of a WebKit runner, which gives them isolated storage and permissions. They aren’t prepared to a third party, let alone dozens of third party browsers, have this capability. So by law they have to disable it from Safari.
 
Apple could have implemented this differently, also on macOS Chrome and Safari can create PWA side by side.
iOS does this by creating new apps that run a WebKit runner. The EU has put limits both on the ability to prefer a particular browser and to have the platform browser use private API.

So they can only ship the current feature if they allow third party browsers to install new executables as apps on the home screen.
 
  • Like
Reactions: mrBeach
“Easily” says the obvious former Apple engineer.
Let me answer with one of my previous comments which addresses this "easily" thing:

 
No, the default behavior of Web Apps could stay exactly the same until a user actually chose to change default web browsers. So long as the default browser is Safari, there's no security issue that requires this change.

People who continue to use Safari shouldn't need to see any difference in the behavior...

That would be great, but it would be illegal.
 
  • Like
Reactions: mrBeach
They aren’t prepared to a third party, let alone dozens of third party browsers, have this capability. So by law they have to disable it from Safari.
This is incorrect.

By law they have to offer possibility to use third party browsers/browser engines. Nothing in the DMA states they have to disable it. The DMA intended they add the support for 3rd party browsers.

(does not matter how many of them there are, they may have offered universal API and it would be on the devs of 3rd party browsers to use this API if wanted; DMA form has been around for two years, quite some time to add this API)
 
[…]

The EU is not trying to do any of that kind. If iOS getting sideloading would stop iOS from being iOS, it would actually be more like macOS than Android if you look at UI, codebase and features.
Also, Apple is not trying any of that, they are just trying to keep on stealing fromd evs who have the right to keep their money. In the EU at least that's the case.

[…]
The EU has crafted laws to play robin hood. It’s interesting you use the hyperbolic word stealing when literally if iPhones were to disappear, people will still have air to breathe and food to eat and money to spend. And I like how you speak for the EU. 👍/s
 
  • Like
Reactions: iOS Geek
It will be interesting to see how Safari will be responding to the inevitable competition where the other browsers will support push notifications and Safari won't.
 
Not the EU fault that Apple made their OS insecure from web browsers and not properly sandboxing web browsers.

The fact is that EU made a decision on new law. As a consequence of that decision, PWA is not as viable option for any developer in any country on any operating system anymore.
 
  • Like
Reactions: iOS Geek
EU Is ruining this for everybody: when you are building a globally used product, PWA it's not an option anymore.
On a serious note: is PWA really a thing today? Do you use it? For which sites?

Maybe it's just me, but I really did not came across PWA for quite some time. Seems like blast from past to me.
 
  • Love
Reactions: wilhoitm
The fact is that EU made a decision on new law. As a consequence of that decision, PWA is not as viable option for any developer in any country on any operating system anymore.

Again Apple choose to make an insurer os part and is choosing not to fix the issue to properly sand back web browsers instead being petty
 
On a serious note: is PWA really a thing today? Do you use it? For which sites?

Maybe it's just me, but I really did not came across PWA for quite some time. Seems like blast from past to me.

I don’t remember the last time I used one. If there isn’t a native app for something I’m not wasting my time on it.
 
On a serious note: is PWA really a thing today? Do you use it? For which sites?

Maybe it's just me, but I really did not came across PWA for quite some time. Seems like blast from past to me.

What is a PWA? I am being serious! I really do not know what it is? And I think most people do not know either!
 
  • Like
Reactions: 3530025
So you're happy, that you can use a different browser on your Samsung. But you argue against that choice on your iPhone. That does not make any sense.
You have always had a choice of browsers on iPhone. They may all have the same underlying web engine, but they are all completely different apps with different features and detriments. Chrome has a horrendous record for security and resource hogging and data stealing, no matter what browser engine it's using. I have no problems if people want to use other browsers. I have problems with government dictating things to companies and forcing them to change things for no good reason all in the name of making things "equal" by taking away their competitive advantages.
 
Last edited:
Correct me if I'm wrong here but... doesn't the fact that non-WebKit browsers are allowed now mean that any other browser app can effectively implement Web Apps? Any App can save a shortcut to the home screen (unless I'm mistaken), and it can see that you launched it via the home screen, and it can use that to give you the version of the app with full permissions vs the ordinary web version where it can't use as much storage space and whatnot?

IDK, persistent web apps are so niche I kind of doubt even most MacRumors readers know much about them...
 
What is a PWA? I am being serious! I really do not know what it is? And I think most people do not know either!
PWA (which stands for "Progressive Web App") is a website that can be saved or installed and behave as if it were a standalone application. This includes things like launching full-screen with no web browser UI elements, appearing with a custom icon on the home screen, and support for things like push notifications, badging, geolocation, media streaming, and video/microphone access. Google's requirements for a PWA to be installable is that it includes code to properly handle offline modes, so that the web app can launch successfully (but maybe not "work") even when not connected to the internet.

Apple has never used the term "PWA", preferring instead of refer to the various web technologies individually. Some of those technologies have been supported in Safari since the very early days of iOS (such as geolocation support), and some of those have only recently been introduced (such as push notifications and badging).

The idea of "progressive" in PWA is that it can work normally as a website in a browser, but you can get some deeper system integration by installing or saving it. On desktop, this means that it launches is its own window and shows up as its own icon in the Dock. On iOS, this built on the (long-existing) add to home screen functionality, but recently started only exposing some functionality to web apps that had been saved.


I use PWAs for some social media sites, where I don't want to install an app that has full access to my device for tracking and advertising purposes, but I want something that can notify me when people mention me in a post.
 
I understand that. But they have to let those browsers run on the platform anyways. That's part of the legislation.
Correct, but they can't protect a web app via a 3rd party browser from accessing other data or your hardware i.e. camera, mic, speakers, etc. Since it would have access to it just like Safari would. Just that you wouldn't get notified (Potentially). And Apple couldn't stop that from happening. So, just removed the feature. Also, it's not used much so no sense in fixing it for a small portion of users.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.