Skip to content
On this page

A2UI in Google Products

Verified A2UI support and version limits across Gemini Enterprise, Google Chat, ADK Web, Opal, and Flutter GenUI.

Updated: 8/6/2026 Reviewed by: HiA2UI Editorial Team Product status checked 2026-08-06

A2UI in Google products

Product support does not advance at the same speed as the protocol. Verify the host’s renderer version, registration path, and preview terms before building an integration.

Enterprise chat, mobile, and web surfaces receiving validated A2UI components from a shared agent layer

Support matrix

ProductVerified roleImportant limit
Gemini EnterpriseBuilt-in native renderer for registered A2A agentsCurrent documentation states v0.8 support; managed ADK registration does not provide the same A2UI path
Google ChatWorkspace add-on quickstart using ADK and Vertex AI Agent EngineEarly Stage Public Preview
ADK WebDeveloper UI capable of rendering A2UI agent partsCurrent documented integration is based on the v0.8 basic catalog
OpalA2UI-backed dynamic UI system for AI mini-appsProduct abstractions are higher level than the public wire protocol
Flutter GenUICross-platform native renderer using A2UI underneathApplication owns transport setup; verify package and protocol compatibility

Gemini Enterprise

Gemini Enterprise can send its supported catalog to an A2A agent, validate returned A2UI, and render the result in the host design system. The production lesson is version negotiation: do not send v0.9.1 messages to a host that advertises v0.8.

Only present actions the user is authorized to perform. Confirm destructive or financial actions outside the generated surface, and never place secrets in the A2UI data model.

Google Chat

The official quickstart connects a Chat app to an ADK agent hosted on Vertex AI Agent Engine. It is useful as a deployment reference for asynchronous progress, tool-backed data, and adaptive cards. Because the feature is preview, pin dependencies and maintain a text/card fallback.

Implementation checklist

  1. Record the exact renderer version advertised by the host.
  2. Negotiate A2UI and transport capabilities before generating UI.
  3. Version the catalog and examples sent to the model.
  4. Keep text fallback and error recovery paths.
  5. Test keyboard, screen reader, small viewport, slow network, and unsupported-component behavior in the real host.

Primary references