Generative UI,the complete guide.
Generative UI (GenUI) lets an application assemble its interface at runtime from governed components, adapting in real time to user intent and context. Here is what the GenUI framework is, how it ships in production on Flutter, and how enterprises are piloting it.
Illustrative of what GenUI composes, next to the static UI it replaces. Bank of VGV is our in-house demo brand. In production, every surface builds from your design system and your data.
Chatbots were just the start.
GenUI is what’s next.
Static screens give every customer the same layout. Chatbots answer in paragraphs and leave them the taps. GenUI answers in the interface itself, mapped to what the customer is trying to do and ready to act. Google already ships it inside Search.
Generative UI is an interface the model composes at runtime. It assembles real components from your design system around each customer and the live moment, instead of answering in text.
Where’s the agent that speaks in widgets rather than in text? It’s the difference between me mapping what I’m trying to do to the taps required by the UI, versus the UI mapping itself to what I’m trying to accomplish.
Generative UI, defined.
Generative UI (GenUI) is an approach where an application assembles its interface at runtime, selecting and arranging components from a governed catalog, adapting in real time to who the user is and what they are doing.
Four ways an interface reaches the screen — and where GenUI picks up.
Hand-built at compile time. Every user gets the same screens, and every new state means another release cycle.
Rules reorder fixed content inside a fixed layout. Useful, but the interface itself never changes shape.
Produces text, images, answers. In an app it usually arrives as a chatbot that answers in paragraphs and leaves you the taps.
Produces the interface itself. The screen is composed in the moment from approved components, on-brand and ready to act.
Google ships the GenUI framework for Flutter: the official Flutter GenUI SDK and the A2UI protocol. Nielsen Norman Group defines generative UI the same way: interfaces generated for the user and the moment, not hand-built in advance.
One brain. Every industry.
The plays are the same everywhere: take one high-intent screen and let it compose for the person in front of it. The content changes by vertical; the system does not.
A first-time saver and a family running a business should not see the same accounts screen. GenUI composes the next best step from real balances and real intent, inside the governance a bank actually has.
“Plan my day” becomes a composed itinerary with the reservation already held. Dynamic offers render as working surfaces the guest can act on in one tap.
“Wedding next Saturday, $500 for a suit and shoes” becomes three complete looks in the shopper’s size, ready to buy. No filters, no spreadsheet, and conversion moves with it.
Wait times fall, weather turns, a child melts down. The plan recomposes around the moment, on the guest’s phone and on every ambient surface in the park.
Somewhere else? The pattern travels. Tell us your vertical.
Pick a customer. Watch the screen build itself.
Bank of VGV is our in-house demo brand. The same system composes for any vertical.
This is where it goes as generation costs fall. The retrofits below are where it starts today.
The phone is one surface. GenUI composes them all.
Different customers bank in different ways. GenUI recomposes the experience for every surface, from a laptop to the kiosk in your branch lobby, delivering the right interface at the right moment.
Bank of VGV is our in-house demo brand, built to show what GenUI can do. In a real deployment, every surface is composed from your brand’s design system, components, and content.
Where GenUI fits. A capability, not a toy.
GenUI is one layer of an operating model, not an SDK you sprinkle on. Here is the hierarchy we build against.
What your customer actually touches. The product surface where loyalty is won or lost.
VGV’s proprietary method for experiences that reshape around each user: the governance, measurement, and delivery practice.
Interfaces assembled at runtime from a governed catalog. The engine inside the method.
One codebase rendering native across mobile, web, desktop, and embedded. The reason one catalog serves every surface.
Read bottom-up: Flutter gives you one codebase on every surface, GenUI makes that surface composable at runtime, and Adaptive Experiences is the method that makes it safe to run in production. Read top-down: the experience your customer gets stops being the screen everyone gets.
The model orchestrates. It never paints pixels.
GenUI never generates raw interface code. The model selects components from a pre-validated catalog, which are formally assembled and rendered by the Flutter GenUI SDK over the A2UI protocol. Three inputs govern every generation.
The operational logic of the agent. Rules, tone, and constraints that align every generated surface with your brand and business intent.
Intent, preferences, and state, bound to the catalog so the model can assemble an experience tailored to the moment.
The vocabulary of the system. The approved components and patterns the agent is allowed to use, and nothing else.
Governed by a method, not a prompt.
We partner with your team to define a custom Generative Design System, then build the AI-driven architecture that powers it in production. The fluidity of AI with the safety of enterprise design.
Composed live.
Never off-brand.
Every generated screen is built from your design system and your real data, reviewed before it ships, and bounded by controls your team holds.
GenUI runs in bounded zones. The app still owns navigation, fallbacks, and rollout. GenUI owns only the surface inside the zone, with kill switches and measurement built in.
GenUI only ever composes from your design system, a brand-safe set of components. Nothing it can invent.
Screens render from your live systems and real availability, never mock data or a stale rule.
Every screen can be inspected and replayed, so you see exactly what a customer will see.
Validated and accessibility-checked on every screen. Anything that fails falls back to a standard component.
Your review board approves the catalog once — components and copy through your existing process — and every composed screen is made only of approved parts. The pilot runs in a sandbox on synthetic data, so it clears review without touching personal data.
Not theory. Shipped.
VGV shipped the first enterprise GenUI in production, including generative UI for Google at Cloud Next. Those lessons are built into the GenUI Kit.
Meet GenUI Kit.
The packaged way in.
GenUI Kit is VGV’s packaged, full-source foundation for adding generative surfaces to the Flutter app you already ship. Your design system becomes a locked catalog, system prompts and guardrails ship as code you own, and quality gates keep every generated screen safe by default.
It debuts at Fluttercon USA in Orlando, July 16 to 17, 2026, with alpha access opening to enterprise Flutter teams after the show.
- Component catalog built from your design system
- System prompts, the operating logic, as editable source
- Guardrails screening every request in and out
- Quality gates with deterministic fallbacks
- Full source, customer-hosted, Flutter-first
Questions worth asking.
Plain answers.
- GenUI
- Generative UI. The interface is assembled at runtime from governed components instead of hand-built for every state. Also written as gen UI or generative user interfaces.
- A2UI
- The protocol an agent uses to describe an interface. Structured component descriptions, not prose.
- Agentic UI
- Any interface driven by an agent. GenUI is the disciplined version: the agent composes from approved parts only.
- Catalog
- A design system converted into the locked set of components the model is allowed to compose from.
- Zone
- A bounded place in an app where a generated surface renders. The app owns everything around it.
- Adaptive Experiences
- VGV’s method for putting GenUI into production. GenUI is the capability; this is the operating model.
What is generative UI (GenUI)?
Generative UI (GenUI) is an approach where an application assembles its interface at runtime, selecting from a catalog of governed, pre-approved components instead of showing every user the same static screen. The model chooses and arranges components. It never draws pixels and never writes raw UI code. Google ships an official Flutter GenUI SDK for it, and VGV builds production GenUI experiences on that SDK.
How is GenUI different from generative AI?
Generative AI produces content: text, images, answers. Generative UI produces the interface itself. A gen AI feature answers a question in a paragraph and leaves you the taps. A GenUI surface answers with a working screen, assembled from your design system and ready to act. GenUI sits on top of generative AI: the model does the reasoning, and GenUI turns the result into interface.
What is the difference between GenUI, agentic UI, and A2UI?
Agentic UI is the broad idea of an interface driven by an agent. A2UI is the protocol underneath: the structured way an agent describes which components to show. GenUI is the practice that makes both safe for production, where the agent composes only from a governed catalog your team approved. In short: agentic UI is the ambition, A2UI is the wire format, GenUI is the discipline.
Which companies are using generative UI today?
Google is the largest, shipping generated interfaces inside Search and publishing the Flutter GenUI SDK and A2UI protocol. VGV shipped the first enterprise GenUI implementations in production, including generative UI built for Google at Cloud Next, and is piloting with enterprises in banking, hospitality, and entertainment. Most of the market is at the pilot stage, which is exactly why the early movers are visible.
Is GenUI safe for banking and other regulated industries?
Yes, when it is governed. The model composes only from a catalog your review board approves once, through your existing process. Guardrails screen every request in and every response out, and anything that fails validation falls back to a deterministic component. Pilots run in a sandbox on synthetic data, so nothing touches personal information before your governance gate clears it. Anything that decides money or carries legal wording stays hand-built.
How much does a GenUI pilot cost?
A GenUI pilot is scoped like an experiment, not a replatform: one high-intent screen, a target on a metric you own, measured against an untouched control. Typical pilots run four to six weeks with a small senior team, and we will give you a fixed number at scoping. Start that conversation here.
How long does it take to ship a GenUI proof of concept?
With GenUI Kit, a team can have a first generative surface rendering from its own design system inside the first week. A measured pilot, one zone in production traffic with a target and a control, typically takes four to six weeks. The long pole is rarely the technology; it is catalog approval, which is why the Kit is built to clear governance quickly.
Does GenUI require Flutter?
The production path we build on is Flutter-first. Google’s GenUI SDK targets Flutter, and one Flutter codebase renders native across mobile, web, and desktop, which is what lets a single catalog serve every surface. If your app is not built on Flutter today, talk to us anyway. Getting enterprises onto Flutter is what VGV has done for a decade.
What is Google’s GenUI SDK and is it production-ready?
The Flutter GenUI SDK is Google’s official framework for rendering agent-described interfaces over the A2UI protocol. The SDK assembles and renders; production-readiness comes from what you put around it: a governed catalog, guardrails, quality gates, and measurement. That surrounding system is what VGV builds, and it is what GenUI Kit packages.
How do I choose a GenUI development agency?
Ask three things. Has the team shipped generative UI in production, not just a demo? Can they show the governance story, meaning catalog approval, guardrails, fallbacks, and measurement, in a form your review board will accept? And do they have real design-system and Flutter depth, since GenUI is only as good as the catalog underneath it? Agencies that clear all three are rare today.
Ready to go deeper? Explore GenUI Kit or talk to an expert.
Put GenUI in the app you already ship.
The fastest way to start: a short call, and we’ll find that screen together.
We design the surfaces, build the system on the GenUI Kit, and stay on through launch.