Topic
Render spec
The JSON contract that turns an answer into native widgets.
8 posts
- 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
- Generative UI on native mobile: how an agent draws real product UIGenerative 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.Render spec15 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
- 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
- Adding an AI agent to a Flutter app, and what GenUI gives youThe platform-channel integration, and an honest comparison with Flutter's own GenUI SDK: what the alpha covers, what production needs, and which to pick.Integration8 min
- In-app agents that finish the task instead of answeringAn assistant that describes where a setting lives competes with your own navigation. One that completes the request does not. What changed, and what to build.Agent basics8 min
- 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