Observed Signal · Jun 17, 2026 · Technical Explainer · Source: UX Collective · Impact: 2/5 · Sentiment: Positive
A2UI: Designing Radically Adaptive UIs
Christine Vallaure explains A2UI, a protocol that enables generative or 'radically adaptive' user interfaces by acting as a shared language between an AI agent and an app renderer. The agent bundles a user request with a catalog of pre-built components and asks an LLM (the article cites Google’s Gemini as an example) to emit a streamed JSONL 'recipe' that names components and properties. The renderer validates the recipe against the catalog and assembles the UI from those existing components. Vallaure argues this shifts designers' responsibilities upstream — the quality and completeness of a product’s catalog determine the quality of generated screens — and outlines practical implications for design systems, Figma workflows, and gaps between design artifacts and machine-readable catalogs.
Explainer of an emerging protocol (A2UI) that changes how UIs are generated and shifts control upstream to design catalogs; relevant to product and UX teams but not an industry-shifting adtech event.
Track Figma Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- A2UI is described as a protocol (a shared language) between an AI and an interface that produces UI 'recipes' streamed as JSONL.
- Google initiated A2UI and related work; the article notes CopilotKit and other projects are shaping the spec.
- A2UI uses an agent/renderer architecture: an agent asks an LLM to write a recipe, and a renderer builds the real screen from a predefined catalog of components.
- The A2UI catalog constrains the model: the model can only name components that exist in the catalog and a validator checks recipes against that catalog.
- Article authored by Christine Vallaure and published on 2026-06-17.
Connected Companies & Entities
3 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
The Push for A2UI: Solving AI Agent Interface Fragmentation
This article advocates for the adoption of 'A2UI' (agent-to-UI), an open-source, declarative standard introduced by Google to solve user interface fragmentation across AI agents. Currently, developers face a 'surface tax,' building unique adapters for platforms like OpenAI's ChatGPT, Anthropic's Claude, Microsoft Copilot, and Slack's Block Kit. Without a unified standard, rendering simple UI components (such as a date picker) requires multiple proprietary formats, causing massive development overhead. A2UI uses declarative JSON that allows the host client to render native widgets according to its own design system, mirroring the historical web standard movement of the browser wars. Industry actors like Hugging Face, Shopify, and ElevenLabs are already adopting similar interactive frameworks like MCP-UI, underlining the growing momentum for neutral, cross-platform UI rendering standards in the AI era.
Interface as Output: Personalized, Derived Web UIs
The article argues that modern interfaces should be treated as derived outputs rather than fixed, authored artifacts. It proposes separating stable interface logic (data, actions, structure) from the visual layer (arrangement, emphasis, ordering) so visuals can be generated specifically for clusters of users. The author describes a cache-first approach: derive an interface per behavioral cluster in advance, cache it, and serve it instantly to matching visitors. Brand is reframed as a constraint system (values, constraints, expressions) rather than a single layout. The piece highlights trade-offs — stability, legibility/transparency, and creative intent — and states that SentientUI is building a personalization layer for the web, starting with React and Next.js.
Agentic AI Meets Figma: Practical Design Systems Guide
This practical guide explains how agentic AI agents are beginning to use well-structured Figma design systems as machine-readable instructions to assemble UI components. The author recounts a Storybook demo where an agent composed a customer-review component by reading components, tokens and props, and highlights technical building blocks designers must adopt: semantic tokens, exact prop and component naming, complete state coverage, auto layout, slots (Figma feature), and Code Connect mappings to code. The piece defines MCP (Model Context Protocol) as the connector agents use to read tools, notes Uber’s recent write-up using an open-source Figma Console MCP, and raises open questions about governance, visual review workflows, and who owns quality as agents accelerate component generation. The article frames agentic workflows as enabling but requiring disciplined file and process changes.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.