Your Next Android Assistant Might Not Be Google
The EU’s new rules on Android, explained
If you use an Android phone in Europe, the assistant button is about to get crowded.
On July 16, 2026, the European Commission issued two binding specification decisions to Google under the Digital Markets Act. One covers AI assistants. The other covers search data.
Both aim at the same thing: making it possible to compete with Google on Google’s own platform.
What actually changed?
Today, rival AI assistants on Android only get restricted access to core operating system features. Google’s own Gemini does not have that problem.
The Commission is blunt about the consequence. Alternative assistants are not competing on an equal footing, which makes them less attractive to the 60% of EU users who are on an Android device.
Three practical things change. You will be able to activate your preferred assistant by voice, the way “Hey Google” works now. That assistant will be able to perform actions inside your apps. And it can use on-device context to do it.
The Commission’s own examples: booking a taxi, suggesting replies in a chat app, answering a question about a place you just visited.
Why the search data half matters more than it sounds
The second decision is less flashy and possibly more consequential.
Google has been required to share search data with rival search engines for a while. The Commission says the offer has been ineffective in practice, so this decision spells out how it should actually work.
Two details stand out. AI chatbots that offer search functionality now explicitly qualify to receive the data. And subject to anonymisation, Google should share the same data it collects to optimise its own search.
Get Haru Kim’s stories in your inbox
Join Medium for free to get updates from this writer.
The anonymisation method is multi-layered and was built in line with the draft joint guidelines from the Commission and the European Data Protection Board. Google can still refuse a specific third party if it flags a serious security or data protection risk.
Is this a real opening, or a paperwork exercise?
Fair question. The DMA has teeth on paper: non-compliance can cost up to 10% of a company’s global annual turnover, and up to 20% for repeated violations.
But a specification decision is guidance on how to comply, not a fine. Timing is the thing to watch, and reportedly the Android-side changes arrive with the platform’s next major release rather than as an immediate update.
So the honest read is this. The rules are set. The ship date is the open question.
If you want the other half of the EU’s AI push, I wrote about the AI Act timeline here: https://medium.com/p/09b4cd105742
Does any of this reach you outside the EU?
Not automatically. These are EU obligations, tied to EU users.
But platform changes rarely stay geographically neat. Once the hooks exist in Android for one region, maintaining two versions of the OS gets expensive.
That is roughly what happened with USB-C on iPhones. It is a reasonable guess here, not a promise.
What this means
If you are in the EU, expect a choice you have not had before: a non-Google assistant that works at the system level, not just inside its own app.
If you are not, watch Android’s next release notes. The interesting question is not whether the EU won. It is whether Google builds this once or twice.
Sources
European Commission, “Commission provides guidance to Google for AI interoperability on Android and sharing of Google Search data under the Digital Markets Act,” 16 July 2026: https://digital-markets-act.ec.europa.eu/commission-provides-guidance-google-ai-interoperability-android-and-sharing-google-search-data-under-2026–07–16_en
European Commission press release IP/26/1634: https://ec.europa.eu/commission/presscorner/detail/en/ip_26_1634
Digital Markets Act, Regulation (EU) 2022/1925, penalties: https://digital-markets-act.ec.europa.eu/about-dma/legislation_en
