Google ships A2UI 1.0 protocol for native generative UI agents
The open protocol lets AI agents render interactive screens across web, mobile, and desktop apps using standard SDKs for major frameworks.
Key points
- A2UI 1.0 enables agents to render native UI components rather than text walls.
- Open-source SDKs are available for React, Angular, Flutter, SwiftUI, and more.
- Atlassian, Bloomberg, and ByteDance are already building with the protocol.
Google released A2UI 1.0 on its Developers blog, marking the first stable version of an open protocol for generative user interfaces.reported The release allows AI agents to generate interactive screens across web, mobile, and desktop applications instead of relying on text-only responses.This update lets AI assistants show buttons and forms instead of just text.The protocol decouples agent logic from UI rendering, enabling native component usage.
What was released or claimed
The protocol introduces bidirectional function calls, swappable inference formats, and secure data binding. Developers can integrate these features using open-source renderer SDKs for React, Angular, Lit, Flutter, SwiftUI, and Jetpack Compose. Agent SDKs are also available for Python, TypeScript, and Dart to facilitate backend integration.
Who it affects
Data science and engineering teams building agentic applications are the primary audience. The blog post noted that companies including Atlassian, Alation, Bloomberg, and ByteDance are already developing solutions using this framework. These organizations aim to replace static text outputs with dynamic, native interface elements.
What is still unknown
The material does not specify performance benchmarks or latency metrics compared to existing solutions. It is also unclear how widespread adoption will be outside the named early adopters. The blog post does not detail pricing models or enterprise support tiers for the open-source components.
The takeaway
The shift from text-based agent interactions to native UI rendering aims to improve user experience and security. By keeping sensitive data on the server and using native components, the protocol seeks to maintain high trust and low latency. This approach allows agents to adapt to user needs while adhering to brand design systems.
What changes for users
Users will see agents that construct personalized, interactive UIs adapting to unique preferences. Applications render content securely at native speed, ensuring consistent fidelity whether accessed via a company app or third-party assistants like Gemini or Claude. Sensitive values remain on the server, preventing exposure to the model during UI generation.
Why it matters
- Teams can leverage existing design systems, reducing the need to build custom UI layers for AI agents.
- Secure data binding ensures sensitive information stays on the server, addressing privacy concerns in generative UI.
- Support for major frameworks like React and Flutter lowers the barrier to entry for integrating agentic experiences.
- The protocol enables consistent user experiences across different platforms and third-party AI assistants.
Topics: generative UI, AI agents, Google, SDKs, open source
Updated
Then / now / next
AI agents primarily responded with text walls, requiring multiple rounds of clarification.
A2UI 1.0 allows agents to render interactive, native screens for immediate user action.
Watch for broader adoption beyond the initial cohort of companies like Atlassian and Bloomberg.
Story timeline
- Then AI agents primarily responded with text walls, requiring multiple rounds of clarification.
- 11 Nov 2026 A2UI 1.0: Build delightful, fast, reliable, agentic experiences
- Now A2UI 1.0 allows agents to render interactive, native screens for immediate user action.
- Next Watch for broader adoption beyond the initial cohort of companies like Atlassian and Bloomberg.
For readers
Developers
- Use open-source renderer SDKs for React, Angular, Lit, Flutter, SwiftUI, and Jetpack Compose.
- Implement secure data binding to keep sensitive values on the server.
Business
- Leverage native components to maintain brand consistency across agent interactions.
- Reduce user friction by replacing text-heavy responses with interactive forms and charts.
Researchers
- Study the impact of bidirectional function calls on agent reliability and latency.
- Analyze the security implications of server-side UI composition versus client-side rendering.
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
Which programming languages are supported by the agent SDKs?
The agent SDKs support Python, TypeScript, and Dart for backend integration.
Can A2UI be used with third-party AI assistants?
Yes, the protocol works with assistants that host MCP apps, such as Gemini or Claude.
Is A2UI 1.0 a stable release?
Yes, Google describes it as the first stable version of the open protocol.
Connected stories
Reading receipt
- A2UI 1.0 enables agents to render native UI components rather than text walls.
- Open-source SDKs are available for React, Angular, Flutter, SwiftUI, and more.
- Atlassian, Bloomberg, and ByteDance are already building with the protocol.
Still open: How will the community contribute to the open-source renderer SDKs?
Still open: What are the specific security vulnerabilities addressed by the secure data binding?
