Case T-639/26, Alphabet and Google Ireland v Commission – Android must open to rival AI assistants
On most Android phones, a long press of the home button calls up Google’s own assistant. The Commission has decided that it must be able to call up anyone else’s as well, and Google has gone to court.
Facts
Article 6(7) of the Digital Markets Act requires a gatekeeper to allow providers of services and hardware, “free of charge, effective interoperability with, and access for the purposes of interoperability to, the same hardware and software features” of its designated operating system “as are available to services or hardware provided by the gatekeeper”. The gatekeeper may take “strictly necessary and proportionate” measures to protect the integrity of the system. On 16 July 2026, in Case DMA.100220, the Commission adopted a specification decision under Article 8(2) DMA setting out what that obligation requires of Google Android for AI services. According to the published summary, it covers features in four groups. Invocation covers the long press of the home button and always-on hotword detection. Context covers centralised access to data that apps store on the device, context-aware intelligence and ambient data. Actions on apps and the system cover structured on-device integration, screen automation and system integration. Resources cover Google’s system-level on-device models, on-device model implementation and background execution. For particularly sensitive features Google may restrict access to third parties meeting eligibility criteria. Most measures must ship in Android 18, by 1 August 2027 at the latest, and concurrent hotword detection in Android 19, by 1 August 2028. Alphabet and Google Ireland ask the General Court to annul the decision and its annex or, in the alternative, to declare Article 6(7) inapplicable under Article 277 TFEU.
Pleas in Law
According to the Official Journal notice, the applicants rely on six pleas in law:
1. First plea in law, alleging that the decision and annex impose obligations on the applicants that go beyond scope of Article 6(7) DMA (which requires access to ‘features’ of the operating system available to the gatekeeper’s services). In particular, the decision and annex err in law as to the meaning and scope of the features captured by Article 6(7) DMA.
2. Second plea in law, alleging that the decision and annex wrongly and disproportionately restrict the applicants’ ability to take legitimate measures to safeguard against the integrity risks that follow from interoperability, contrary to the second paragraph of Article 6(7) read in the context of (inter alia) Articles 6(4) and 8(1) DMA.
3. Third plea in law, alleging that the decision and annex err in law and fact and/or impose disproportionate obligations in their assessment of the role of OEMs and users in the Android ecosystem.
4. Fourth plea in law, alleging that the decision and annex err in law, are outside the Commission’s competence and fail to give adequate reasons when requiring the applicants to delegate certification processes to third parties.
5. Fifth plea in law, alleging that the decision goes beyond the remit of Article 8(2) DMA in breach of Article 291 TFEU or, alternatively, unlawfully and disproportionately interferes with rights protected by the Charter of Fundamental Rights. In the alternative, Article 6(7) DMA impermissibly delegates legislative powers to the Commission and unlawfully and disproportionately interferes with rights protected by the Charter of Fundamental Rights.
6. Sixth plea in law, alleging that the specification proceedings leading to the decision suffered from important procedural defects that infringed the applicants’ rights of defence.
Sources
OJ notice C/2026/5907 (EUR‑Lex) · Case file on CURIA · Summary of the Commission decision in DMA.100220 (OJ C/2026/5428) · Regulation (EU) 2022/1925 · Apple v Commission, T‑354/25 (OJ notice)
Comment
The first plea is the one on which the rest depend. Article 6(7) speaks of “features” available to the gatekeeper’s own services. Some items in the decision are features in the ordinary sense, such as the home-button shortcut. Others look more like Google’s products: the on-device models, of which the summary gives Gemini Nano as an example, which third parties are to use “as available to Alphabet’s own services”. There is also data from Google’s own apps, which Google must provide to other assistants when it makes such data available to Gemini. Whether a model or a data feed is a “feature … accessed or controlled via the operating system” is a question the DMA did not answer in terms. The answer will decide how far interoperability can reach into what the gatekeeper has built on top of the system.
The second and third pleas concern who controls the risks. The DMA allows integrity measures that are “strictly necessary and proportionate”, and the decision lets Google restrict the most sensitive features to eligible third parties. Google says the Commission has nevertheless limited those measures too far and misjudged the place of manufacturers and users in Android. That links to the fourth plea, against a requirement to hand certification to third parties. Assistants that can read the screen and act in other apps are exactly where security arguments are strongest, and where the Commission will have to show that its limits are no more than necessary.
The fifth plea and the alternative claim under Article 277 TFEU go furthest. They argue that if Article 6(7) permits this decision, it delegates legislative choices to the Commission and disproportionately restricts Google’s rights under the Charter. Apple made the same argument in 2025 against the specification decisions on iOS of March 2025 (T‑354/25 and T‑359/25), which are still pending. The General Court will therefore have two gatekeepers asking it to decide whether Article 6(7) is valid.