Skip to content

Ecosystem Renderers

Community and third-party A2UI renderer implementations.

!!! note These renderers are maintained by their respective authors, not the A2UI team. Check each project for compatibility, version support, and maintenance status.

RendererPlatformv0.8v0.9ActivityLinks
@a2ui-sdk/reactReact (Web)Stars Last commitGitHub · npm · Docs
A2UI-AndroidAndroid (Compose)Stars Last commitGitHub
a2ui-react-nativeReact NativeStars Last commitGitHub
@zhama/a2uiReact (Web)npm
A2UI-reactReact (Web)Stars Last commitGitHub

These projects are early-stage or experimental:

  • @xpert-ai/a2ui-react — React renderer with ShadCN UI components (v0.0.1, published Jan 2026)
  • a2ui-3d-renderer — Experimental Three.js/WebGL 3D renderer for A2UI (~2 stars)
  • ai-kit-a2ui — React + ShadCN renderer for the AIKit framework (~2 stars)

@a2ui-sdk/react is currently the most mature community React renderer, with 11 published versions, Radix UI primitives, Tailwind CSS styling, and a dedicated docs site. It was announced on the A2UI discussions.

A2UI-Android fills an important gap — it’s the only community Jetpack Compose renderer, covering Android 5.0+ with 20+ components, data binding, and accessibility support.

a2ui-react-native is the only React Native renderer, enabling A2UI on iOS and Android via a single codebase.

No credible A2UI renderer packages were found on PyPI as of March 2026. A2UI renderers are client-side (UI) libraries, so the ecosystem is naturally focused on JavaScript/TypeScript and native mobile frameworks.

Built an A2UI renderer? We’d love to list it here.

  1. Fork the google/A2UI repository
  2. Edit this file (docs/ecosystem/renderers.md) — add a row to the Community Renderers table with your renderer’s name, platform, npm package (if any), version support, and a link to the source
  3. Open a PR against google/A2UI with a short description of your renderer
  4. Post in GitHub Discussions — let the community know what you built! A short demo video goes a long way.

Need inspiration? Browse the community samples in the repo — these cover Angular, Lit, and ADK-based agents and are a good starting point.

A listing is more likely to be accepted and used if it:

  • Has published source code (open-source preferred, MIT or Apache 2.0)
  • Clearly states which A2UI spec version it supports (v0.8, v0.9, or both)
  • Covers core components: text, buttons, inputs, and basic layout
  • Includes a README with install instructions and a minimal usage example
  • Is actively maintained — flag it as archived if you’re no longer supporting it

Community renderers don’t need to be production-ready to be listed — experimental and early-stage projects are welcome in the Notable Mentions section.