GenUI Kit drops into the app you already run.
Your design system becomes a locked catalog. Our engineers build the guardrails, quality gates, and Dart backend into one bounded zone of the app you already run, with no rebuild and no platform to log into.
The complete GenUI guide- 4 Packages behind every GenUI build
- 5 days To a first catalog running in your sandbox
- Your repo Full source, customer-hosted
- 1 zone To start, with the rest of the app untouched
From static screen to adaptive surface.
Start with one high-intent surface in an app you already ship. Drop a generative zone into search, booking, or checkout, leave the rest of the app untouched, and measure the lift before you expand.
Financial Services
Travel & Hospitality
Retail
Stop making customers compare.
A comparison table makes them do the work. GenUI composes the recommendation around their actual spending, ready to add to the wallet.
Composed fromSpending historyCard catalogLive offers
Skip the application.
Four dropdowns become one held offer, composed around income the bank already sees, a tap from funded.
Composed fromDeposit historyRate tableBudget line
Don’t hand them a warning.
A static alert gives the customer homework. GenUI recomposes the month around the dip and holds what matters.
Composed fromCash-flow forecastBill calendarBuffer rules
Whole again by the 28th
Stop making guests browse.
A filtered list makes them do the work. GenUI composes the day around their party, pace, and budget, ready to book.
Composed fromParty & paceExcursion catalogPort schedule
Skip the reservation form.
Four dropdowns become one held table, composed around the whole party and tonight, a tap from confirmed.
Composed fromParty of 6Dining catalogTonight’s seatings
Table for six, held
Don’t make them re-plan.
A static alert hands the guest the problem. GenUI recomposes the day around the weather and holds what matters.
Composed fromForecastDay planHold rules
Your day, rearranged
Three looks, not two thousand products.
Wedding next Saturday, $500 for a suit and shoes is a sentence, not eleven filters. GenUI asks what matters, size, color, budget, then composes complete looks ready to buy.
Composed fromThe askSize & fit historyLive stock
Skip the seven-step configurator.
Complex products die in dropdowns. GenUI assembles a complete, compatible build from how they’ll use it, one confirm away from ordered.
Composed fromUse caseCompatibility rulesInventory
All 7 parts fit
One trip, not five tracking numbers.
Gear for a trip arrives as five orders and a hope. GenUI sequences the kit around the departure date: what ships, what’s in-store today, what to swap so it all lands in time.
Composed fromTrip dateStock & shippingOrder history
Packed by Wednesday
What we’d never generate
Anything that decides money or must be exactly right stays hand-built. The model never composes it.
-
Checkout and payment
Prices, totals, and the pay button stay hand-built, so money never rests on what a model chose.
-
Legal wording
Terms, disclosures, and consent text show exactly as your legal team approved them.
-
Core navigation
Tabs, menus, and the way back stay where people expect them, on every screen.
A deployable toolkit, not a science project.
Four pieces, and every one of them runs in the app and cloud you already own. What we hand to your team is yours to change, brand, and extend.
- 1 Flutter
A frontend
The GenUI experience your users interact with. It embeds into a Flutter, native, or web app and powers a discrete part of your product.
- 2 Dart
A backend server
Connects GenUI to your information and handles the unglamorous but important parts. Deploy it, or use it as the reference.
- 3 Your workflow
An MCP server
Turns Figma designs into a GenUI catalog, guides component choice, and builds the system prompt, checking your coding agent’s work at each step.
- 4 Preview & iterate
A sandbox app
Connects the pieces so your team can build and preview the GenUI experience on its own, outside your full app.
The right first six to eight components.
Not a promise to convert your whole design system on day one. Enterprise buyers want bounded areas with kill switches, fallbacks, and measurement. Zones give them exactly that.
- 01 Generate a focused GenUI catalog from your design system
- 02 Run it in the developer sandbox
- 03 Connect the backend to at least one real tool
- 04 Embed one controlled GenUI zone in your app
- 05 Measure the lift, then expand to the next zone
The gap between a demo and a product.
Anyone can stand up a GenUI proof of concept. The Kit is the part after that: the safety layer that keeps a live model on-brand in production.
- In 01
Authenticate
The real user
- In 02
Screen the request
Guardrails, in
- Out 03
Validate structure
Only approved components
- Out 04
Validate content
Only real IDs and data
- Out 05
Enforce intent
Guardrails, out
The guardrails come with the Kit. A customer cannot trick your AI into promising something it should not, and if the AI glitches, the mistake gets caught and fixed before it reaches anyone's screen. The screening layer is built on Google Cloud's enterprise model safety service.
Questions worth asking. Plain answers.
01 What does GenUI Kit add on top of Google’s Flutter GenUI SDK?
The SDK renders. The Kit is everything that has to sit around it: converting your design system into a catalog, screening what the model is asked and what it returns, validating a generated tree before a customer sees it, and handling auth, cost controls, and observability on the server. It also includes the MCP tooling that turns your Figma files into the catalog and system prompt.
02 How does GenUI Kit keep generated screens safe and on-brand?
Layers, each of which your own team controls. The catalog only contains components your team approved. System prompts constrain what the agent is for. A guardrail layer built on Model Armor screens every request in and every response out. Quality gates validate each generated tree, falling back to a deterministic component when anything fails.
03 Does GenUI Kit work with the app we already have?
Yes. That is exactly what it is for. GenUI Kit embeds a generative zone into the app you already run, whether that app is Flutter, native, or web, so you keep your navigation, your release process, and your code.
04 Does our app have to be built in Flutter?
No. The generative surface itself is built in Flutter, and it embeds into Flutter, native, and web apps alike, so your host app stays what it is.
05 What do we actually get?
A demo gets you a walkthrough of the four packages, the sandbox running, and a scoping session. When we build the surface with your team, it lands in your own repository: the Flutter frontend, a Dart backend server, an MCP server, and a sandbox app. Nothing phones home to us, and there is no login.
See GenUI Kit on your own surface.
A call with the engineers who build with the Kit, the four packages and the sandbox on real components, and a scoping session on where a generative zone fits your product.
Request a demoA 30-minute call about what you’re building.