Skip to content
On this page

A2UI Roadmap and Release Status

Evidence-based status of A2UI v0.8, v0.9.1, the v1.0 candidate, renderers, and integration work.

Updated: 8/6/2026 Reviewed by: HIA2UI editorial team v0.9.1 / v1.0 candidate

Roadmap and release status

This page records published upstream work, not predicted delivery dates. A proposal, pull request, or roadmap item is not a production release.

Status on 6 August 2026

TrackStatusProduction guidance
v0.8LegacyMaintain only where a product integration still requires it.
v0.9.1Current production linePin the schema and renderer version; use application/a2ui+json.
v1.0Candidate designPrototype behind a compatibility boundary; do not promise final wire compatibility.

See the version status guide for message-level differences.

Published milestones

  • The project moved to the a2ui-project GitHub organization.
  • v0.9.1 defines the current production-oriented protocol line and supported renderer packages.
  • React, Lit, Angular, and Flutter renderers are maintained in the official repository.
  • MCP Apps integration patterns now cover embedded A2UI, A2UI-over-MCP, and MCP Apps over A2A.
  • The v1.0 candidate explores initial-surface payloads, mixable catalogs, composition constraints, and explicit function-call responses.

Work still in motion

  • v1.0 schema and migration details remain subject to change.
  • SwiftUI and Jetpack Compose support should be treated as planned until an official supported release is published.
  • Product integrations can lag the protocol. Verify the version accepted by Gemini Enterprise, Google Chat, or another host before deployment.

How to plan

  1. Record the exact protocol and renderer versions in the architecture decision.
  2. Validate every inbound message and every outbound action.
  3. Isolate version conversion from product logic.
  4. Re-check the official repository, specification, and release notes before upgrading.