On 8 July 2026, the EU General Court dismissed Apple's challenges to its Digital Markets Act gatekeeper designation for the App Store and iOS. The headlines framed it as Europe forcing the App Store open, but the ruling is narrower than that. What the court did was confirm that Apple remains subject to DMA obligations for those services and reject Apple's attempt to split its app stores across iPhone, iPad, Apple Watch, Mac and Apple TV into separate services. It did not, by itself, create a new developer right or order Apple to open anything new on the day of the judgment. The distinction matters if you build for the platform.

What the court actually ruled

The core of the judgment is about designation — who the rules apply to — rather than any specific new obligation. The court rejected Apple's attempt to have its five app stores treated as separate services, finding that they all perform the same function of connecting developers with users, which keeps them inside a single gatekeeper designation. On iMessage, the posture is worth stating precisely: Apple was not ultimately designated as a gatekeeper for iMessage following the Commission's market investigation, so the DMA's obligations do not currently apply to it, and the court's handling of Apple's iMessage-related complaint leaves that unchanged. Apple can still appeal to the Court of Justice of the EU, the bloc's highest court, but only on points of law, not for a fresh look at the facts.

The most consequential procedural point is sequencing. The court's reasoning limits Apple's ability to challenge the substance of DMA obligations in the abstract before the Commission has adopted a specific enforcement decision applying them. In plain terms, designation can be challenged at the designation stage, but fights over the scope of individual obligations generally have to wait for concrete Commission action. That matters beyond Apple, because other designated gatekeepers may face the same sequencing limit, and it makes pre-emptive, broad legal attacks a weaker delay tactic for any gatekeeper facing DMA enforcement.

What it does not do — and where the opening actually comes from

Here is the correction worth making explicitly. The obligations that developers care about — allowing alternative app marketplaces and web distribution on iOS in the EU, letting developers steer users to cheaper payment options outside the App Store, and opening iOS features to third parties — do not originate in this ruling. They come from the DMA's gatekeeper rules themselves and from separate Commission enforcement, most notably the €500 million anti-steering decision of 23 April 2025, the first fine ever levied under the DMA, which found that Apple's restrictions prevented developers from directing users to cheaper options; Apple has appealed that fine, and it remains pending. Wednesday's ruling is a different matter from that appeal, and from the separate Commission interoperability proceedings and specification decisions on iOS access.

So the accurate way to describe the ruling is that it reinforces the framework behind those obligations by making it harder for Apple to dismantle them in court pre-emptively — not that it hands developers anything new on the day it was issued.

What it means for developers

For developers, the ruling is indirect but useful. It does not change App Store economics the morning after the judgment, and it does not automatically deliver new APIs or alternative distribution access. What it does is reinforce the legal foundation underneath the DMA obligations developers care about: alternative app marketplaces and web distribution in the EU, anti-steering, and interoperability. The practical gains still depend on Commission enforcement and Apple's implementation, not on this judgment alone.

The reality check is that the gap between the rules on paper and working access remains wide. Research by the Free Software Foundation Europe found that, of 56 formal interoperability requests made to Apple under DMA Article 6(7), not one had produced a concrete working solution as of early 2026, with Apple frequently arguing that requested features fall outside the scope of the law. And even where steering has been enabled, it is not free: according to legal analysis of Apple's revised EU business terms, Apple layered new fees onto external-purchase links — a 5% initial acquisition fee and a 10% store-services fee on link-out purchases — that the Commission considered non-compliant. In other words, developers have the rights on paper and, in many cases, still not the access or the economics in practice. This ruling narrows Apple's room to keep that gap open; it does not close it.

The bigger picture

Two pieces of context keep the ruling in proportion. First, Apple's central objection was never actually before the court. Apple maintains that the DMA forces it to weaken the privacy and security that define the iPhone, and the judgment settles only who the rules apply to, not whether they are wise or whether Apple's security concerns have merit — that argument remains live and unresolved. Second, the DMA is not a rubber stamp for the Commission: only last month the same court partially annulled Meta's gatekeeper designation, freeing Marketplace from the rules while keeping Messenger inside them, which makes Apple's outright loss more pointed by comparison. There is also a geopolitical charge worth noting in a line: Washington has objected to European rules that land hardest on American companies, and rulings like this add to that friction.

One more scope point for developers outside Europe: these obligations are EU-specific. A developer in Singapore, the US or India does not automatically gain steering rights or access to alternative iOS app marketplaces because of a DMA ruling; the benefits, such as they materialise, apply to the EU market.

Key Takeaways

  • On 8 July 2026, the EU General Court dismissed Apple's challenges to its DMA gatekeeper designation for the App Store and iOS, rejecting Apple's bid to treat its five app stores (iPhone, iPad, Apple Watch, Mac, Apple TV) as separate services and confirming a single designation covers them. Apple can appeal to the CJEU on points of law only.

  • The ruling's most consequential element is procedural sequencing: a gatekeeper's ability to challenge the substance of a DMA obligation in the abstract, before the Commission issues a specific enforcement decision, is limited — which matters beyond Apple, since other gatekeepers may face the same limit and it weakens a key delay tactic.

  • Crucially, this is not a fresh order to open the App Store. The developer-facing obligations (alternative app marketplaces and web distribution, anti-steering, interoperability) come from the DMA rules and separate enforcement — notably the €500 million anti-steering fine of April 2025, which Apple is appealing — and this ruling reinforces that framework rather than creating new access. iMessage is not currently subject to DMA obligations.

  • For developers, the effect is indirect but real: it makes DMA enforcement harder to stall. But access remains limited in practice — the FSFE found 56 interoperability requests under Article 6(7) had produced no working solution as of early 2026, and enabled steering still carries Apple fees the Commission considered non-compliant. These obligations are EU-only; developers elsewhere gain nothing automatically. Watch the Commission's specific enforcement decisions for where paper rights become working access.