Skip to main content
European Commission logo
Digital Markets Act (DMA)

DMA.100220 – Consultation on the proposed measures for interoperability with Google Android (Article 6(7) of the DMA)

The Commission is consulting third parties on the draft measures that Alphabet must implement to ensure effective interoperability with AI services on its Android operating system (Google Android), as required by Article 6(7) of the DMA.

  • Consultation
  • Closed

Details

Status
Closed
Opening date
Deadline

Target audience

All citizens, companies and organisations are welcome to contribute to this consultation. The Commission especially welcomes contributions from companies with first-hand experience on issues concerned by these proceedings, such as those providing Artificial Intelligence (AI) services on Android smartphones and tablets or Original Equipment Manufacturers (OEMs) whose mobile devices are powered by Google Android. 

Why we are consulting

The DMA is a European legislation that aims to make digital markets fairer and more open. The DMA applies to gatekeepers, which are companies operating large digital platforms that play an important role in the digital economy and act as gateways for other companies to access end users. Alphabet is one of such gatekeepers in relation to the Google Android mobile operating system. 

Amongst others, the DMA requires gatekeepers to provide interoperability with and access to software and hardware features of designated operating systems. To assist Alphabet in enabling such interoperability, the Commission opened proceedings on 27 January 2026 to specify measures that Alphabet must implement to comply with its interoperability obligations under the DMA, when it comes to the features relevant for AI services. The Commission’s case reference is DMA.100220

The procedure focuses on interoperability with key capabilities of Google Android, such as:

  • the ability of users to invoke AI-powered services via wake words;
  • the possibility of AI-powered services to effectively interact with users’ applications to understand their context and execute tasks on their behalf;
  • access to the necessary hardware and software resources for AI-powered services to be reliable and responsive. 

On 27 April 2026, the Commission addressed its preliminary findings to Alphabet, including the draft measures that Alphabet must take to ensure effective interoperability with Google Android. A Case Summary and the Annex containing the draft measures are available in the Reference documents section below. 

The Commission is now seeking feedback from interested parties on the proposed measures found in the Annex containing the draft measures. The Commission’s measures cover four main themes, and a set of general measures:

  1. Features for invocation. The proposed measures address the capabilities to invoke AI services via their own customised wake word. In addition, the draft includes proposed measures to allow third party apps and services to be invoked via the system-wide access points long press on the home button or navigation handle. Those services should also receive contextual data to offer enhanced capabilities, such as translating text or searching for information on screen.
  2. Features for context. The proposed measures address the possibility of AI-powered services to access, in a centralised manner, apps’ data stored on-device. The proposed measures also envisage the following possibilities: allowing any third-party application to contribute to and surface proactive suggestions; allowing AI-powered services to access the features required to offer their own innovative use cases, like proactive suggestions on keyboards. Those AI-powered services should get access to necessary inputs (for instance, audio or screen content), processing resources (for instance, models that can process and interpret the input) and display surfaces.
  3. Features for actions on apps and the operating system. The proposed measures aim to ensure that AI-powered services can integrate with the applications on the user’s device and perform tasks within these applications. Third-party AI services should also be able to autonomously control the user’s installed applications. Furthermore, the proposed measures aim to enable seamless integration with the operating system and its settings, such as changing the display brightness or enabling do not disturb mode.
  4. Features for access to resources. The proposed measures aim to ensure that AI-powered services can execute tasks with high levels of performance, availability and responsiveness. The proposed measures aim to ensure that the on-device models which are part of the system are available to all third parties, and that third parties can use their own on-device models on Android devices in an effective manner to offer innovative services to users.
  5. General measures for all features. Alphabet will have to ensure that interoperability is offered free of charge on all Google Android devices, including those offered by original equipment manufacturers (OEMs), through complete and well-documented frameworks and APIs. Alphabet will also have to ensure that all apps, including user-installed and pre-installed apps, have equal access to the features without requiring more cumbersome system settings or user friction. Furthermore, Alphabet will have to make new functionalities available to third parties, offer technical assistance to ensure effective implementation of these measures and report how it implemented the measures.

