The editorial frames Apple's withdrawal as 'the nuclear option' — pulling the product rather than re-architecting it — and notes this is the same playbook used for iPhone Mirroring and SharePlay. It implies Apple could comply if it chose to, but is treating EU users as collateral in a trade fight with Brussels.
The deeper read in the editorial is that Article 6(7) effectively bans AI assistants that can only function as single-vendor, vertically integrated stacks. The Commission is signaling that interoperability must be designed in from the start — third parties must be able to plug in without the gatekeeper brokering access to user data.
Apple's stated rationale, as reported, is that exposing Siri's app-action APIs to Alexa, Google Assistant, and ChatGPT would force it to share the private user data the assistant depends on to function. Rather than build that architecture, Apple chose to withhold the feature from the EU entirely.
The Commission's official statement says Apple 'failed to make its AI tool comply with EU regulations,' placing the burden squarely on Cupertino. The framing rejects Apple's privacy defense and asserts that compliant architectures are possible — Apple just declined to build one.
Apple has told the European Commission it will not roll out the upgraded, LLM-powered Siri in the 27 EU member states. The decision, reported by Reuters on June 9, follows the Commission's refusal to grant Apple an exemption from the Digital Markets Act's interoperability requirements. The new Siri — the one that finally does cross-app actions, on-screen awareness, and personal context — was already a year late from its WWDC 2024 announcement. Now European users will not get it at all, at least not in 2026.
The specific sticking point is DMA Article 6(7), which obliges gatekeepers to provide third parties with "free of charge, effective interoperability with, and access for the purposes of interoperability to, the same hardware and software features" that the gatekeeper's own services use. Apple argued that opening Siri's app-action APIs to competitors — Alexa, Google Assistant, ChatGPT's voice mode — would force it to expose private user data the assistant depends on to function. The Commission's reply, in essence: that is the point. Either build an architecture where third parties can plug in without you brokering their access to user data, or do not ship the feature.
Apple's response was the nuclear option: pull the product from the market rather than redesign it. This is the same playbook Apple used for iPhone Mirroring and SharePlay screen sharing earlier this year, both of which remain unavailable to EU users. The Commission, for its part, issued a statement saying Apple "failed to make its AI tool comply with EU regulations" — phrasing that puts the burden squarely on Cupertino rather than the regulation.
The surface-level read is a trade fight: Apple vs. Brussels, with European users as collateral. The deeper read is that the DMA is now reshaping how AI assistants get architected, full stop. The Commission has effectively ruled that an AI assistant that can only function as a vertically integrated, single-vendor product is incompatible with the EU single market. If Siri needs your contacts, calendar, photos, and on-screen content to be useful, then any rival assistant must be able to request that same context through a documented API — not a private one Apple controls.
This is a much harder engineering problem than it sounds. The current generation of "agentic" assistants — Siri's new mode, Google's Gemini-on-Android, Microsoft's Copilot Recall — all share an architecture pattern: a privileged process with broad OS-level read access to user state, feeding a model that produces actions. The privilege is the product. Strip it down to a permissioned API and you get something closer to the old Siri Shortcuts: capable in narrow domains, useless for the open-ended "do the thing I'm thinking about" use case the marketing demos.
Apple's public argument is that the DMA forces a privacy regression. Their filing reportedly claimed interoperability would require sharing user data with companies that don't meet Apple's privacy standards. The Commission's counter is that Apple is conflating two things: the right of a user to grant a third-party app access to their data (which the DMA protects) versus Apple's preference to be the sole gatekeeper of that access (which it doesn't). Senior engineers should read the Commission's position as a forcing function for capability-based security models, not a privacy rollback. If you architect for explicit per-capability user consent — "this assistant may read your last 10 emails for this query" — you can satisfy both the DMA and a reasonable privacy posture. Apple, so far, has chosen not to do that work.
The community reaction has been predictably split. On Hacker News, the top comments cluster around two poles: "Apple is right to refuse — the DMA is making the EU a tech backwater" versus "Apple is exposing the lie that their privacy moat was ever about users rather than control." Both are partly correct. Mistral CEO Arthur Mensch has been vocal in recent months that EU AI startups can't compete if assistant-level distribution is locked to the OS vendor, and the Commission's ruling reads as a direct response to that lobbying. Meanwhile, EU consumer groups have noted that Apple is selling iPhones in Europe at full price while shipping a materially less capable OS — a position that will not survive a class-action environment forever.
If you're building anything that touches device-level context — assistants, agents, productivity tools, anything that wants to read or act on user state across apps — you now have a clear architectural fork. Path A: vertically integrate, ship outside the EU, accept that 450 million users are off the table. Path B: design the capability surface as a public, documented API from day one, with explicit per-call consent and audit trails. Path B is more work upfront and substantially cheaper than Path A six months later.
Concretely: stop treating "context access" as an internal implementation detail. The new minimum viable architecture for an EU-eligible assistant looks like (1) a context broker service that mediates all reads from user state, (2) per-capability OAuth-style scopes the user grants at runtime, (3) a queryable audit log of which agent read what and when, and (4) a documented public API surface that your own assistant uses on equal footing with competitors. If your own product can't function through the same API you'd expose to a rival, the Commission will eventually notice.
For RAG and synthesis products specifically: the same logic applies to whatever "private corpus" you're indexing. If your assistant reads a user's Gmail, calendar, and Slack to answer questions, the DMA increasingly implies that a competitor's assistant must be able to request the same reads through the same interface, with the user as the consent authority — not you. Build for that now, not after a Commission letter.
The likely endgame is not Apple winning a court fight or the EU backing down. The likely endgame is a slow, grudging rebuild of Siri's architecture around documented interop surfaces, shipped 18 to 24 months late to EU users, and quietly adopted everywhere else because the same architecture turns out to be what regulators in the UK, Japan, and eventually the US will want too. The DMA is increasingly the de facto global spec for how gatekeeper platforms expose AI capabilities. Apple's refusal to ship is a stalling move, not a strategy. The engineers reading this should architect as if the DMA model is the global default by 2028 — because for assistants that touch device-level user state, it probably will be.
I understand Apple's position on this one. This is essentially a backdoor into all of your data. It is also a very useful feature. The EU regulators are disallowing guardrails without which this backdoor will be used to strip-mine people's personal data. The privacy implications are not le
It's totally fine that Apple doesn't release this feature for EU customers. If they think they can still sell enough phones it's also fine I guess.What's not fine, is to blame the EU for the missing feature. It's damaging their brand and damaging their reputation. Just think
I'd rather have my iPhone turn into a dumbphone than EU bow to the Megacorps.
I find it interesting that Apple prefers to fall behind in Europe rather than opening their platform a tiny bit.It gives us European some opportunities. I have a side project at work that was heavily threatened by Siri’s new features. Now I feel more relaxed as Siri isn’t coming there anytime soon.B
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Apple said "hey, can we not comply with the law", the EU said no, so it didn't launch. Seems pretty straightforward to me.I can see why Apple might want to request an 18 month exemption, there's clearly extra work required to comply with EU regulations. But on the other hand it a