This summer Flutter moved two important pieces: a release with a major structural change, and a Fluttercon in Orlando dominated by generative UI. Let's go through them.
The framework is finally letting go of Material and Cupertino
Flutter 3.47 landed in mid-August, running on Dart 3.13, and it brings the summer's biggest structural change: the Material and Cupertino libraries, built into the SDK since day one, now live as independent packages (material_ui and cupertino_ui) already at version 1.0. Until now, any improvement to design widgets had to wait for Flutter's full release cycle. From now on they can move at their own pace, with their own versioning.
Google has already said the old libraries, the ones still inside the SDK, will be marked deprecated in the fall release in November, so migrating with dart isn't optional, it comes with a deadline. 3.47 also makes Impeller the default renderer on macOS, Windows, and Linux, moves Widget Previews out of beta, and raises the minimum iOS and macOS versions (iOS 13 to iOS 15, macOS 10.15 to macOS 12) ahead of Xcode 27.
GenUI, the word everyone kept repeating in Orlando
Fluttercon USA ran in mid-July in Orlando, and if there was one thread running through it, it was generative UI: apps that no longer paint a fixed screen but assemble it in real time from a catalog of widgets, based on what the person using it asks for or what an agent decides. Very Good Ventures brought the largest delegation at the event, with sessions alongside teams from Etsy, Toyota, and Universal Studios, several of them digging directly into how GenUI is being used in production: an Agent Development Kit drawing the interface on the fly, built on the open A2UI protocol, instead of an agent just returning text.
The idea has been building since Google I/O in May, when it was introduced as part of Flutter 3.44 alongside the rest of the AI-assisted development toolkit but by Fluttercon the talk had moved on to actual use cases, not just keynote demos.
Our opinion
Of everything from this summer, we think the one that's going to stick is separating Material and Cupertino from the core SDK: it changes how design systems get maintained and updated in any Flutter project, ours included, and it doesn't depend on any trend actually taking off.
GenUI feels promising to us, but still early. The teams presenting it describe it as early-stage themselves, and assembling an interface on the fly raises questions about control, testing, and visual consistency that don't have a clear answer yet. It's a direction worth watching, not a feature we're about to drop into a client project next week.
We've had Flutter as one of our core technologies since 2018, and it's this kind of underlying decision, more than any single keynote headline, that ends up shaping how we set up a new project or plan a migration.
