EU Orders Google to Open Android to AI Rivals and Share Search Data

The European Commission has directed Google to provide rivals including OpenAI with access to 11 key Android features and to share anonymised search data used to train and optimise services. This action stems from specification proceedings under the Digital Markets Act rather than a fresh antitrust investigation.

The measures require Google to enable rival AI assistants to interoperate with Android hardware and software functions on terms comparable to those available to its own Gemini service. They also compel the company to supply search competitors with ranking, query, click and view data on fair, reasonable and non-discriminatory terms. Both obligations aim to reduce the data and platform advantages that the Commission has long identified as barriers to competition.

The Commission opened two parallel specification proceedings against Google on 27 January 2026. One proceeding addressed Android interoperability for third-party AI services; the other addressed access to search-related data. On 16 July 2026 the Commission announced the outcomes of those proceedings, setting implementation deadlines of July 2027 for the Android changes and January 2027 for data sharing.

Reporting indicates the Android decision covers voice activation, system-level access and the ability to perform actions inside third-party apps such as sending emails, booking restaurants, ordering food and sharing photos. The search-data obligation applies to anonymised datasets that Google has previously used to refine its own ranking and generative-AI models. The Commission stated that the purpose is to level a playing field where Google controls data volumes competitors cannot replicate.

Earlier EU enforcement already required Google to present users in Europe with choice screens offering five search applications and five browsers. Those screens were implemented after the Commission found that Google had imposed pre-installation requirements and payments to secure default placement for its services. The new DMA measures build on that record without reopening the underlying infringement findings.

What the policy says

The specification decisions require Google to grant rival AI assistants and services access to 11 Android features on equivalent technical and commercial conditions to those provided to Gemini. They further oblige Google to share anonymised search query, click, view and ranking data with competing search engines and, according to some reports, AI chatbot providers. Implementation timelines are fixed: Android interoperability changes must be delivered by July 2027 and search-data access must begin by January 2027.

The obligations are framed as binding instructions issued after the specification proceedings that commenced on 27 January 2026. They do not constitute new findings of infringement but rather detailed compliance directions under the Digital Markets Act. Google must therefore redesign certain Android interfaces and establish data-access mechanisms that satisfy the fair, reasonable and non-discriminatory standard.

What it means in practice

In practice Google will need to expose voice-trigger APIs, notification channels and in-app action capabilities so that third-party assistants can operate with parity to Gemini. Device manufacturers and operators will face revised integration requirements, while rival developers will receive documented access terms previously reserved for Google’s own services. Search competitors will gain structured feeds of anonymised user-interaction data that can be used to train ranking models or generative-AI features.

Because the measures are DMA specification decisions rather than infringement decisions, they carry immediate compliance force without requiring a further administrative procedure. Google retains the right to propose specific implementation methods, yet the Commission retains oversight to verify that the chosen methods meet the equivalence and non-discrimination standards.

Who this affects

Android device manufacturers operating in the European Economic Area must accommodate the new interoperability interfaces in software updates scheduled for 2027. AI-assistant developers, including OpenAI and smaller European entrants, gain a regulatory route to deeper device integration. Search-engine operators receive a defined channel for data that previously remained proprietary.

Outside Europe the effects are indirect but material. Product changes made for the EU market frequently propagate to global Android builds, including those shipped on low- and mid-range devices common in African markets. Local startups building voice-enabled services or alternative search tools may therefore encounter more open platform conditions earlier than they otherwise would.

For founders building AI assistants or search products the decisions lower the technical and data barriers that previously favoured the incumbent. Operators already licensed under the DMA must now incorporate these access obligations into their compliance programmes and monitor the Commission’s verification process. Investors evaluating exposure should note that the measures apply only to designated gatekeepers and that implementation costs will be borne primarily by Google rather than by downstream licensees.

Implementation gaps remain. The precise list of the 11 Android features has not been published in full, and the technical specifications for data-access interfaces are still under negotiation. It is also unclear whether the data-sharing obligation extends to real-time query streams or only to historical anonymised datasets, and whether non-EU regulators will adopt similar requirements.

Google may propose alternative compliance methods that the Commission must accept or reject. The outcome of those negotiations will determine the practical scope of access granted to rivals. No public consultation window has yet been announced for the detailed implementation plans.

Market participants should monitor the Commission’s expected follow-on guidance on data-access formats and the July 2027 Android compliance milestone. Any enforcement action arising from non-compliance will provide further clarity on the practical reach of the specification decisions.