Apple pulls Siri AI from EU after Commission denies DMA exemption

What happened

The European Commission has formally denied Apple's request for a Digital Markets Act exemption covering the new Siri features that ship under the Apple Intelligence umbrella. Apple had argued that the on-device LLM routing, App Intents-driven Siri actions, and personal-context features were too tightly coupled to iOS internals to be safely exposed to third-party assistants under the DMA's interoperability mandate. The Commission disagreed, and Reuters reports that Apple's response is to simply not roll out the affected Siri capabilities in the EU at all.

This is the third major Apple Intelligence feature set Apple has withheld from the EU, after iPhone Mirroring and SharePlay screen sharing in 2024, and it is now the clearest pattern: when forced to choose between opening a gated API or shipping nothing, Apple ships nothing. The Commission's position, restated this week, is that gatekeepers under the DMA cannot self-certify which of their own features are too sensitive to interoperate. If Siri can read your calendar, draft a reply, and trigger an App Intent in a third-party app, then by the DMA's logic a competing voice assistant must be able to do the same on the same device.

Apple has not given a timeline for when, or whether, EU users will see the held-back features. The Reuters piece notes that Apple is continuing to ship the lower-risk pieces of Apple Intelligence in the EU — Writing Tools, notification summaries, image cleanup — but the marquee Siri rework that was demoed at WWDC, and that App Intents 2.0 was designed around, is staying out.

Why it matters

For most of the last decade, the implicit contract for iOS developers was simple: write to Apple's APIs, ship globally, and assume the surface area is the same everywhere except for a handful of region-locked apps (FaceTime audio in Saudi Arabia, Apple Cash in the US, etc.). That contract is now broken in a structural way, not a temporary one. App Intents, the framework Apple is pushing as the canonical way to expose your app's actions to Siri, Spotlight, Shortcuts, and the on-device model, now has a meaningfully different runtime depending on whether your user is in Munich or Minneapolis.

The community reaction on Hacker News split the way these threads usually do. One camp reads this as Apple weaponizing EU users against their own regulators — withhold the shiny thing, let the press write "EU loses out on AI," and pressure the Commission to back down. The other camp reads the Commission as doing exactly what the DMA was written to do: refusing to let the gatekeeper carve out an exception for the one product surface that matters most for the next decade of platform competition. Both reads can be true at once. The DMA does not care about Apple's product roadmap, and Apple does not care about the Commission's theory of contestable markets. The collision was always going to happen at the assistant layer because that is where lock-in compounds fastest.

What is genuinely new is the speed. iPhone Mirroring was held back from the EU for roughly a year before Apple quietly opened parts of it. The Siri features have not even shipped yet and Apple has already pre-committed to a regional split, which means EU divergence is now being designed in at the SDK level, not patched in after launch. That changes the engineering posture from "ship globally, regionalize edge cases" to "assume two SKUs of the platform from day one."

There is also a real question about whether third-party assistants would actually use the interop if it were forced open. The DMA's interoperability requirements have so far produced more headlines than shipping integrations — the messaging interop mandate has not resulted in any meaningful WhatsApp-to-Signal bridges, and the browser engine choice screen has not dented WebKit's share on iOS in any measurable way. Apple's bet is that even if it were forced to expose Siri's intent routing, no competitor would build against it fast enough to matter. The Commission's bet is that you cannot know until you try, and gatekeepers do not get to make that call unilaterally.

What this means for your stack

If you ship an iOS app with App Intents, you now have to treat the EU build as a distinct target for the foreseeable future. Concretely: any flow that assumes a user can invoke your intent via the rebuilt Siri — "Hey Siri, log my run in Strava and text Maya" — will silently degrade in the EU to the older Shortcuts-style invocation, with no personal-context awareness and no cross-app chaining. Audit your intent definitions now for anything that assumes the new on-device model is doing the parsing, because in the EU it will not be.

For backend teams, the implication is subtler but more annoying. Apple Intelligence's private-cloud-compute routing was supposed to be opaque to your app — you call an intent, the OS decides whether it runs on-device, on Apple's PCC, or hands off to a partner model. With the EU split, that routing decision now depends on the user's region in ways your telemetry will not surface cleanly. If you track latency or success rates on intent-driven flows, expect a persistent EU/non-EU bimodality that is not a bug in your code. Bake the region into your metrics dimensions before you spend a week chasing a phantom regression.

For anyone building a cross-platform assistant or agent product, the Commission's stance is actually the more interesting signal. The EU is now the only major market where the regulator has explicitly said the OS-level assistant slot is contestable, which means EU users are the cleanest testbed for whether third-party agents can win when the home-team advantage is regulated away. If your product depends on being able to run as a default assistant on iOS, the EU is where that experiment will happen first, even if Apple's current move is to make sure the experiment runs on a degraded version of the platform.

Looking ahead

The Commission has tools beyond denying exemptions — periodic penalty payments under the DMA can run to 5% of average daily worldwide turnover, and Apple has already been fined €500M earlier this cycle for the anti-steering rules in the App Store. Withholding a feature is not, in itself, a DMA violation, but discriminating against EU users in a way that pressures the regulator could be characterized as one. Expect the next 12 months to be a slow-motion negotiation conducted through press releases and SDK release notes, with the actual question — does the assistant layer get carved open or not — getting answered somewhere between Brussels and One Apple Park Way, and not by anyone who reads this site.