For most of Android's history, "Hey Google" has had no real rival on the phone itself. That changes, at least on paper, under two binding orders the European Commission adopted on July 16, 2026. Under the Digital Markets Act (DMA), Google must now give competing AI assistants, including OpenAI's ChatGPT and Anthropic's Claude, "equally effective access" to the same Android capabilities it has reserved for its own Gemini assistant, and must share anonymized Google Search data with rival search engines and AI chatbots. The orders are not guidance or a warning. They are enforceable decisions, and they came after six months of formal specification proceedings the Commission opened on January 27, 2026.
Gemini
AnthropicHow a "gatekeeper" ends up with a binding order
The DMA does not regulate every large tech company the same way. It first designates specific firms as "gatekeepers" for specific "core platform services," based on size, control over a gateway between businesses and users, and an entrenched market position. The European Commission made its first such designations on September 6, 2023, naming six gatekeepers, Alphabet, Amazon, Apple, ByteDance, Meta and Microsoft, across 22 core platform services. Alphabet's list includes Android, Google Search, Chrome, Play, Maps, Shopping and YouTube.
Designation alone does not spell out every obligation in technical detail. When the Commission decides a gatekeeper's own compliance plan does not meet the law's interoperability or data-access requirements, it can open a "specification proceeding" and, at the end, issue a binding decision that defines exactly what compliance looks like. That is the mechanism behind the July 16 orders: one proceeding on Android interoperability for AI services, one on access to Google Search data, both concluded on the same day.
What Google must actually change
The Android order requires Google to grant rival AI assistants equally effective access to 11 defined capabilities across four categories, according to the Commission's DMA developer portal and reporting from TechTimes and Gadget Hacks: invocation (custom wake words, a long-press home-button or navigation-handle trigger, Circle to Search-style integration), context (centralized access to on-device app data, proactive suggestions, keyboard-level AI inputs), actions (autonomous control of installed apps and OS-level settings such as brightness or Do Not Disturb), and access to resources, covering both system services and processing resources such as on-device machine-learning models.
11 Android capabilities, 4 categories
The Commission's decision defines these as the building blocks any Android AI assistant needs to compete with Gemini on equal footing.
- Custom wake words for voice activation
- Long-press home button / navigation-handle trigger
- Circle to Search-style integration
- Centralized access to on-device app data
- Proactive, context-aware suggestions
- Keyboard-level AI inputs
- Autonomous control of installed apps
- OS-level settings (brightness, Do Not Disturb, etc.)
- Equal access to Android system services
- On-device machine-learning models
- Sufficient hardware/software resources to run at parity with Gemini
"Equally effective access" means these capabilities, not merely app-store availability of a rival assistant.
In practice, that means a user could eventually set ChatGPT or Claude as the assistant triggered by a long-press of the home button, let it read on-screen context the way Gemini does today, and let it take actions inside other apps, rather than being limited to a chat window that cannot reach past its own app sandbox. The Search order runs in parallel: Google must share anonymized ranking, query, click and view data with eligible rival search engines and AI chatbots on fair, reasonable and non-discriminatory terms, beginning in January 2027.

