Introducing an RFC for intent-driven replay-able generative UI.
Generate an interface. Click a button that intends to take you to a new page, generate that page on the fly. Coming back to that page is instant.
Couple of interesting topics to dive into:
Infinite Software
Rather than hitting dead ends in your favorite software tool with wishes it could do X, Y or Z... what if you could just tell it to add the functionality and it appears inline with the rest of the content. You get to mutate and mold the experience to your expectations. Mix capabilities from your favorite tools (e.g. Add a "create ticket" button next to a list of Github repos that when clicked automatically create a Linear task).
Intents
Today software is usually made as a whole, meaning every path needs to be well thought out before we can ship it. Most users don't use 100% of the surface area either and everyone seems to use it differently. With intents you can place a button on the screen with an intent, such as "Open a new page with details about this musical artist", and without having to have generated that view ever before we can ship the software. When a user clicks that button that screen will be generated on the fly!
Materialize new views as you click "intents", or upsert visual changes in your existing interface. Software starts to feel magical.
Persistence
An important component of this RFC is the ability to persist changes over reloads, and consistently rebuild the entire UI. Page reloads reference the JSON page structure to lay it out. Tool calls and API requests are made on load to populate latest data into the slots in the UI – but we only make the calls we need. LLM calls stay totally out of the loop on every refresh, only used to amend experiences.
Data Connections
Bring any MCP server or OAuth service as a configuration and access their data. Write operations require human approval, read operations drive the visible UI generation. Ideal world would be you set up all your connections one time and use them anywhere you go. Github, Linear, Cloudflare, any service... you name it.
UI Library Agnostic
The RFC does not require use of any specific UI library so you're encouraged to bring your own. Bind specific UI components to a catalog. For example I bind "Modal" to "LayerDialog" from Kumo (http://kumo-ui.com)
----
Imagine not being limited by the developers vision and being able to expand upon existing products however you want. Add new functionality on the go. Today the concept works on green field projects, but will continue exploring what a product might look like if this option was given to users to mutate their UI.
The RFC specifies Intents and Persistence (IAP): a JSON document format and the host behavior that lets a model-generated application be stored, reloaded and replayed predictably.
Give it a read and let me know what you think!