Android · AI interoperability

The EU opens Android AI assistants to competition — user choice could become more meaningful

The European Commission adopted binding measures for Google on 16 July that are intended to give third-party AI assistants access to 11 important Android functions. The decision could enable alternatives with deeper integration than a standalone app, but users should not expect the new capabilities to appear immediately.

A generic smartphone connects several AI assistants to voice, apps, context and privacy controls

What did the Commission decide?

The binding specifications under the Digital Markets Act require Google to provide competing AI services with effective and free interoperability with key Android hardware and software features. The Commission says Android serves around 60% of European mobile users, making technical access important to meaningful assistant competition.

Which capabilities are covered?

The decision covers 11 features in four groups: invoking an assistant through a custom wake word or button, understanding user context from apps, sensors and the screen, performing actions in apps and the operating system, and using the necessary hardware and software resources. Examples include drafting an email, adding shopping-list items and booking a taxi.

Why does this matter to users?

Choosing an AI assistant has often meant choosing a separate app. Deeper interoperability could make an alternative a genuine system assistant that starts naturally and works across the user's preferred apps. Competition could also improve language support, privacy choices and service quality.

Privacy is not automatic permission

The Commission emphasises explicit user consent. Access to screen content, app data, the microphone or actions must not become a blanket permission for a third-party assistant. The GDPR, Cyber Resilience Act and other EU privacy and security requirements continue to apply.

What should users do now?

Do not replace a phone because of this decision. Wait for Google's implementation timetable and assistant-specific releases, then check which data each service processes on the device and in the cloud. When new permissions arrive, grant only what a task needs and test confirmation steps for messages, purchases and other irreversible actions.

Sources