A more comprehensive summary is available in the Case Summary document (available in the Reference documents section below).

In particular, the Commission seeks views on the technical aspects of the measures:

  • The effectiveness of the measures in practice: if implemented, will the proposed measures result in effective interoperability with Google Android for competing AI service providers in a sense they will have effective access to features required to offer competitive AI services to Google Android users?
  • The completeness of the measures: is there anything else needed to ensure effective interoperability with any individual feature? Are there any other implementations possible?
  • The integration effort concerning the measures: are the proposed measures feasible to implement for a third party, such as a third-party provider of AI services, in a sense they can integrate the feature into their service?
  • Timelines: is the proposed timeline for Alphabet to implement each proposed measure achievable? Is the proposed timeline for Alphabet to implement each proposed measure suitable for third parties, including providers of AI services, to remain competitive and keep pace with the rapidly evolving innovation taking place in the digital space?

The Commission will carefully assess the feedback provided by interested third parties and Alphabet. The input received may result in adjustments to the proposed measures and will feed in the Commission’s decision making the measures legally binding on Alphabet. The Commission will adopt a final decision by 27 July 2026 (within six months of opening the proceedings).

Respond to the consultation

The response period for this consultation has ended. Thank you for your input.

Reference documents

  • 27 APRIL 2026
DMA.100220 - Case Summary - Google Android - interoperability
  • 27 APRIL 2026
DMA.100220 - Annex (draft measures) - Google Android - interoperability

Additional information

What is a specification procedure?

Specification proceedings are an instrument to formalise the regulatory dialogue between the Commission and gatekeepers with the aim of further clarifying the obligations in the DMA.

The proceedings aim to assist the gatekeeper in their compliance effort by detailing the measures that a gatekeeper must take to effectively comply with the obligations specified in Articles 6 and 7 of the DMA. The Commission has six months to conclude specification proceedings.

The legal basis for a specification procedure is Article 8(2) of the DMA.

What are preliminary findings?

Within three months of the opening of the specification proceedings, the Commission communicates its preliminary findings to the gatekeeper, in this case Alphabet. In the preliminary findings, the Commission explains which measures it considers that Alphabet should implement and the reasoning for the proposed measures.

At the same time, the Commission makes the proposed measures and a summary of the reasoning public, and requests that third parties provide comments on the proposed measures.

Based on the feedback from Alphabet and third parties as well as further investigative steps, the Commission then may adjust the proposed measures. Within six months from the opening of the specification proceedings, the Commission shall adopt its final decision with the binding measures for Alphabet.

The legal basis for preliminary findings is Articles 8(5) and 8(6) of the DMA.

Why must my contribution be non-confidential towards Alphabet?

The Commission can only rely on non-confidential submissions to reason the final decision in the specification proceedings. In addition, the consultation feedback must be made available to Alphabet so that it can express its views on third-party input and consider it when developing interoperability solutions. Therefore, it is important that contributions are non-confidential.

Will my contributions be made public?

Your contribution will not be made public. Alphabet will be granted access to your contribution, to allow them to provide feedback on your contribution. The Commission may reference your contribution in its final decision making the measures legally binding on Alphabet.

Are there any other active specification procedures?

The Commission has also opened separate specification proceedings in relation to Google Search data sharing with third party undertakings providing search engines.

The case reference for these other proceedings is DMA.100209.

The Commission is organizing a separate public consultation on the proposed measures in this case, which closes on 1 May 2026.

Can I submit a single contribution for the two consultations (DMA.100220 and DMA.100209)?

If you intend to make contributions relating to both cases, please submit two separate contributions according to the instructions on each consultation page. This allows the Commission to allocate your submission to the correct case file.

Where can I find more information about the Digital Markets Act?

More information about the Digital Markets Act is available on its website:

https://digital-markets-act.ec.europa.eu/index_en