Login
Android AI Violates DMA
The issue before the commission currently is the built-in advantage for Gemini on Android. When you turn on any Google-powered Android phone, Gemini is already there and gets special treatment at the system level. The European Commission is taking aim at the lack of features available to third-party AI services. The commission believes that there are too many experiences on Android that only work with Google’s Gemini AI, and as a gatekeeper, Google must change that.
[…]
European regulators are proposing several broad changes to the way AI tools operate on Android phones. Some of this is straightforward, like allowing third-party AI tools to be invoked system-wide via hot words or button presses. This might also include allowing AI tools to view screen context when the user opens them.
[…]
Many of the Gemini AI features in Android, including Magic Cue, rely on running local models, and Google has been slow to allow third parties the system access to make that work effectively. So the EU is also suggesting a mandate that would ensure developers have the necessary hardware access to run local models “with high levels of performance, availability and responsiveness.”
Via John Gruber:
The difference between Google and Apple on this front is that Google just blazed ahead and shipped Gemini integrated into Android in the EU, and is now facing compliance problems after shipping. (Ask forgiveness.) Apple isn’t shipping Siri AI in the EU in iOS 27, knowing that it’s going to be deemed non-compliant. (Ask permission.)
Previously:
Update (2026-07-17): Juli Clover:
The European Commission today formally ordered Google to give third-party AI services the same access to Android device features that Gemini has.
[…]
The European Commission is giving Google a full year to implement changes that will meet the Digital Markets Act requirements, and that's before any legal appeals Google might make.
Google (via Ben Schoon):
This Android ruling threatens device security by granting external apps sensitive and powerful device permissions without these safeguards.
Update (2026-07-23): John Gruber (Mastodon):
They provide separate “Q&A” overviews of the guidance for Android AI interoperability and web search sharing, and the full guidance documents are PDFs (Case DMA.100220 for Android AI, Case DMA.100209 for web search).
[…]
The EC is demanding that Google create APIs that allow third-party AI assistants to do everything Google Gemini does now[…]
[…]
Also, in my reading, the EC is demanding that Google make available to third-party AI assistants all information in Google’s own apps (Gmail, Google Calendar, Google Docs, Google Maps, etc.) that Gemini has access to.
[…]
Apple unfortunately hasn’t shared any technical details describing its proposal for a “Trusted System Agent” that it shared with the EC last year. But whatever Apple’s vision for the Trusted System Agent is, I don’t see how the EC would deem it compliant with the DMA if they want from Apple anything close to what they are now demanding from Google.
I don’t know what will come of this, but I’m pleased to see it in the sense that it is logically coherent. The TSA seems like a way to give the appearance of doing something without actually solving the problem. Like Gruber, I don’t really see why Google would want to comply with this rather than taking their Gemini ball and going home. Unlike Gruber, I don’t find it scary to let users opt into sharing their data and background time with apps of their choosing. I don’t like software design by government committee, but it seems less bad than further entrenching an unfettered monopoly. Maybe this could have been avoided if Google had developed its own reasonable solution instead of shipping something that was obviously not compliant.
