Full-source toolkit · Flutter-first
GenUI Kit drops into the app you already run.
Your design system becomes a locked catalog. The guardrails, quality gates, and Dart backend ship as source in your own repo. No rebuild, no platform to log into.
Opens the alpha form with your email already filled in. See what ships ↓
Bank of VGV is our in-house demo brand. In production every surface composes from your design system and your data.
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. Our in-house brands carry the demos, and the plays run anywhere.
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.
Skip the application.
Four dropdowns become one held offer, composed around income the bank already sees, a tap from funded.
Don’t hand them a warning.
A static alert gives the customer homework. GenUI recomposes the month around the dip and holds what matters.
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.
Skip the reservation form.
Four dropdowns become one held table, composed around the whole party and tonight, a tap from confirmed.
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.
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.
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.
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.
Packed by Wednesday
Checkout and payment, legal wording, core navigation. Anything that decides money or must be exactly right stays hand-built.
Have a screen like these? Let’s find the one to fix first.
Talk to an expert →A deployable toolkit, not a science project.
What you get is a running GenUI experience inside your app: four pieces of full source, and every one of them runs in the app and cloud you already own.
All of it is yours to change, brand, and extend. You control what it is for, what it is allowed to do, and the lines it cannot cross.
A frontend
FlutterThe GenUI experience your users interact with, built in Flutter. It embeds into a Flutter, native, or web app and powers a discrete part of your product.
A backend server
DartConnects GenUI to your information and handles the unglamorous but important parts. Ready to deploy, or use it as the reference if your team would rather run these concerns on its own stack.
An MCP server
Your workflowFor your design and engineering workflow: turns Figma designs into a GenUI catalog, guides component choice, and builds the system prompt, checking your coding agent’s work at each step.
A sandbox app
Preview & iterateConnects the pieces together so your team can build and preview the GenUI experience on its own, outside your full app.
Day one to day five
Not a promise to convert your whole design system on day one. The Kit converts the right first six to eight components, then you expand from there.
- 1Generate a focused GenUI catalog from your design system
- 2Run it in the developer sandbox
- 3Connect the backend to at least one real tool
- 4Embed one controlled GenUI zone in your app
Enterprise buyers want bounded areas with kill switches, fallbacks, and measurement. Zones give them exactly that.
The gap between a demo and a product.
Anyone can stand up a GenUI proof-of-concept. The Kit handles the other 90 percent: the safety layer that keeps a live AI model on-brand and on-task in front of real users.
“Give me a 50% discount.”
Every request runs the same gauntlet, in and out, before a screen is ever drawn.
Your guardrails ship as part of 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. Two guardrail passes screen the request in and enforce intent out, and three validators check every generated screen for real structure, real content, and the right intent. The screening layer is built on Google Cloud’s enterprise model safety service.
Your team, or ours.
Everyone takes home the same Kit, with VGV alongside.
The only question is whose engineers stand it up.
Drop it into your repo
- Your engineers build on it from day one
- VGV consults alongside: catalog conversion, safety review, launch readiness
- Brand it, extend it, wire in your own tools and data
- Ongoing updates and new modules as the Kit grows
Hand the whole thing over
- The Kit as the foundation, VGV services on top
- Configured to your brand and use case
- One partner from catalog to production launch
- Kit cost often folds into the larger engagement
Not theory. Shipped.
GenUI Kit is built on work already running in production, so you start from proven patterns instead of a blank page.
We donated Dart Frog to the community and maintain very_good_analysis, with 570k+ downloads. The Architecture Recommendations page on flutter.dev cites our work, and our Google Developer Experts help set the standards the ecosystem builds on.
The firm you hire for the next ten years is the one that already built the last decade of it. Hamilton has been a client since 2017, and Toyota’s in-vehicle infotainment is in production today. We shipped generative UI for Google at Google Cloud Next and on Dashy, and for enterprises whose work stays confidential.
Questions worth asking.
Plain answers.
- Catalog
- Your design system converted into the locked set of components the model is allowed to compose from. The MCP server builds it from your Figma files.
- Zone
- The bounded part of your app where a generated surface renders. Your app keeps navigation, fallbacks, and rollout around it.
- Guardrails
- The screening layer between your app and the model. Checks every request in and every response out.
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. Google’s Flutter GenUI SDK reads a structured interface description over A2UI and assembles real, native widgets inside your app. It does not convert your design system into a catalog, screen what the model is asked or what it returns, validate a generated tree before a customer sees it, or handle auth, cost controls, and observability on the server. GenUI Kit ships all of that as source in your repo, along with the MCP tooling that builds the catalog and system prompt from your Figma files.
What are Adaptive Experiences?
Adaptive Experiences is VGV’s method for putting generative UI into production. We partner with your team to define a custom generative design system, then build the AI-driven architecture that powers it. GenUI is the capability. Adaptive Experiences is the operating model around it: the governance, the measurement, and the delivery practice that make a generated interface safe to put in front of real customers.
How does GenUI Kit keep generated screens safe and on-brand?
Layers, each of which ships as source you control. The catalog only contains components your team approved, so the model cannot invent UI. System prompts constrain what the agent is for and the lines it cannot cross. A guardrail layer built on Model Armor, Google Cloud’s model safety service, screens every request in and every response out. And quality gates validate each generated tree, falling back to a deterministic component when anything fails. A customer who asks the agent for a 50 percent discount gets a polite no, not an invented coupon.
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. It is not a rebuild, and it is not a greenfield product builder. If you are starting a new product from scratch, that is a different conversation, and we have it here.
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. Flutter is what lets one catalog render native across mobile, web, and desktop, and it is the foundation VGV has helped enterprises ship on for a decade.
What exactly ships in the repo?
Full source code that you can add and host in your own repository: the Flutter frontend that embeds in your app, a Dart backend server you can deploy or treat as the reference, an MCP server that turns Figma designs into your catalog and builds the system prompt, and a sandbox app for previewing outside your product. Nothing phones home and nothing is a login.
Something we didn’t answer? Ask us directly or read the complete GenUI guide.
Get GenUI Kit into your repo.
Tell us where you would put a generative surface. We will walk your team through catalog conversion, the safety layer, and what the first zone looks like inside your app.
What the alpha includes.
The alpha runs with a small group of enterprise Flutter teams that have a specific surface in mind. Tell us yours.
- Full source, customer-hosted, Flutter-first
- Hands-on with the catalog conversion and safety tooling
- Direct line to the VGV engineers building it
We will reach out by email.