The EU Just Broke Google's Grip on Android's AI Assistant
On 16 July 2026, the European Commission handed Google two sets of binding specification measures under the Digital Markets Act. One forces Google to share Search data with rivals. The other, less discussed but arguably bigger for marketers, forces Android to let rival AI assistants compete on equal footing with Gemini. That second measure is what I want to talk about.
Because I think this is the moment the default-assistant lock on Android quietly ends. And that changes how your brand gets discovered on the one device most Europeans hold in their hand.
What actually happened
The Commission issued binding rules requiring Google to give competitors' AI services equal access to Android functionality. Until now, third-party assistants had restricted access to the operating system, while Gemini enjoyed full access.
The detail that matters: users will soon be able to activate their preferred AI assistant by voice, in the same way "Hey Google" works today. They will also be able to let that assistant act inside apps, booking a taxi, drafting chat replies, or answering questions about a place they visited. You can read the specifics in the Commission's guidance on AI interoperability and Search data sharing.
Why the timing is significant
These are binding specification measures, not consultations. They apply now, and they target the roughly 60% of EU users who own an Android device, per the Commission's own figures.
Pair this with the parallel decision on Search data. Google must now share the data it uses to optimise its own results, and critically, AI chatbots offering search functionality are explicitly eligible to receive it. I covered the data side in how the EU cracked open Google's Search data vault. The assistant side is the other half of the same story.
How the multi-assistant device changes discovery
Here is the mechanism in plain terms. Today, an on-device query on Android runs through Gemini by default. Tomorrow, that same query could route to ChatGPT, Perplexity or Copilot, depending on what the user has set.
From my observation, that removes the assumption most brands still work from: optimise for Google, and you are optimising for the phone. That assumption is about to break.
| On-device query layer | Before 16 July 2026 | After the DMA measures |
|---|---|---|
| Default voice assistant | Gemini via "Hey Google" | User's chosen assistant |
| Assistants competing | One (Gemini) | Gemini, ChatGPT, Perplexity, Copilot |
| Data feeding rivals | Restricted | Shared Google Search data (anonymised) |
| Optimisation target | Single assistant | Every assistant on the device |
Caption: The shift from single-assistant to multi-assistant discovery on Android, based on the Commission's 16 July 2026 specification measures.
What this means for your team
The practical takeaway is uncomfortable but simple. Your brand's presence can no longer be tuned for one assistant. In my opinion, structured, machine-readable content becomes the shared currency, because each assistant needs the same clean signals to answer a query well.
- Audit your schema and structured data now, since it feeds every assistant, not just Google's.
- Test how ChatGPT, Perplexity and Copilot currently describe your brand, and note the gaps.
- Prioritise clear, factual, quotable content that any model can lift with confidence.
The full Commission press release is worth reading if you want the legal framing. And if you want the wider context on how assistant audiences are already fragmenting, I looked at that in how ChatGPT's user base went global.
The concrete action: stop building for a single assistant. Start building for a device where four of them fight over the same query, and make sure your content is the cleanest answer any of them can find.
Tags