A2UI Official Website Launches: Your Complete Getting Started Guide

Great news for the developer community: a2ui.org is now live! Google’s official A2UI website provides a central hub for documentation, specifications, and getting started resources.

In this article, we’ll walk you through what you can find on the site and how to take your first steps with A2UI development.

[!IMPORTANT] Update (January 2026): A2UI is now officially Open Source! This article covers the initial website launch preview. For the latest details on the official public release, reference implementation, and open source repository, please read our new feature story: A2UI Officially Open Sourced.

What is a2ui.org?

a2ui.org is the official home of the A2UI project. It serves as:

The canonical source for the A2UI specification.
A documentation hub for developers building A2UI clients or agents.
A community gateway linking to GitHub, Discord, and contribution guidelines.

Pro Tip (E-E-A-T): Always reference a2ui.org for the latest spec. Third-party tutorials may become outdated as the protocol evolves towards v1.0.

Key Resources on a2ui.org

1. The A2UI Specification

The core JSON schema that defines how agents describe UI components. This is the single source of truth for:

Component types (button, form, datePicker, etc.)
Action definitions (what happens when a user interacts)
State management patterns

2. Client Renderer Libraries

Official libraries to render A2UI JSON in your application:

Platform	Library	Status
Flutter	`a2ui_flutter`	✅ Stable
Angular	`@a2ui/angular`	✅ Stable
Web (Lit)	`@a2ui/lit`	✅ Stable
React	`@a2ui/react`	⏳ Q1 2026

3. Agent Integration Guides

Step-by-step tutorials for integrating A2UI into your AI agents, whether you’re using:

Vertex AI Agent Builder (See our dedicated article)
LangChain / LangGraph
Custom LLM pipelines

4. Security Best Practices

A dedicated section on why A2UI uses JSON and how the component catalog model prevents UI injection attacks.

Getting Started: Your First A2UI Agent

Here’s a minimal example of what an A2UI JSON payload looks like:

{
  "components": [
    {
      "id": "greeting",
      "type": "text",
      "content": "Hello! How can I help you today?"
    },
    {
      "id": "dateInput",
      "type": "datePicker",
      "label": "Select a date",
      "action": "selectDate"
    },
    {
      "id": "submitBtn",
      "type": "button",
      "label": "Submit",
      "action": "submitForm"
    }
  ]
}

When your client application receives this, it renders a native text element, a date picker, and a button using its own UI framework.

Why This Matters

The launch of a2ui.org signals that A2UI is moving beyond “experimental” status. Having a dedicated website means:

Increased Visibility: Easier for developers to discover and learn.
Community Building: A central place for discussions and contributions.
Enterprise Confidence: A professional presence that reassures enterprise adopters.

What’s Next?

With the official website live, we recommend:

Bookmark a2ui.org for spec updates.
Star the GitHub repo to follow development.
Join the community to provide feedback on the A2UI roadmap.