On 16 July 2026 the European Commission adopted two binding specification decisions under the Digital Markets Act requiring Google to give rival AI assistants the same access to Android's mic, camera, on-screen content, wake-word system and app-automation surfaces that Gemini already enjoys — and to share anonymised Search data with competing engines and AI chatbots. The EU DMA Google Android AI rivals ruling is not a fine; it is a build order, and the first time a regulator has treated third-party AI assistants as first-class citizens of a mobile OS.
TL;DR
- The European Commission issued two binding DMA specification decisions against Google on 16 July 2026 covering Android AI interoperability and Search data sharing.
- Rival AI assistants must get parity access to 11 Android features — mic, camera, screen, hotword, app automation.
- Google may require certification for five "restricted" features but cannot gate the other six.
- Deadline: Android 18 by 1 August 2027; simultaneous assistant listening slips to Android 19 / 1 August 2028.
- Anonymised Search data must be offered to rival search engines and AI chatbots from January 2027, at a cost-based fee.
- Google's Kent Walker warned the rules create privacy, device-security and national-security risks.
What did the EU actually order Google to do?
The Commission adopted two binding specification decisions on the same day. The first covers AI interoperability on Android: Google must give any qualifying third-party AI assistant the same OS reach Gemini has — reading what is on screen, opening the camera, using the mic, firing on a wake word while the display is off, and driving other apps in the background by imitating taps and typing. Delivery is required in Android 18, no later than 1 August 2027.
The second covers Search data: Google must offer anonymised Search data to rival search engines and AI chatbots that do search, at a cost-based fee, starting January 2027 — closing a loophole the previous generation of search-competition remedies left open. This follows earlier DMA moves against Apple and Meta, and is analysed alongside the world's first national emotional-AI law in /articles/china-ai-companion-ban-first-national-emotional-ai-law.
Is this a fine, and what happens if Google refuses?
No. A DMA specification decision is a build order, not a penalty. The Commission retains separate power to open a non-compliance case — if Google ships Android 18 without the required interfaces, Brussels can fine up to 10 percent of global turnover (20 percent for repeat offences). The specification decision now defines what compliance looks like, leaving Google less room to argue the DMA is vague.
Which Android features must be opened up?
The interoperability decision covers 11 OS features, split into two groups. Five are "restricted features" where Google may require certification: centralised on-device data access (AppSearch), context-aware intelligence (Magic Cue), structured on-device integration (App Actions/App Functions), screen automation (Computer Control), and system integration (settings, media, screenshots, notifications, power).
The other six carry no certification requirement — any user-installed app the user consents to can use them: ambient data streams (mic, camera, screen contents, location, sensors, in the background), always-on hotword detection on the low-power DSP, long-press invocation, system-level on-device models, third-party model implementations, and background execution.
Paragraph 55 spells out what a certified assistant can reach: retrieving/drafting Gmail, Calendar events, Drive/Docs content, Maps navigation, YouTube playback, SMS/MMS/RCS, and phone calls. Consent still gates all of it; Google can require process isolation and encryption. The one deferred item — letting several assistants listen simultaneously — slips to Android 19 by 1 August 2028.
How does Search data sharing work in practice?
Google must offer anonymised Search query, click and ranking data to rival search engines and AI chatbots, via a multi-layer anonymisation method aligned with the draft Joint Guidelines on the DMA-GDPR interplay. Google may charge a cost-based fee and may assess cyber-security or data-protection risks before sharing. Sharing begins January 2027.
For AI chatbots this is significant: the main structural disadvantage of a chatbot competing with Google is the absence of a live web index and click-signal corpus. The DMA now requires Google to hand over an anonymised version of exactly that corpus, at cost. Google's own agent strategy, covered in /articles/autonomous-ai-agents-google-agent-first-future, sits directly in the path of this remedy.
What has Google said in response?
Kent Walker, Google's Head of Global Affairs, argued the measures would "introduce unprecedented risks to user privacy, device security, and national security." Executive Vice President Henna Virkkunen countered that the Commission hopes to see emerging alternatives to Google Search and Gemini so EU users enjoy greater choice. Teresa Ribera, Executive Vice President for competition, said the goal is a level playing field rather than one tilted toward the largest incumbents. The Trump administration has publicly criticised the DMA as targeting American companies — a backdrop also visible in /articles/apple-vs-openai-hardware-trade-secret-lawsuit.
Why does this matter for the AI industry?
Android carries roughly 60 percent of European mobile users. Until now, any assistant not made by Google or the handset OEM was locked out of the parts of the phone that make an assistant useful — the always-on mic, the camera, the ability to see what the user is looking at, and to act inside other apps. That gap was a permanent structural advantage for Gemini. The specification decision removes it inside the EU and sets a precedent regulators elsewhere will likely reference. Combined with the economic pressure discussed in /articles/ai-job-displacement-economists-nobel-laureates-letter and the compute build-out in /articles/meta-hyperion-50-billion-data-center-louisiana, it signals an environment where distribution — not just model quality — becomes the contested surface.
FAQ
Q: What did the EU order Google to do? A: Open Android's mic, camera, screen contents, hotword detection and app-automation to rival AI assistants by 1 August 2027, and share anonymised Search data with rival search engines and AI chatbots from January 2027.
Q: Is this a fine? A: No. It is a binding DMA specification decision telling Google what to build, not a penalty. The Commission retains separate power to open a non-compliance case with fines up to 10 percent of global turnover.
Q: Can Google still require security and privacy checks? A: Yes. Google may demand certification for five restricted features, require process isolation and encryption, and assess cyber-security risks before sharing Search data with a specific recipient.
Q: When does it take effect? A: Android AI interoperability must ship in Android 18 by 1 August 2027. Search data sharing begins January 2027. Simultaneous listening by multiple assistants moves to Android 19 by 1 August 2028.
Q: Which AI assistants benefit? A: Any third-party AI assistant meeting Google's certification for the five restricted features, and any user-installed app the user consents to for the six unrestricted features. AI chatbots offering search are explicitly eligible for the shared Search data.
Q: Does this apply outside the EU? A: Legally no — the DMA applies to gatekeepers operating in the EU. In practice, Google may ship a single global Android build or region-gate the interfaces; the decision is enforceable only within the EU.
Discussion
0 comments