The EU Just Ordered Google to Let Rival AI Assistants Onto Android
Key takeaways
- EU regulators have told Google to open Android so phone makers and users can set a rival AI assistant, not just Gemini, as the default.
- The ruling lands in the same week reports suggested Gemini slipped again on a key benchmark.
- Defaults decide who gets the queries on mobile, and queries are what train and improve an assistant over time.
- The order is EU specific for now, but it is one of the most direct regulatory levers pulled on AI assistants so far and other regulators are watching.
Android ships on roughly seven in ten smartphones worldwide, and until now Gemini has sat in the one seat that matters most on the device: the default assistant slot. EU regulators have just told Google that seat has to be open to rivals, meaning phone makers or users themselves will be able to set a different AI assistant as the default rather than Gemini alone.
The mechanics of default settings sound boring until you notice how much they decide. Most people never change a default. Whatever answers when you hold the home button or say the wake word is the assistant that gets used, day after day, without a second thought. That is not a minor UX detail, it is the entire competitive battlefield for AI assistants on phones. An assistant nobody opens does not improve, does not get funded, and eventually does not exist. An assistant sitting behind the default slot gets a torrent of real world queries that make it better and justify further investment. Forcing that slot open changes who gets to compete for that flywheel at all.
The timing adds an edge to this. The ruling arrived the same week reports suggested Gemini had slipped again on a key benchmark, the kind of detail that would normally pass as a minor technical footnote. Paired with a regulatory order forcing Google to share the default slot, it reads differently: Google now has to defend Gemini's position on merit, in an open competition for the assistant slot, at a moment when its technical edge is reportedly being questioned. That is a much harder position than quietly holding the default by platform ownership alone.
Google will not enjoy this, and Android device makers will now have real leverage to negotiate. A phone manufacturer could set a different assistant as the shipped default in exchange for a better deal, or offer users a genuine choice screen at setup, the way EU rules have already forced for search engines and browsers on Android in the past. Expect Google to comply narrowly and slowly, the same pattern seen with earlier EU platform rulings, while rivals push for the broadest possible interpretation of what "default" and "rival assistant" actually cover.
Scope matters here too. This order applies to the EU market specifically, not globally, and Google's compliance is likely to be geofenced rather than rolled out everywhere at once. But EU digital rulings have a track record of setting a template other regulators later borrow from, on subjects ranging from app stores to browser choice screens. A regulator in the UK, South Korea or elsewhere watching Brussels force open the AI assistant default is not watching in isolation.
Step back and the pattern is clear. Governments spent the early AI era mostly reacting to model capability and safety questions. This is something else: a structural intervention into who controls the doorway users walk through to reach any AI assistant at all. If it works as intended, the AI assistant market on mobile stops being a story about whoever ships inside the operating system, and starts being a genuine competition for the default slot itself.