Very questionable argumentation. This can be seen from two different angles: 1. PWA is a native wrapper for a web application, not a browser. It is supposed to be limited to the app website. DMA does not tell Apple that every app with embedded WebView should offer users possibility to switch the engine. Why PWA should be treated differently here? I‘d rather clarify this with regulators first, before harming end users…
> DMA does not tell Apple that every app with embedded WebView should offer users possibility to switch the engine. 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?
Is there any reason that you couldn't just install a third-party browser and add PWAs to the home screen that use WebKit as a rendering engine?
Why would these two different things affect each other?