How does an agent show a balance, a list or a form instead of describing it?
Render spec
Server-driven native UI: the agent names the widgets, your app draws them, and shipping a new answer shape stops requiring an app release.
7 posts
Start here
Generative UI on native mobile: how an agent draws real product UI
Generative UI on the web streams React components. On iOS and Android it has to become a typed spec over a fixed native catalogue. Here is why, and how it works.
- Shipping UI without a release: the case for server-driven UIWhy mobile teams move layout decisions to the server, what it costs in versioning and coupling, and what changes when an agent is the thing choosing the shape.Render spec8 min
- In-app search when the query is a whole sentenceHow search inside an app breaks when people speak in sentences, and how to build the search tool an agent can actually call.Render spec7 min
- How a render spec turns one JSON payload into native UIThe whole contract is a spoken answer, a separator, and an array of widget objects. The interesting parts are the constraints, not the format.Render spec10 min
- The first 300 milliseconds of an agent turnYou cannot make the model faster from the client. Almost all of the felt wait is decided before the model has said anything, and that part is yours.Render spec10 min
- Server-driven UI was already the answer. LLMs made it urgent.Server-driven UI and generative UI are one idea arriving from two directions, and a decade of mobile practice already tells you which parts are hard.Render spec10 min
- A catalogue beats free-form generation, and the objections say whyEvery serious objection to generative UI is an objection to free-form generation. A fixed catalogue answers all four without giving up the idea.Render spec10 min