Flutter's GenUI Package and A2UI Protocol Receive Major Overhaul: New Architecture Promises Greater Developer Control

Breaking: Flutter Team Unveils GenUI v0.9.0 with Decoupled Architecture

The Flutter team has released a significant update to both the genui package and the A2UI protocol, moving to version 0.9.0. The most critical change is the shift from a 'Structured Output First' approach to a 'Prompt First' philosophy, where agents now embed blocks of JSON as text in their responses.

'This update gives developers direct control over LLM interactions,' said a Flutter team spokesperson. 'The architecture decoupling means you can now manage chat history, retry logic, and error handling without framework wrappers.'

Background: What Are GenUI and A2UI?

Generative UI (GenUI) is a user experience pattern where an agent not only generates content but also decides how that content is displayed and made interactive. For Flutter developers, implementing GenUI requires A2UI, an open protocol that enables agents and renderers to collaborate on UI composition and state.

The Flutter team built the genui package to connect agents with a catalog of widgets via A2UI. Previous versions relied on a monolithic ContentGenerator class that handled prompt construction, LLM calls, and response parsing. That approach is now outdated.

What This Means for Developers

The removal of ContentGenerator is the most impactful code change. The framework is now split into three distinct layers:

• Engine (SurfaceController): Manages UI state and rendering.
• Transport (A2uiTransportAdapter): Streams messages between agent and renderer.
• Facade (Conversation): Offers a high-level API for managing chat states.

This decoupling means developers bypass rigid APIs and directly set up connections to their preferred LLM, tweak generation settings, and add custom functions. Previously used provider-specific wrappers like genui_dartantic and genui_google_generative_ai are no longer needed.

'Instead of passing a ContentGenerator to your SurfaceController, your app is now responsible for setting up its own agent connection and passing messages through a TransportAdapter,' the spokesperson added.

Migration Guide: From v0.7.0 to v0.9.0

If you are upgrading an existing app, follow the official migration steps:

1. Remove dependencies on provider-specific wrapper packages.
2. Replace ContentGenerator with your own agent setup and transport adapter.
3. Wire up a new chat loop using the Conversation facade.

Detailed documentation is available in the Flutter team's migration guide. The shift promises greater flexibility but requires a more hands-on approach to LLM integration.

Industry Reaction and Next Steps

Developers have reacted positively to the increased control, with early testers noting improved customizability. The Flutter team expects the new architecture to accelerate adoption of GenUI patterns in production apps.

Future updates will focus on simplifying the transport layer and adding more widget catalogs. For now, the community is encouraged to experiment with the Prompt First approach.