EU orders Google to open Android AI assistant access to rivals under the DMA

The European Commission's July 16, 2026 order does not just tell Google to 'allow' rival AI assistants onto Android - it maps out precisely which system hooks have to open, and on what terms ^[1]. The Commission identified 11 specific Android feature and access points spread across four categories: invocation, contextual data from apps and device sensors, cross-app task execution, and on-device hardware and software resources ^[2].

Those 11 points split into two tiers. Six 'unrestricted' features - ambient microphone, camera, screen and sensor data, always-on hotword detection, long-press invocation, on-device models, and background execution - are open to any qualifying app immediately, no certification required ^[1]. The other five - AppSearch data access, Magic Cue-style context intelligence, App Actions and Functions, Computer Control screen automation, and system integration with settings, media, and notifications - are 'restricted' and require certification through a new Qualified AI Assistant Programme ^[1].

The result, on paper, is close to parity with Gemini: a qualifying assistant like ChatGPT, Claude, or Perplexity can register a custom wake word at the OS level, trigger itself via a long-press of the home button or navigation handle, read what's currently on the user's screen, and execute tasks inside other apps ^[3]. Those are precisely the capabilities that, until now, only Google's own assistant had by default.

Buried under the Android headlines is a second, arguably more consequential order: Google must start handing rival search engines and AI chatbot companies anonymized versions of the query, click, and ranking data that make Google Search work ^[4]. Search is the raw material that trains ranking systems and, increasingly, the AI answers layered on top of them - a resource competitors have never been able to replicate at scale.

The privacy engineering is deliberate. Records containing rare or sensitive details get suppressed, users are grouped into bundles of at least 1,000, and identifiers are stripped before anything leaves Google's systems ^[4]. Only vetted firms with a credible plan to improve search quality get access, and the arrangement is subject to independent audits and a cost-based fee model, with dataset delivery due by November 2026 and pricing terms by January 2027 ^[4].

Given that roughly 60 percent of EU users are on Android ^[5], the two orders compound each other: the same window that opens Gemini's OS-level advantage to rivals also opens the search index Gemini draws on. A rival assistant that could previously never match Google's contextual and retrieval quality now has a legal path to both.

This is not the Commission's first attempt to loosen Google's grip on Android. In 2018 it fined Google 4.3 billion euros for forcing device makers to pre-install Search and Chrome - a remedy Google later narrowed in practice, according to Yale economist Fiona Scott Morton, partly through the contractual terms it wrote into OEM agreements ^[6]. That history appears to have shaped how narrowly this order is drafted.

Scott Morton argues the Commission's decision to define Google Android's core platform service functionally - covering Google Play Services and related middleware, not just the open-source AOSP code - is a deliberate, robust choice precisely because it is harder to route around through contract language ^[6]. It is also a decision she suggests could inform how US regulators craft remedies in the parallel Google Search antitrust litigation.

The timing adds weight. Just two weeks before the July 16 decisions, the EU's top court upheld a separate 4.1 billion euro Android antitrust fine against Google, clarifying the legal standard for exclusionary abuse in digital markets ^[7]. Brussels is not treating this as an isolated Android skirmish - it is the latest entry in an eight-year campaign, and the enforcement design reflects lessons learned from the ones that came before.

Google's opposition is not just corporate posturing - it names a real tension the order does not fully resolve. Kent Walker, Google's President of Global Affairs, says the decision 'threatens device security by granting external apps sensitive and powerful device permissions' ^[1], and warns that sharing anonymized search data could still expose Europeans' information to companies users have never heard of.

A more structural version of that critique comes from ECIPE, the Brussels-based trade policy institute, which argues the rule's biggest problem isn't the access it grants today but the incentive it sets going forward: 'If new AI capabilities must be made available to rivals at the moment of deployment, they become less proprietary from the outset' ^[8]. That, ECIPE argues, could push Google to build fewer distinctive Android features rather than more, since anything genuinely new has to be shared with competitors as soon as it ships.

ECIPE's sharper warning is architectural: collapsing Android's varied access levels into one certification standard risks forcing Google to centralize security governance across all Android device makers, trading today's diversity of OEM security implementations for a single point of failure ^[8]. Whether that risk is real or overstated will not be testable until the Qualified AI Assistant Programme actually starts certifying apps in 2027.

The compliance clock is specific and unforgiving. Google must begin sharing anonymized search data with rivals from January 2027, Android-side changes are expected to start reaching users from July 2027, and full compliance is required by August 1, 2027, timed to Android 18 ^[4]. Certification terms for the restricted-feature tier are due even earlier, by February 1, 2027.

The stakes for missing those dates are unusually high. DMA non-compliance can trigger fines of up to 10 percent of a company's total global annual turnover ^[4]- for Alphabet, an order of magnitude larger than any EU penalty issued to date. For comparison, the previous DMA fine record was 500 million euros against Apple and 200 million euros against Meta, both from April 2025 ^[9], and the EU's top court had just upheld a separate 4.1 billion euro Android fine against Google days before this order ^[7].

These specification decisions are also distinct from, and additional to, a separate, ongoing DMA non-compliance investigation into Google Search self-preferencing and Play Store anti-steering, which was expected to produce its own penalty in the hundreds of millions of euros around the same period ^[1]. Google is not just being told to open Android; it is doing so under the shadow of parallel enforcement that has already cost it billions.