> provide a compelling explanation of how the way iOS runs PWAs constitutes a use of Safari, or of web browsing. Oh, this is easy. First-party software is dis

> provide a compelling explanation of how the way iOS runs PWAs constitutes a use of Safari, or of web browsing. Oh, this is easy. First-party software is distributed by Apple. They choose how that software is presented because they are the operator of the software. PWAs and websites are distributed by third-parties. They are websites, not curated by Apple, that load in your browser. It's only after you use your browser's "PWA" function (something everyone should have) that we change into this "WebView" scenario. It's arbitary, and not at all the same as Apple rendering Apple Music or Settings using WebKit. > how a PWA runtime environment differs in principle from the regular iOS app runtime environment A PWA is packaged by the user. If Apple's "solution" is forcing all apps to display PWAs in a Safari WebView, then yes, the DMA will target it as a core service. I don't see why the EU would roll over when they made specific carveouts for browser control in the DMA.