Component Catalog Driven UI
Component catalog driven UI is a generative-interface architecture where an agent selects and configures approved client components rather than inventing arbitrary new UI.
Key points
- Google emphasizes that frontend teams already have design systems and components, so agents should dynamically use existing frontends instead of forcing a new component set [src-038].
- In A2UI, a catalog defines the components an agent may produce, and examples can be supplied for few-shot learning [src-038].
- The Schema Manager turns catalogs and spec versions into system instructions, then validates and repairs the LLM’s JSON against the selected catalog [src-038].
- Dynamic catalogs allow runtime switching across component schemas based on device constraints, user permissions, or client capabilities [src-038].
- Version negotiation lets the agent choose the best A2UI spec version based on what the client supports [src-038].
- Catalog-driven generation gives product teams a guardrail: agents can create adaptive interfaces while preserving brand, accessibility, and implementation constraints owned by the frontend [src-038].
Related entities
Related concepts
Source references
- [src-038] Google A2UI Team — “A2UI v0.9: The New Standard for Portable, Framework-Agnostic Generative UI” (2026-04-17)