The compliance runway is staggered, not immediate
None of this lands overnight. Google must ship most of the 11 capabilities with Android 18, the platform's next major release, by August 1, 2027 at the latest. One piece, letting more than one AI assistant listen for its own wake word concurrently, gets an extra year and is due with Android 19 by August 1, 2028. Search data sharing is meant to start in January 2027, ahead of the Android deadline.
From proceedings to enforceable deadlines
Six months of DMA specification proceedings compressed into two binding decisions, followed by a staggered two-year compliance runway.
- January 27, 2026Specification proceedings openedThe European Commission opens two parallel DMA specification proceedings against Google/Alphabet: one on Android interoperability for AI services, one on access to Google Search data.
- July 16, 2026Two binding decisions adoptedThe Commission adopts binding specification decisions concluding both proceedings. They take effect immediately and are enforceable, not mere guidance.
- January 2027Search data sharing beginsGoogle must start sharing anonymized Search ranking, query, click and view data with eligible rival search engines and AI chatbots on a fair, reasonable and non-discriminatory basis.
- August 1, 2027Android 18: AI assistant access opensGoogle must ship the 11 required Android capabilities to rival AI assistants at the latest with Android 18, the next major release.
- August 1, 2028Android 19: concurrent hotword detectionThe remaining piece, letting more than one AI assistant listen for its own wake word at once, gets an extra year and lands with Android 19.
Google has publicly disagreed with both decisions and may appeal; unless overturned or suspended, they remain binding on the dates shown.
Today's decisions risk undermining essential privacy and security safeguards for millions of Europeans.
Google, public statement responding to the July 16, 2026 decisions
Google has pushed back publicly on both fronts. Kent Walker, the company's president of global affairs, has argued the changes could compromise "vital privacy and security guardrails," and Sameer Samat, president of the Android Ecosystem, said the Commission "is on the wrong track" and would add "unnecessary technical complexity." Google has also pointed out that Android already lets users download any AI assistant app from the Play Store, framing the platform as "open by design." The Commission's position, articulated by EU tech chief Henna Virkkunen, is that app-store availability is not the same as system-level parity, and that the goal is fostering "emerging alternatives to Google Search and Gemini, and more choice for EU users." Whether Google appeals the decisions to the EU courts, as it is entitled to do, remains an open question as of this writing.
Why the assistant, not the browser, is the new front line
Regulators spent the DMA's first two years mostly on browser choice screens and app-store terms, because those were the visible chokepoints of the smartphone era. An AI assistant with system-level hooks is arguably a bigger one: if only Gemini can be summoned by wake word, read the screen, and act inside other apps, then no rival assistant, however capable its underlying model, can compete on the terms that matter to a phone user. That is the logic behind treating invocation, context and action access as the real battleground, rather than which chatbot app happens to be installed.
Apple offers an instructive contrast rather than a clean precedent. Facing a parallel DMA interoperability dispute, Apple chose not to launch its new Siri AI experience in the EU alongside iOS 27 and iPadOS 27, arguing it could not meet the Commission's access requirements without compromising the on-device privacy model behind Private Cloud Compute. Google, by contrast, is proceeding toward compliance while contesting the Commission's reasoning, meaning EU Android users are on track to gain assistant choice that EU iPhone users, for now, are not.
The unresolved question: does interoperability actually move market share
None of this guarantees rival assistants win meaningfully more users. Technical access to a wake word or an app-automation hook is necessary for competition on equal footing, but it is not sufficient. Gemini's advantage on Android was never purely a permissions problem; it also comes from default placement, integration polish and years of tuning against exactly these system hooks. Whether ChatGPT or Claude, once granted the same access, actually pull meaningful share away from Gemini on Android is an empirical question that will only be answered after Android 18 ships and the eligibility terms Google is required to publish (draft terms by February 1, 2027, final terms by May 1, 2027) turn out to be usable in practice rather than technically compliant but commercially unattractive. Readers should treat this as a regulatory remedy whose real-world effect is genuinely unproven, not a foregone conclusion either way.
That underlying idea, that people should be able to choose which AI assistant handles a task rather than being locked into whichever one their operating system defaults to, is also the premise behind giving people model-agnostic access to leading AI systems in one place. Metir AI takes that approach at the application layer today: instead of waiting for a phone maker's default assistant to open up, it lets people work across leading models including those from OpenAI and Anthropic in a single workspace.
The takeaway
The EU's July 16, 2026 orders are the most concrete attempt yet to regulate AI assistants the way earlier DMA cases regulated browsers and app stores: not by banning a default, but by forcing the platform holder to make switching genuinely functional rather than merely possible. The 11 capabilities and the two-year compliance runway are specific and enforceable. What they will actually do to Gemini's position on Android, and whether Google's threatened appeal changes any of it, will not be visible until the deadlines in 2027 and 2028 actually arrive.
Sources:
- Commission provides guidance to Google for AI interoperability on Android and sharing of Google Search data under the Digital Markets Act | European Commission, DMA
- Alphabet specification proceedings - Interoperability for AI services | European Commission, DMA Developer Portal
- EU Gives Rival AI Assistants System-Level Android Access Google Reserved for Gemini | TechTimes
- EU Orders Google to Break Gemini's Android Lock-In: Search Data Sharing Starts January | TechTimes
- EU prepares to force Google to open Android to ChatGPT and Claude under Digital Markets Act | The Next Web
- EU Forces Apple, Google to Open AI Assistants to Rivals | Memeburn
- EU Orders Google to Open Android to Rival AI Apps by 2027 | Gadget Hacks
- How EU's DMA puts Apple and Google on different paths for smartphone AI | Business Standard
- The European Commission designates six gatekeepers under the Digital Markets Act | Macfarlanes
Image credits
Header image: the Berlaymont building in Brussels, headquarters of the European Commission, the body that adopted the July 16, 2026 DMA decisions. Photo by acediscovery via Wikimedia Commons, licensed under CC BY 4.0. In-body photograph: Android version-themed mascot statues outside a Google building on its Mountain View campus, via Wikimedia Commons, licensed under CC BY-SA 2.0. No photograph of the unreleased Android 18 or Android 19 releases exists yet, so the image depicts the Android platform generally rather than the specific releases named in the order.
