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.
Or that it's in fact straightforward to offer an API for browser engines to integrate with caching, background operations, notifications, etc., and Apple should have held off compliance with DMA until these were implemented?
If so I'd love to learn more. I'm sort of inclined to believe that these currently sit deep in WebKit and it's a nontrivial exercise to pull them out and offer them as an API to other browser engines.
That would have been the least controversial aspect of their first attempt at compliance, in my view.
They could have also just allowed third-party browsers to offer a "PWA home screen" as an intermediate step until the APIs are ready. I can't think of a PWA API that's impossible to implement in a third-party browser other than appearing on the home screen and in the app switcher under its own icon.
They could have also just forced the same upon WebKit PWAs until the API is ready.
So many options. Yes, all of them would have taken some engineering work, but that hasn't stopped them from doing very complicated things in other aspects of their DMA compliance framework.
Yeah but how much work would it be to implement, and is it worth implementing for the 1% of sites that use it?
I'm not saying it's straightforward to build the necessary apis for that but they had years to do it.
a user can download spying native apps from the apple app store but I cannot decide to trust Google, Microsoft, Mozilla with their browser security sandbox?
otherwise why do you specifically care what browser engine choice I make?
Apple could disable web capabilities in safari and let other engines do otherwise
you CAN and SHOULD stay in Safari if you trust only apple browsers to be safe?
what do you care if I use chrome and got fucked? (which I wont)
do you want to tell me that I should not use macos, linux, windows android and firefox or edge or chrome because I may get fucked?
you do not really understand that it is MY choice how I get fucked with a lastpass native app clone on apple or with a real chrome browser
nobody stops you to stay by your webkit engine!
Since ~nobody uses PWAs, or at least so few people that Apple can’t justify the effort to retain any advantages PWAs confer on its own browser/OS, doesn’t it become a business decision at that point?
it is also an effort to build access for disabled people
the difference is Apple has practically disabled the web as an app store and in the future if it is possible to launch web apps on every platform, there will be 99% web apps
apple is a big company and it is such a vital thing they can and will be forced what android, windows, linux, mac os(!) can do...
it is like claiming not many disabled people wanted to use my services until now (huge stairs without lift or so) so I just do not want this 2 days and 0,000000001% of my monopolisitc budget to build access for them
very WEAK arguments from apple, practically lies
mac os users have been safe from service workers and web app capabilities using chrome and firefox and edge in the last 5-10 years
surely apple is able to keep ios and ipados users safe from these scary other browser engines
it is much easier to safeguard 3-10 other browser engines than millions of native apps
in addition, do they really have to pay attention to other than chrome, edge and firefox? if somebody uses a chinese spy browser or a russian, the same when somebody downloads any other spying ot malicious native app
do they even need to care about me optin out from safari on MY 1000 dollar iphone?
what the fuck, I am not a child!
keep safari safe and at max give me some warning before downloading chrome or firefox or whatever!
> 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.
This is quite easier said than done. Simply copying a feature from competitor is not neccessarily easy especially if they challenge deep architectural decisions that have been made in the past.
See, Apple? This is how you can implement PWAs so that users do not accuse you of other browser's problems. Then again I assume this is already known in Cupertino but not implemented because it would break down that wall around the garden, brick by brick.