Gemini is replacing the default assistant on 2 billion Android devices.
At this very moment, EU regulators are stepping in.
On April 23, the European Commission formally advanced a Digital Markets Act (DMA) specification procedure with a clear target: requiring Google to grant ChatGPT, Claude, and other competitors the same system-level access to Android as Gemini enjoys.
Failure to comply could result in a fine of up to 10% of Alphabet's global annual revenue. Given Alphabet's size, that figure exceeds $30 billion.
What Exactly the EU Wants Opened
This is not about "allowing users to download Claude from an app store."
The EU has listed specific system features:
| Feature | Current Status |
|---|---|
| Voice activation ("Hey Google" trigger phrase) | Gemini exclusive |
| Power button wake-up | Gemini exclusive |
| System-level screen reading | Gemini only |
| Native integration with Gmail, Calendar | Gemini only |
| Always-on listening | Gemini only |
| Setting as default system assistant | Restricted |
The essence of these features: the AI assistant experience on Android is fundamentally designed for Gemini. Even if competitors are downloaded, they cannot do what Gemini can.
The European Commission's logic: being downloadable is not the same as being able to compete fairly. How can an AI assistant that cannot be voice-activated or read the screen compete with one deeply integrated into the system?
"We want to ensure the playing field is open and fair, not tilted towards a few of the largest companies."
— European Commission
Google's Response
Google's reaction is a classic defensive statement: "Android is designed to be open, and users can download any AI app from the Play Store."
This is true, but it does not address the core issue.
Users "can download" ChatGPT, but can ChatGPT be activated with "Hey Google"? Can it read the screen? Can it replace Gemini as the default system assistant? No.
"Being downloadable" and "competing on equal footing" are two different things. The EU wants the latter.
Timeline and Penalty Mechanism
The timeline for this matter:
| Date | Event |
|---|---|
| January 27, 2026 | European Commission initiates two specification procedures |
| April 16, 2026 | Search data sharing specification published |
| May 1, 2026 | Public consultation period ends |
| July 27, 2026 | Final binding decision must be issued |
July 27 is a hard deadline. Not "expected," but a legally mandated period.
Penalty mechanism:
- First violation: 10% of global annual revenue (over $30 billion for Alphabet)
- Repeat violation: 20%
- Severe cases: Possible forced business divestiture
This is not a soft suggestion; it is a legally binding administrative order.
The EU has a track record of enforcement. In 2024, the EU already found Google in violation of the DMA for self-preferencing in search results. This is the second encounter, and the pressure is greater.
Why This Matters
Google controls approximately 65% of the mobile operating system market in Europe.
This means: in Europe, the phone in your hand is likely Android, and the AI assistant ecosystem on Android is currently dominated by Gemini.
If the EU's specification is implemented:
- Siri will not be affected (Apple's ecosystem is independent)
- The beneficiaries are OpenAI and Anthropic, whose assistants could gain true system-level access
- Google needs to complete engineering changes by the end of July
For OpenAI and Anthropic, this is a ticket to the system layer of 2 billion Android devices, granted by regulators from the outside.
Google can appeal, but an appeal does not suspend enforcement. And Google has already lost once on the search self-preferencing case, so the pressure is now even higher.
Broader Implications
Frankly, this is technically challenging.
Integrating different AI assistants into the system involves permission management, security sandboxes, device manufacturer agreements... It's not that Google cannot open up; it's that the cost and complexity of doing so are significant.
But the EU has clearly made up its mind: "It's hard to do" is not a reason to avoid compliance.
In essence, the EU is playing an interesting game this time:
It's not about making Google pay money; it's about making Google's competitors able to compete head-on with Google on Google's own operating system.
We'll see the outcome by the end of July.
Sources: CocoLoop, EU prepares to force Google to open Android to ChatGPT and Claude under Digital Markets Act (The Next Web, April 23, 2026); Google Faces EU Pressure to Open Up Android to Gemini Rivals (Bloomberg, April 23, 2026); The EU tells Google to give external AI assistants the same access to Android as Gemini has (Engadget, April 23, 2026)