Currently, something deterministic emits the schema (backend service, rules engine, handwritten handler) and Flutter renders it. Using Google Agent Development Kit (ADK) a Gemini agent is the author. We are still using the same A2UI protocol, but now most of the decision making is being done by the LLM. There are changes on the Flutter side when utilizing the ADK. There is a lot less business logic to dictate for each scenario. We can rethink the GenUI catalog as part of our design system and focus on component quality. We can give these abstract widgets to the agents to use in any context. This is an ever-evolving technology and there are multiple ways to handle this architecture. In my experience I used an orchestrator, a thin dispatcher, which passes the metadata context to the appropriate agent. This could also be done with an agent that is tasked to orchestrate to other sub-agents. What would be faster or more efficient? Flutter doesn’t need to know about each individual agent. It just needs one endpoint. The Flutter side becomes a passive renderer of what the agent decides to show. The ADK is a new tool that can make a lot of changes in Flutter development for a GenUI app.