A2UI Renderer Ecosystem: Official and Community Options

Renderer choice is an architecture decision, not a cosmetic library preference. The renderer owns schema handling, surface state, catalog mapping, action routing, accessibility output, and failure behavior.

Maintained choices

The official project documents stable React, Lit, Angular, and Flutter paths for the v0.9.1 family. Web renderers share protocol machinery through @a2ui/web_core, reducing the risk of each framework reimplementing data-model and lifecycle semantics.

SwiftUI and Jetpack Compose remain planned rather than stable official releases. A prototype repository or roadmap entry should not be represented as supported production software.

Community coverage

Community projects expand A2UI to Vue, Apple platforms, terminal UIs, React Native-style runtimes, MUI catalogs, and cross-platform native engines. Their value is real, but compatibility labels vary: some maintain v0.8 and v0.9 branches, while others implement a specific snapshot.

Before adoption, verify the latest release, commit activity, protocol fixtures, malformed-message tests, URL policy, data-model path hardening, keyboard support, screen-reader behavior, license, and upgrade ownership. Run the project’s conformance tests against the exact catalog you will deploy.

Selection sequence

Choose the application’s native framework first. Confirm the protocol version second. Then test incremental updates, two-way data binding, unsupported components, large lists, image loading, reconnects, and action replay. Only after correctness should bundle size and styling convenience decide between compatible implementations.

Our maintained renderer matrix records current options and selection criteria. Pair it with the version guide before committing to a production dependency.