A2UI React Renderer Status: What Is Available Now

The earlier Q1 release tracker is now historical. The official project documents @a2ui/react as a maintained renderer for the v0.9.1 family, built with shared web protocol machinery from @a2ui/web_core.

What the official renderer provides

The renderer receives validated lifecycle messages, maintains Surface and DataModel state, resolves approved Catalog components, and routes user actions. It does not decide product authorization and does not make arbitrary remote content safe.

Before adoption, pin the renderer and schema versions together. Verify the exact public API in the installed package because examples written for v0.8 or an early v0.9 snapshot can use obsolete message names.

Catalog ownership

React applications retain ownership of components and design tokens. A Catalog maps protocol definitions to reviewed React implementations. This supports consistent themes and accessibility, but each implementation still needs tests for unsafe URLs, Markdown, navigation, file handling, focus, keyboard operation, and unsupported properties.

Migrating a custom implementation

Keep the old renderer until both implementations pass the same protocol fixtures. Compare creation, incremental updates, two-way data binding, deletion, duplicate delivery, reconnects, action replay, unsupported components, and fallback UI. Move version conversion to the transport boundary and avoid mixing v0.8 lifecycle names into v0.9.1 streams.

Community renderers remain useful when they provide a specialized Catalog or platform fit. Evaluate them by evidence—releases, tests, protocol compatibility, maintenance, security, accessibility, and license—not by framework popularity.

See the current renderer matrix, client setup sequence, and production security checklist.