The company said cutting off PWAs was part of an effort to comply with the Digital Markets Act, arguing browsers other than its own Safari software would expose users to security and privacy risks that were not permitted under the law.
They are so full of shit, it's unbelievable! Are they really claiming that their own browser is THE ONLY legal browser there is?!
It's blatant anti-competitive behavior and anybody who cares about antitrust should be outraged about this and similar efforts. Getting legal protection for such decisions is nothing but regulatory capture.
@ICastFist
Yes, however the EU enacted new regulations to put a stop to that practice, so that Apple will be required to allow other browsers on their platform.
Disabling PWAs is how Apple has chosen to retaliate against those new regulations.
almost every apple user says shit like this while using Gmail, Google docs, and the Google app on their phone and blindly giving Apple their data. let's be real for a sec and not pretend most Apple users give a flying fuck that Google tracks them. if a user truly cared about privacy, they would eventually come to the conclusion that it doesn't matter Apple or Google, privacy means not giving your data to ultra mega corps. so owning an iPhone isn't adequate for privacy either. both googled Android and iOS give your data back to their respective companies. neither are good for your privacy. one day when Apple start changing their tune on privacy policies, Apple fan boys who have put their their whole lives into the apple ecosystem will realize they put all their eggs in one basket.
I am using https://lichess.org/ and prefer it over the native iOS App for this free chess website.
It is in fact a smoothly running PWA and even supports notifications (e.g. to remind one to move in correspondence games).
Same goes with Voyager ( https://vger.app/ ), that was used to create this post.
They will try. This is about OS-level APIs. In order for a browser to to install and run PWAs, it needs certain OS APIs for e.g. home screen installation, storage and notifications. iOS currently has these APIs but Safari severely limits what you can do with it. Now the DMA will force Apple to accept other browsers, which have no such limitations. So, Apple now wants to remove these APIs altogether and kill PWA support outright, before that portion of the DMA takes effect.
There probably will be a lawsuit and Apple will probably lose, but it will take years to resolve that. And in the mean time PWAs remain dead and the only way on the iOS home screen in paying the 30% app store cut.
Isn't it the other way around? Afaik the EU commission investigates them, makes a decision, and sets a due date for Apple to comply or pay a potentially hefty fine. It would be Apple who'd have to sue against that, and they'd have to pay the fine until a court confirms or nullifies it.
Yes because what they are doing is just removing websites from the app-store. Other app-stores might add those websites to their store if they want but for the user it is almost always better to just save the website to their homescreen, which gives the exact same UX as previous web-apps but now you don't need to go to the app-store to download it, the app takes up no storage on your device and the web app can't access your privacy sensitive device IDs that might be used for cross-app tracking.
This is so frustrating because this is a big hit to browsers like firefox because Apple has such a large userbase, but this same userbase does not give a shit, and this is because they bought an apple in the first place. Frustrating
They are not sabotaging "web apps" (aka websites), you just need to save the website to the homescreen if you want to use a web app, (this is both quicker and takes up less storage on your device so it is better for the end-user).
They are removing these "apps" from the appstore because they are not native apps.
PWAs (Progressive Web Apps) are their own categories of websites and they do indeed have the ability to behave like an actual app. They are much more than just a shortcut, which apple is reducing them to.
On android, my PWA that I developed for fun can go full screen and appear as though a browser isn't wrapping the page, I can send notifications, I can access the microphone and camera, I can do nearly everything you could expect an app to do, I can support offline mode, I can store data locally, and I can manage my PWAs permissions as well as uninstall my app at an OS level. My entire family uses my PWA, and they see it as an app.
Are there some things native apps can do that PWAs can't? Absolutely, but that is not the point. PWAs are an open and clearly defined technology to the web. Windows supports them as well.
Apple is refusing to accept that though. They are removing notifications, badges, etc, and reducing them to what you have described, just a shortcut to a Safari window. They are citing security concerns even though other operating systems are able to implement security around them just fine.
The real issue is Apple wants more control over how you use your device and is acting against the consumer.
On android, my PWA that I developed for fun can go full screen and appear as though a browser isn’t wrapping the page
That is literally how I am using kbin.social right now even though it's just a website
I can send notifications, I can access the microphone and camera, I can do nearly everything you could expect an app to do
All of those are defined in the web spec as well so you wouldn't need an app for that (if apple implemented all of them, not sure if they have)
I can support offline mode
Your cached web page can do that too (even though most web pages don't because it's not a common usecase)
I can store data locally
Cookies have existed for much longer than the iPhone
uninstall my app at an OS level.
A website added to your home page basically acts like an app: it has an icon on your home screen and you can longpress > delete it just like apps
Badges might be the only valid complaint (I don't know if they are part of the web spec)
[Apple] is acting against the consumer.
Not sure how this is hurting the consumer. This has been announced many years ago and devs haven't been able to publish new or update old web apps for ages, so this change only applies to those very old apps still on the appstore.