Google confirmed at Google I/O 2026 that Canonical is the new lead maintainer and ‘strategic steward’ of Flutter desktop for Windows, macOS and Linux.

The announcement of an expanded partnership with Canonical came during the ‘What’s new in Flutter’ presentation at Google I/O 2026, where Kate Lovett, Engineer Manager on the Flutter Framework team at Google, touched on their existing work:

“[The Flutter] desktop experience has reached a new level of maturity this year, driven by our incredible engineering partnership with Canonical, the publisher of Ubuntu”.

She later confirmed that Canonical’s ‘deep technical expertise’ will now oversee maintenance of Flutter for desktop and take charge of its roadmap. The arrangement is said to be the first step in a wider governance expansion for Flutter.

Canonical made Flutter its ‘default choice’ for developing new Ubuntu desktop apps in 2021. Since then the distro has created and shipped a range of Flutter-based software for Ubuntu, including App Center, Firmware Updater and Security Center.

A leaner Flutter core

Canonical’s stewardship on the desktop wasn’t the only major change announced at the ‘What’s new in Flutter’ presentation at Google I/O 2026.

On desktop, Flutter now supports tooltips and content-sized views, and can now create additional windows and dialogs so that developers can create “complex multi-window apps that feel native on Linux, Windows, and macOS”.

Google also moved Material and Cupertino design libraries out of Flutter’s core SDK into standalone packages. Framework updates will no longer force developers to absorb breaking UI changes (like Liquid Glass or newer Material Design) at the same time.

Foundational classes like Listenable transition out into pure Dart packages so that the wider Dart community can use them without needing to pull in the entire Flutter framework as a dependency.

The presentation also covered a raft of AI-focused features and tooling updates, though most are aimed at mobile and full-stack Dart developers.

Given Flutter’s wide and diverse usage (including for in-car infotainment systems now), there’s plenty of enthusiasm for Flutter at Google. It isn’t jettisoning Flutter from its own orbit, even if Flutter team layoffs and rejigs did signpost a change in priorities.

But with Flutter moving towards a more collaborative governance model, this looks like Google doing a bit of maintenance offloading by handing stewardship of platforms it’s less invested in to parties who are – in this case, Canonical.

Big thanks niikv