Compose
Google's native declarative UI toolkit for Android, written in Kotlin. It supports live previews and expression-driven animation and serves as the API foundation of Remote Compose.
Timeline (last 90 days)
A2UI's choice of declarative JSON description means the agent only needs to output the target state rather than a sequence of operations, and the client can decide for itself how to render, how to animate and how to reuse components, which is also the precondition for it to be carried by native Compose components.
The Google Jetpack Compose team has released the A2UI (Agent to UI) library, which lets agents describe interfaces declaratively in JSON, with the client rendering them using native Compose components.
A2UI's integration path has three layers: the Chat Session receives the agent's streaming responses and extracts the raw A2UI JSON messages; the Message Processor uses a Parser to convert the JSON into a semantic representation, validates it against the Catalog, and maps it to the Surface model; finally the A2UI Surface composable renders it into native Compose UI.
When customizing components in A2UI, replacing a basic catalog button only requires implementing the composable function of the corresponding interface; adding a new component type requires implementing the A2UI Component interface, whose name and description are serialized into the Catalog schema sent to the backend as the basis for the agent to decide whether to use the component, so they must be written descriptively enough.
Compose 1.13 introduces morph polygon shape, supporting smooth transitions between different polygons.
Compose has had a blur modifier since Android 12, suitable for blurring with a uniform radius.
Progressive blur is an official API in Compose 1.13.
Compose 1.12 introduces MeshGradients.
Compose 1.12 begins to support wide color gamut.
Compose 1.13 natively supports polygon shapes.
1 more timeline events
All Facts (11)
A2UI's choice of declarative JSON description means the agent only needs to output the target state rather than a sequence of operations, and the client can decide for itself how to render, how to animate and how to reuse components, which is also the precondition for it to be carried by native Compose components.
50%UnverifiedWhen customizing components in A2UI, replacing a basic catalog button only requires implementing the composable function of the corresponding interface; adding a new component type requires implementing the A2UI Component interface, whose name and description are serialized into the Catalog schema sent to the backend as the basis for the agent to decide whether to use the component, so they must be written descriptively enough.
50%UnverifiedA2UI's integration path has three layers: the Chat Session receives the agent's streaming responses and extracts the raw A2UI JSON messages; the Message Processor uses a Parser to convert the JSON into a semantic representation, validates it against the Catalog, and maps it to the Surface model; finally the A2UI Surface composable renders it into native Compose UI.
50%UnverifiedCompose has had a blur modifier since Android 12, suitable for blurring with a uniform radius.
50%UnverifiedAfter Instagram migrated its UI to Compose and adopted an AI-native architecture, token usage in AI-assisted development dropped by about 33%.
50%UnverifiedThe Google Jetpack Compose team has released the A2UI (Agent to UI) library, which lets agents describe interfaces declaratively in JSON, with the client rendering them using native Compose components.
50%UnverifiedProgressive blur is an official API in Compose 1.13.
50%UnverifiedCompose 1.13 introduces morph polygon shape, supporting smooth transitions between different polygons.
50%UnverifiedCompose 1.13 natively supports polygon shapes.
50%UnverifiedCompose 1.12 begins to support wide color gamut.
50%UnverifiedCompose 1.12 introduces MeshGradients.
50%