As I'm looking at the vision pro and try to envision what I could with it, when I think of developing a new app for it, those kind of extreme hostilities come to my mind now.<p>It just shows they don't care, they are releasing a whole new platform right now and at the same time show one of the most abusing attitude to developer I think we have rarely seen.<p>Apple app store condition were already overreaching but this time they really went the extra length with every single of their DMA adaptations.
The reasoning here from Apple seems reasonable to me to be honest - they’ve gone into a surprising level of technical detail, quite interesting. I suspect many in this thread are commenting without actually reading their argument.
Wow. I have no words. This is quite something, even for Apple.<p>> to comply with the DMA’s requirements, we had to remove the Home Screen web apps feature in the EU. [...] Still, we regret any impact this change [...] may have.<p>Regrets all the way to the bank. I'm sure it has nothing to do with the Core Technology Fee whatsoever.
>Addressing the complex security and privacy concerns associated with web apps using alternative browser engines would require building an entirely new integration architecture that does not currently exist in iOS and was not practical to undertake given the other demands of the DMA and the very low user adoption of Home Screen web apps.<p>If alternative browser engines and PWA is enough to pwn iOS, maybe it was never really secure in the first place.
>Addressing the complex security and privacy concerns associated with web apps using alternative browser engines would require building an entirely new integration architecture that does not currently exist in iOS and was not practical to undertake given the other demands of the DMA and the very low user adoption of Home Screen web apps.<p>This makes me worried Apple will remove PWA support altogether.
Apple is run by glorified accountants.<p>Jobs and Ive are long gone.<p>I would expect a bit more decency and awareness, but they probably suffer some kind of tunnel vision.
Can someone please clarify? Deep down I hope that "home screen apps" means something else than the recently added support for PWAs...
Does this mean PWAs will not work anymore on iOS?
It's just a f*cking link on the home screen. Opening in the browser of the user's choice.<p>This doesn't only hurt PWA's, it also hurts very simple webapps that are nothing more than a responsive website with some functionality and data. Made easily accessible by a link (with title and favicon) on the homescreen.<p>Of course, one can open a browser, wait, click again on some bookmark icon, scroll to the webapp, click it, wait again... and use it just like that.<p>The world wide web is an evil place. Luckily Apple protects everybody with an iPhone. The year of the Linux desktop, Linux tablet, Linux phone, Linux smartwatch, Linux AR glasses could not come soon enough.
There is a bug in Safari's Intelligent Tracking Protection where sometimes when I visit one of my own websites, it will refuse to send an auth cookie. ITP forces this behavior if you have used Safari for seven consecutive days without visiting a website... but it seems to occasionally happen by mistake, which is very frustrating UX. This problem doesn't exist with home-screen web apps, which are now unavailable in the EU.
I am curious how they have approached this in the code structure.<p>It sounds like it could be a challenge to maintain if multiple regulatory bodies across the globe start asking for their own little changes.
The only real reason to use PWA so far was access to Web Push Notifications on iOS, which likely to stop working altogether. If you fork $99 to apple, you may be able to use "Safari Push Notifications". Maybe one of their 600 new apis will allow Chrome to show notifications?
People need to own the unintended side effects of their preferred regulation instead of constantly complaining about companies not embracing the “spirit” of said regulation.