>I don’t see how that’s related to the issue being discussed.
PWA is not a browser, it is a native app using a browser engine to render a specific website.
>Why do you think “you can install a third party browser, but if you do, you can’t add PWAs to the Home Screen” doesn’t hinder competition?
I literally explained it in my comment you are replying to, but I can repeat. Competition does not exist yet. Browsers do not offer PWA support out of the box, it is a feature to be implemented separately from rendering engine. See Firefox on Windows for an example — it doesn’t support PWA out of the box. This feature has to be built: if Apple were to hinder the competition, they would resist it by not offering the APIs. But they can offer them through the cooperation with vendors, even if those APIs do not exist yet. Say, Mozilla comes and asks for APIs: Apple starts negotiating and proposes the compatibility requirements and a reasonable timeline. They both work on their part and eventually Firefox is released with PWA support. Who would fine or sue them if it worked this way? How the violation of DMA could be proven?
> Why do you think “you can install a third party browser, but if you do, you can’t add PWAs to the Home Screen” doesn’t hinder competition?
Because you can't add PWAs to the Home Screen if you use the first-party browser, either. The whole point of this article is they're turning off PWAs for Safari so that they're all on the same feature footing.
The comment I replied to said “In the meantime current solution could stay”. In context, I can’t interpret “the current solution” else than as what’s in shipping iOS now.
I don’t see how that’s related to the issue being discussed.
> In the meantime current solution could stay simply because it does not hinder any competition.
Why do you think “you can install a third party browser, but if you do, you can’t add PWAs to the Home Screen” doesn’t hinder competition?