Europe’s Android AI assistant choice now has a release clock

An AI assistant can look like a chat box. On a phone, its real advantage sits much deeper: the wake word, the home-button press, the screen context, the power to act inside another app and the right to keep working in the background.

The European Commission has now put a release clock on that deeper access. On 16 July, it adopted binding measures requiring Google to make eleven Android capabilities available to competing AI services under the Digital Markets Act. The goal is not simply to let another chatbot appear in an app drawer. It is to let a user-chosen assistant reach the same operating-system building blocks that make Google’s own services useful across the device.

Nothing new has appeared on EU phones because of the decision yet. The Commission says most measures must arrive in Android 18, with 1 August 2027 as the latest deadline. Its press release says users should start benefiting from July 2027. One technically harder piece, allowing more than one service to listen concurrently for its own wake word, is due in Android 19 and no later than 1 August 2028.

That distinction keeps a future platform change from being mistaken for a current product feature. The decision is legally binding, but Google still has to design, document, test and release the interfaces. Alternative assistant providers will then have to build against them. A rule can open a door without guaranteeing that every service walks through it.

The eleven capabilities fall into four practical groups.

The first is invocation. A third-party service should be able to respond when a user long-presses the central home button or navigation handle, rather than leaving that access point reserved for a Google service. It should also be possible to activate an alternative assistant with a chosen wake word while the screen is off or the phone is in battery-saving mode. Concurrent wake words come later, so the 2027 change should not be read as an immediate promise that several assistants can always listen side by side.

The second group is context. With permission, an assistant could use information that apps have chosen to store and share on the device, draw on screen or sensor context, and offer relevant suggestions without waiting for a fresh prompt. The Commission gives examples such as surfacing a flight number during a conversation or providing live translation. This is also the most privacy-sensitive part of the plan.

The measure does not say that any downloaded assistant may silently inspect everything on a phone. Apps decide which data and actions they make available, users must consent to access, and existing EU privacy and cybersecurity rules still apply. For particularly sensitive capabilities, Google may use objective and non-discriminatory eligibility conditions. Independent certification is built into the planned route for restricted features such as screen automation, system integration and central access to shared on-device app data.

The third group is action. An assistant should be able to use structured integrations to send a message, create a note or schedule a meeting in an app that supports the task. Screen automation could handle a multi-step job in a separate virtual window, while system integration covers ordinary controls such as brightness, media, do-not-disturb mode and Bluetooth. The final measures also name Google apps including Gmail, Calendar, Drive, Docs, Maps, YouTube, Messages and Phone for access through operating-system integration channels.

This is where assistant competition becomes visible. A service that can answer a question but cannot complete a permitted action remains a chatbot beside the phone, rather than an assistant inside it. The EU decision is trying to make the second route technically possible without declaring which provider will offer the best, safest or most useful version.

The fourth group is computing access. Competing services should receive equal access to system-level on-device models, be able to install and run their own on-device models under comparable conditions, and receive fair access to background execution. Local models can reduce latency, work without a network for some tasks and keep some processing on the device, but the decision does not make every AI request local or private by default. That still depends on the service, task, settings and consent.

Google must provide the interoperability solutions free of charge, publish complete documentation and APIs where needed, offer technical assistance and let developers test beta implementations. Future additions to the covered features must become available to third parties no later than they become accessible to Google’s own services on the same device. Phone makers may still customise Android and differentiate their devices, provided those changes do not obstruct effective interoperability.

There is also a monitoring trail. Google must submit an initial implementation report, report monthly until the deadlines, notify the Commission before public releases and continue with periodic reporting after implementation. The specification process does not itself find that Google broke the law or impose a fine. It sets out how the existing Android interoperability duty should work.

A separate decision adopted on the same day concerns anonymised Google Search data for competing search engines and eligible AI chatbots with search functions. That is a different opening, with its own privacy controls, price formula and January 2027 timeline. It should not be confused with the Android device features.

For an EU Android user, the useful test will arrive later than the headline. Can a preferred assistant be invoked from a familiar physical or voice shortcut? Can it complete a task in a chosen app without awkward detours? Are permissions understandable, and can access be refused or withdrawn? Does an alternative work across handset brands, rather than only on one showcase device?

The decision answers the platform question more clearly than the product question. It says the system doors must open on a timetable. Which assistants earn a place on the other side will depend on implementation, developer work and user trust.