What it means
The model outputs component trees, layout, and interactions that render in product, often iteratively edited through follow-up prompts.
Why designers should care
GenUI needs guardrails: design tokens, component allowlists, accessibility checks, and diff/review before merge. Otherwise you get pretty demos that break your system.
Example
A PM describes a metrics panel; GenUI renders cards bound to real data schema. The designer swaps auto-picked charts for approved components before release.
Common mistakes
- Shipping generated UI that ignores your design system and accessibility baselines.
- No preview vs production boundary; users think generated code is already live.
- Infinite prompt iteration with no version compare or rollback.
Frequently asked questions
What is Generative UI (GenUI)?
Generative UI (GenUI) is when AI produces live interface elements (forms, dashboards, cards, charts) from prompts or data, not just static text.
Why should designers care about Generative UI (GenUI)?
GenUI needs guardrails: design tokens, component allowlists, accessibility checks, and diff/review before merge. Otherwise you get pretty demos that break your system.
What are common mistakes with Generative UI (GenUI)?
Shipping generated UI that ignores your design system and accessibility baselines; No preview vs production boundary; users think generated code is already live; Infinite prompt iteration with no version compare or rollback.