Re: I
This will take a bit of clarification. Let's start with the PWA and update issue. You are correct that there is no contract between Apple and PWA developers. This has no relevance to my point. The reason I pointed out that PWA developers cannot update their applications is because you claimed that Apple isn't deleting data related to PWAs because it's like any other time when an update is incompatible. It is not. If I write a native application that runs on IOS 17 and someone updates to IOS 18 and Apple has made a change meaning they will refuse to run my application, I can fix it by updating my application. The user's files are restored. If I wrote a PWA, I do not have any way to update it to get the user's data back. The article alleges that, even if I could, the files won't exist. Even if they do, I can't write a native app that would access them. Their restriction on those developers, even though there is no contract between them, means that they have effectively deleted the user's data which they used my app to access. The harm is to the developers, but Apple doesn't have to care, but there is also harm to users which they should care about and may be legally required to. Other commenters have suggested this might be a violation of both computer misuse legislation and clauses of the DMA.
Me: “Existing PWAs could run in WebKit because that is what they're already set to run in”
You: "No they shouldn’t, Apple does *not* have that legal freedom. The EU made it a legal requirement that the user be allowed to opt out of using WebKit. This is what that looks like in practice."
No, that is not what it looks like. Opting out does not mean that I will never use WebKit. It's already installed on my phone. I can use it or, and the or is crucial here, something else. That means that I could choose to use a non-WebKit browser as a browser but still use Safari when I want. It means that I could set one PWA to try to open in Firefox, and assuming that it doesn't work properly right now, set it back to Safari until Firefox fixes their bugs. Nowhere in the law does it say that Apple must remove WebKit from availability, and they haven't done so since there will still be a Safari and WebKit in system UI components in all devices. They have complete legal freedom to continue to offer PWA support through WebKit and allow other browser engines to do the same. They have removed that option without a legal or technical need to do so, which is where their other motives become more obvious.
And by the way, intent does tend to matter a lot in whether they're allowed to do that. The law has many parts that explicitly prohibit intentional degradation of features when a user uses something Apple doesn't like. They don't specifically list possible degradations. This is not necessarily going to go Apple's way.