Apple didn't just lose its gatekeeper case. It lost the right to argue before it complies.
The headline is that the App Store stays under the Digital Markets Act. The binding part is a procedural rule that now tells every designated gatekeeper the same thing: comply first, litigate later.

Image: Cédric Puisney / Wikimedia Commons, CC BY 2.0
The reported version of last week's judgment is simple and, as far as it goes, correct: on 8 July the General Court of the European Union dismissed Apple's challenge to being called a gatekeeper, and the App Store and iOS stay bound by the Digital Markets Act. That is true. It is also the least interesting thing the court decided. The sentence everyone repeated is about Apple. The sentence that will matter for years is about procedure, and it binds companies that were not in the room.
Apple had brought three actions, joined by the court as Cases T-1079/23, T-1080/23 and T-214/24, against the designation the European Commission made on 5 September 2023. The Eighth Chamber, sitting with five judges, dismissed all of them. To understand why the win is broader than the App Store, it helps to read what each of the three arguments actually was, and how the court disposed of it.
One store, not five
Apple's first argument was a counting exercise. The DMA sets quantitative thresholds — users, business users — above which a service is presumed to be a gatekeeper. Apple runs five App Stores, on the iPhone, iPad, Mac, Apple Watch and Apple TV, and it argued that each should be assessed on its own. Counted separately, only the iPhone store clearly crossed the line; the others, Apple said, should fall outside the designation.
The court rejected the premise. What matters under the DMA, it held, is the function the service performs, not the hardware it runs on. The definition of an app store, the judgment reasons, "should be technology neutral and should be understood to encompass those provided on or through various means or devices," because each of the five stores is used "for the same purpose, namely to intermediate between end users and business users in the distribution of applications and in-app digital content." Different download volumes and app mixes across devices describe a different user experience; they do not describe a different service. So the five are one, and the one is in scope. This is the DMA reading its own definitions the way they were written — around the economic function, not the marketing category — and it is the reading that makes the law hard to shrink by slicing a product into pieces.
The iMessage point that looks like a win and isn't
Apple's second argument concerned iMessage, which the Commission had discussed as a possible core platform service. Here Apple prevailed — the court held its iMessage challenge inadmissible — and a fair number of headlines recorded that as a partial victory. Read the reasoning and it is the opposite of a victory; it is a lesson in where obligations come from.
The court found the challenge inadmissible because iMessage appears only in the recitals of the designation decision, not in its operative part. And under the DMA, the court explained, classification alone carries no legal weight: the regulation "does not provide for any obligation or entail any legal consequences solely on the basis of the classification of a service, so long as the service in question has not been referred to in the operative part of a designation decision." Because iMessage was never named in the part of the decision that binds, it imposes nothing on Apple — and you cannot ask a court to strike down something that does not bind you. Apple did not win the iMessage point. It was told there was nothing there to win, because the operative clause is the only part that speaks.
Classification carries no obligation. The operative clause is the only part of a decision that speaks. Everything else is commentary.
The holding that binds everyone
Put the App Store and iMessage rulings together and a principle falls out that is bigger than either, and it is the real news. The court drew a hard line between two stages of the DMA. The first stage is designation: the Commission names you a gatekeeper. The second stage is obligation: the Commission, in a specific enforcement act, tells you precisely what you must do or stop doing. And the court held that a gatekeeper may challenge an obligation only once that second-stage act exists and produces binding legal effects — not before, and not in the abstract.
The consequence is a sequencing rule, and it is worth stating plainly because it reorders the leverage every regulated company is used to having. You cannot go to court to argue that a DMA duty is unlawful in principle. You must wait until the Commission issues a concrete decision directing you to comply with a specific requirement. By the time that decision exists, you are already bound by it. You comply first, and you litigate afterward — while complying — and only on points of law. The order of operations is the whole game, and the court has just fixed it in the regulator's favour.
This is the distinction between a rule being in force and a rule being enforced, and it is where most people misread European regulation. Apple's designation has been in force since 2023; that was never really the fight. The fight was over whether a gatekeeper could tie the specific obligations up in abstract litigation before they ever bit. After this judgment, the answer is no. The obligations bite on the Commission's schedule, and the courtroom opens only after the biting has started.
Who else is now bound by the same clock
The DMA currently designates seven gatekeepers: Alphabet, Amazon, Apple, Booking.com, ByteDance, Meta and Microsoft. The sequencing rule was decided in Apple's case, but it is not about Apple. It is now the answer any of the seven will get if they try to litigate a duty before a specific decision compels it. That is why the judgment reaches companies that were not party to it: the court did not just resolve a dispute, it set the terms on which every future dispute of this kind will be heard.
The load-bearing date is not in this ruling; it is on the calendar just ahead of it. Alphabet faces binding Commission specification decisions expected by 27 July, the first real test of the rule the Apple judgment just confirmed. Amazon and Microsoft are under separate proceedings over whether their cloud businesses should be designated at all. ByteDance remains under compliance scrutiny over TikTok, and Meta is appealing a €200 million fine while a separate enforcement track over its consent model continues. Every one of those threads now runs through the same procedural needle: the obligation lands, the clock starts, and the challenge comes later, if at all.
Why a procedure in Luxembourg becomes a default everywhere
It is tempting to file this as European housekeeping, a matter of admissibility and chambers and joined case numbers. That is exactly the mistake that has let the DMA surprise people for two years. The obligations the sequencing rule protects are concrete and they travel: alternative app marketplaces and sideloading, third-party payment options, an end to steering restrictions, browser and default choices, interoperability requirements. These are changes to how iOS and the App Store work, and Apple does not build a separate iPhone for Europe. When the compliant version becomes the version that exists, the compliant version tends to become the version everyone gets, whether or not their own legislature ever passed a word of it.
That is the mechanism people mean, usually too loosely, when they say "the Brussels Effect." It is not that Europe fines the loudest. It is that Europe writes an obligation, forecloses the abstract escape routes, makes compliance the path of least resistance, and lets a global product carry the result outward on its own. The engineering of that outcome is dull by design — it lives in the difference between a recital and an operative clause, between designation and obligation, between in force and enforced. Last week the court tightened one of those seams. Apple lost a case about its App Store. Everyone else lost the argument they had not yet made.
A caveat, because precision is the point. Apple may still appeal to the Court of Justice, within two months and ten days of notification, on points of law only — not the facts, and not the wisdom of the policy. Such an appeal does not suspend the obligations in the meantime. So even the escape hatch that remains runs on the same principle the judgment just entrenched: the rule keeps operating while you contest it. In European technology regulation, that sentence is doing more work than any fine — and it is the one the summaries left out.
References
- Court of Justice of the European Union — General Court judgment in Cases T-1079/23, T-1080/23 and T-214/24 (Apple v Commission)
- JURIST — EU General Court upholds Apple's gatekeeper designation under Digital Markets Act
- Concurrences — The EU General Court upholds a Big Tech company's gatekeeper designation for its app store and operating system under the DMA (Apple)
- Courthouse News Service — Apple loses EU court fight over Big Tech gatekeeper rules
- PPC Land — Apple loses App Store and iOS gatekeeper appeal at EU court


