As for your argument about core platform services, the app store is a core platform service and (I’m pretty sure) uses WebKit internally, at least for some of its pages in login and payment flows, and similar for various iCloud-related functions accessible from Settings.
I’ve read the DMA, you don’t have to be condescending.
This is a silly and thin technicality, and not at all the same as what people are mad about. Nobody cares that WebKit is used to render certain windows on iOS and MacOS - it's Apple's choice to implement first-party programs that way. They can defend their usage of it internally, the problem is the limitations they impose on competitors.
> I’ve read the DMA
You're certainly taking some elements in liberty. It remains unclear how defining WebKit as a "PWA runtime environment" exempts it from the terms of the DMA or DSA.
Just to be clear, I’m absolutely in favor of having a free choice of PWA engines, I just don’t see this being implied by the DMA and the present gatekeeper designations. The question really is how a PWA runtime environment differs in principle from the regular iOS app runtime environment, which the DMA also doesn’t mandate to be replaceable.
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.
> "... the Commision concludes that Safari, including all the elements that allow for the display and access to web content, either standalone, integrated or embedded in other software applications or similar, constitutes a web browser CPS ..."
If you've seriously worked on hashing out all the details of CPS and clearing up the ambiguities, you cannot be unaware of this decision since this will impact everything on your daily works. Yeah I did that because the precise definition of CPS was critical for my work in the last year.EU is not that dumb, to my understanding they've been pretty serious in respecting the spirit of this specific legislation. You cannot say that some part of it can be simply opted out by adjusting the definition of your product. What they care about is how business is done and make the market control out of it.
There is no such consumer-driven market for in-app UI libraries, be they WebKit-based or not. The "consumers" in such a market would be the app vendors, and in fact this is an area well-served by existing products from competing vendors. That's clearly not what the DMA is trying to regulate.
> No, DMA wording made it very clear that it's about web browser engine.
You follow this up by quoting a clause that manages core platform services.
What it says is:
> The gatekeeper shall not require [people] to use, to offer or interoperate with [stuff] of that gatekeeper in the context of services provided by [third party devs] who use the gatekeeper’s core platform services.
A good example where this is applicable is the App Store, which is designated as a core platform service. PWAs aren’t designated as core platform service and there’s also an argument to be made that web developers aren’t considered “third party devs” (or as the DMA calls them “business users” due to a lack of agreement between Apple and them.
> And they cannot make self-preferencing on their products.
Same here. This one is even narrower because it’s only limited to preferential treatment in the sense of “ranking and related indexing and crawling”
> The gatekeeper shall not treat more favourably [in ranking and related stuff] [their own products and services] than [similar products and services by others]
This applies to ranking apps in the App Store. It has no bearing whatsoever on PWAs unless somehow Apple starts ranking PWAs in a list and then chooses to rank their own PWAs higher.
The other one is also much narrower than you’re reading it.
> The gatekeeper [shall not prevent users from switching to and subscribing to different apps including browsers]
This mainly pertains to setting default apps and switching default apps. This tangentially relates to PWAs, but installed PWAs are technically not run in Safari and instead in their own app that uses WebKit under the hood, so it’s not so clear if this would apply to PWAs.
> There's no room for this kind of interpretation in the view of enforcement entity. Apple is just trying to buy time by pretending ignorance.
I can’t distill a lifetime worth of legal experience into a tangible piece of evidence nor are there readily available authoritative sources on compliance with government regulation narrow and simple enough that I can just present them without much worry of you understanding them, especially since you’re already struggling with, what is considered in European legal standards, rather straightforward legal text.
So all I have is a trust me bro, and perhaps an appeal to common sense: Apple’s lawyers didn’t just wake up today and said to themselves “You know what, we were too cautious with interpreting the DMA a couple of weeks ago, I’m sure it’ll be fine if we keep PWA installs without implementing a way for other browsers to install them as well”, much less a variation in which they are trying to buy time by feigning ignorance.
We already know that the EU reached out to Apple about disabling PWA installs. So with that in mind, do you think the lawyers woke up one day and said “fuck it” or do you think it’s more likely the lawyers gave the go ahead after the EU told them that PWA installs as implemented in iOS are beyond the scope of the DMA?
The core platform service in this case would be iOS itself.
Also, nowhere in the DMA does it say that there must be a contractual relationship between an entity and the gatekeeper in order for the former to be considered a business user. Windows is a designated CPS under the DMA and no contract with MS is required in order for you to make, distribute, and have your users run your software on their Windows PCs.
You’re right, iOS is a CPS. But that doesn’t change much in the meaning of the provision, nor does it make it applicable to web developers.
Specifically for iOS it would change to:
> The gatekeeper shall not require [people] to use, to offer or interoperate with [stuff] of that gatekeeper in the context of services provided by [third party devs] who use [iOS].
The PWA engine is a core part of the iOS operating system, so there is no “us[ing]” “offer[ing]” or “interoperat[ing]” with other stuff.
But the point below is more relevant here.
> Also, nowhere in the DMA does it say that there must be a contractual relationship between an entity and the gatekeeper in order for the former to be considered a business user.
True, I’m skipping the minutiae and going straight with the end conclusion.
Article 2 of the DMA contains all definitions.
For business users it states under clause 21:
> 'business user' means any natural or legal person acting in a commercial or professional capacity using core platform services for the purpose of or in the course of providing goods or services to end users
The CPS in this instance is not iOS because iOS isn’t used in the course of providing goods and services nor for the purposes stated above nor can it be used for those purposes.
The CPS in question is as defined under clause (2)(a), namely an intermediary service, more precisely, the App Store.
And Apple only allows usage of the App Store (and its IP needed to make apps) when under contract.
The DMA does not prohibit this, because doing so would be nationalizing private property. Ipso facto, business users are under contract and web developers aren’t “business users” as defined under the DMA.
Hence the main clause in question, the one clarified at the top, doesn’t apply to PWA developers.
> Windows is a designated CPS under the DMA and no contract with MS is required in order for you to make, distribute, and have your users run your software on their Windows PCs.
That’s not a consequence of the DMA, it’s a consequence of Microsoft not monetizing their IP in that way.
For furher clarification, please see this fellow HNer's comment and its response by user kmeisthax: https://news.ycombinator.com/item?id=39564383
> The gatekeeper shall not require end users to use, or business users to use, to offer, or to interoperate with, an identification service, a web browser engine or a payment service, or technical services that support the provision of payment services, such as payment systems for in-app purchases, of that gatekeeper in the context of services provided by the business users using that gatekeeper’s core platform services.
And they cannot make self-preferencing on their products.
> The gatekeeper shall not treat more favourably, in ranking and related indexing and crawling, services and products offered by the gatekeeper itself than similar services or products of a third party. The gatekeeper shall apply transparent, fair and non-discriminatory conditions to such ranking.
> The gatekeeper shall not restrict technically or otherwise the ability of end users to switch between, and subscribe to, different software applications and services that are accessed using the core platform services of the gatekeeper, including as regards the choice of Internet access services for end users.
And Safari has been explicitly designated as a separate core platform service. There's no room for this kind of interpretation in the view of enforcement entity. Apple is just trying to buy time by pretending ignorance.