GenUI Package 0.10.0 Ships with a2ui_core and Client-Side Function Support

The Flutter ecosystem's push into generative user interfaces continues to gather momentum with a fresh update to the genui package. Version 0.10.0 arrived with a set of fixes and new features, and the most notable of them is the introduction of a dedicated package that centralizes the classes underlying the A2UI protocol. For teams building agentic experiences that generate interfaces on the fly, this is a structural change designed to make the whole stack easier to work with.

Generative UI represents one of the most interesting frontiers in app development. Instead of hand-authoring every screen, an AI agent generates the interface, layout, and interactions in response to user intent, grounded in a protocol that keeps the experience predictable. As that idea moves from experiment to production, the tooling around it needs to mature, and the genui package update is part of that maturation.

Centralizing the Protocol with a2ui_core

The headline change in this release is a new package that centralizes classes related to the A2UI protocol. This includes the expressions and catalog entries and other shared concepts that appear throughout generative UI applications. By pulling these into a single, focused package, the Flutter team gives developers a stable, coherent home for the vocabulary of generated interfaces.

The benefit of centralization is largely architectural. When protocol classes live scattered across multiple packages, upgrading or extending the system becomes awkward, and consumers can struggle to keep track of where a particular type lives. A dedicated core package establishes a clear boundary, making the protocol easier to reuse, document, and evolve without friction.

• Version 0.10.0 introduces the focused a2ui_core package
• Protocol classes like expressions and catalog entries are centralized
• A stable home for shared types makes upgrades and extensions cleaner
• The update bundles a range of fixes and new features

For developers building on generative UI, this restructuring reduces guesswork. When you need to know how the protocol represents an expression or a catalog entry, the answer now lives in a predictable place. That clarity becomes more valuable as teams assemble larger systems around generated interfaces, where a well-organized type story is essential for long-term maintainability.

Client-Side Functions Bring New Possibilities

The other significant addition is support for A2UI's client-side functions. These allow the agent to provide functions that the client can direct to use for validation, derived values, and other small tasks, all without making a round trip back to the model or server. It is a mechanism designed to keep generated interfaces responsive and capable of lightweight local logic.

Consider a form generated by an agent. Instead of sending every input off for validation, the agent can attach client-side functions that check values locally, compute derived state, and respond in real time. The result is an interface that feels responsive and snappy, because the common, small operations happen directly on the device rather than waiting on a network call.

• Client-side functions let agents hand small tasks to the running app
• Validation and derived values can be computed without a round trip
• Generated interfaces feel more responsive and interactive
• The feature slots naturally into agentic, real-time experiences

This direction is a natural fit for the broader momentum around generative UI in Flutter. The ecosystem has been investing heavily in making generated interfaces not just visually appealing but genuinely functional, and client-side functions are a meaningful step toward that goal. They shift some responsibility from the agent to the app, which tends to produce faster and more reliable interactions.

For teams evaluating the genui package, version 0.10.0 lowers the barrier to understanding the A2UI protocol while simultaneously expanding what generated interfaces can do at runtime. Both changes point in the same direction: making generative UI a practical, production-ready way to build applications rather than a fragile experiment.

As with any early-stage ecosystem, it is wise to keep an eye on the package documentation and changelog as the genui stack continues to evolve. The introduction of a2ui_core in particular is the kind of structural milestone that often precedes further refinements, so the pace of change here is likely to stay high. But for developers ready to embrace agentic, interface-generating apps, the foundation is getting steadily stronger.