Flutter's GenUI Package Overhaul: Major Architecture Shift in Latest Update

Breaking: Flutter Team Unveils Radical Changes to GenUI and A2UI

In a significant update that will reshape how developers build generative user interfaces, the Flutter team has released version 0.9.0 of the genui package, accompanied by an update to the A2UI protocol. The move marks a departure from the previous 'Structured Output First' philosophy to a 'Prompt First' approach, fundamentally altering the framework's architecture.

The most notable change is the complete removal of the ContentGenerator class, which previously handled prompt construction, LLM network calls, and response parsing. Developers now have direct control over how their application interacts with Large Language Models (LLMs).

'This decoupling gives you control over chat history, retry logic, and error handling,' said a Flutter team spokesperson. 'You're free to use any model or provider without going through the framework's API.'

Architecture Decoupling: Engine, Transport, and Facade

The genui package now splits its responsibilities into three distinct layers: Engine (SurfaceController) manages UI state and rendering; Transport (A2uiTransportAdapter) streams messages between agent and renderer; and Facade (Conversation) provides a high-level API for chat state management.

This separation eliminates the need for provider-specific wrapper packages such as genui_dartantic, genui_google_generative_ai, and genui_firebase_ai. Developers must now set up their own agent connections and pass messages through the TransportAdapter.

Instead of passing a ContentGenerator to your SurfaceController, your app is now responsible for establishing the connection to the LLM,' explained a Flutter contributor. 'This is the most significant code change in the migration.'

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 should be displayed and made interactive. For Flutter developers, implementing GenUI relies on A2UI, an open protocol that defines how agents and clients (renderers) collaborate on UI composition and state.

The Flutter team originally built the genui package to leverage A2UI, connecting agents with a catalog of widgets and presenting them to users. The previous version (0.7.0) wrapped agents in a ContentGenerator class, which concealed many details from developers.

The v0.9 update aligns with version 0.9 of the A2UI protocol, shifting from structured output APIs to a Prompt First approach where agents include JSON blocks as text in their responses.

What This Means for Developers

This architectural overhaul offers greater flexibility but requires significant migration effort for existing apps. Developers moving from v0.7.0 must follow a detailed migration guide, including dependency cleanup and wiring up new chat loops.

• More control: Developers can now customize LLM connections, tweak generation settings, and add custom functions without framework wrappers.
• Simplified dependencies: No more provider-specific wrapper packages; a single genui package handles all integrations.
• Improved error handling: The new architecture allows direct implementation of retry logic and error management.

However, the removal of ContentGenerator means that the framework no longer abstracts LLM interactions. Teams must now set up their own agent connections, which may increase initial complexity but offers long-term flexibility.

'The Prompt First approach aligns better with how modern LLMs work,' noted an industry analyst. 'Developers gain transparency and can optimize performance directly.'

Immediate Steps for Migration

The Flutter team has provided a step-by-step guide for upgrading from v0.7.0 to v0.9.0. Key actions include:

1. Remove all references to provider-specific packages such as genui_google_generative_ai.
2. Update dependency declarations to use the latest genui package.
3. Replace ContentGenerator instances with direct LLM connections implemented via A2uiTransportAdapter.
4. Refactor chat loops to use the new Conversation facade.

'We recommend reviewing the official migration guide to ensure a smooth transition,' urged the Flutter team.

For more details, visit the genui release notes and A2UI protocol documentation.