01Render
Render A2UI on your platform
Install a renderer, connect a host, paint a surface. About twenty lines each.
Render A2UI in React Install the two npm packages, connect a host, paint a surface with <HostSurface>.Render A2UI in SwiftUI Add the Swift package, hand the painter a host, show a surface on iOS and macOS.Render A2UI in Compose Add the Maven artifact, connect a host, paint a surface in Jetpack Compose.Render A2UI in gpui Add the crates, give the SurfaceView a host plugin, paint natively on the desktop.
02Customise
Make it yours
Themes change the look, extensions add components, host plugins decide what a surface may do.
Write your own theme Tokens, recipes and an extends chain: one JSON file every renderer loads at runtime.Write an extension Custom components: a catalog schema plus a painter per platform, or a macro only.Write a host plugin Functions behind a policy gate, data bindings by source URI, the URL and media policy.
03Build
Build with agents
Ship an app as a declarative package, or let a model answer with UI.
04Compiled in CI
Compiled in CI
The pages show the files in apps/ui-site/guides as they are. guides/check.ts builds each in an empty temp directory from the packed npm packages, the Swift package, local Maven artifacts and path crates:
shell
bun apps/ui-site/guides/check.ts react # or agent, theme, swift, compose, gpui, allComplete apps: the samples run web, iOS, Android and gpui hosts against one local A2UI server, with a third-party theme and an extension component.