Flutter 3.47 decouples Material and Cupertino into standalone packages
What's New in Flutter 3.47
Flutter 3.47 marks a major milestone by releasing material_ui and cupertino_ui as standalone 1.0 packages, decoupling design systems from the core SDK. The update also brings Impeller to desktop by default, prepares for Apple's Xcode 27 with raised minimum OS versions, and graduates Widget Previews to stable. Developers can migrate using dart fix, and the release includes experimental multi-window support and flavors for desktop.
By opting into the decoupled design systems, you gain control over your design roadmap.
- oDot
Does anyone know if the original promise of their simple layout model proved itself?
IIRC, the Flutter team mentioned how using just width/height constraints is enough to represent all relevant layouts. This sounds very nice, being so much simpler than Flexbox and miles ahead of CSS Grid ergonomics.
Did it live up to the promise or did they expand the model with Flex/Grid/etc?
- doodlesdev
While I've used Flutter since Alpha, I've been away for a few years. A few things have shocked me in these release notes: how come Impeller still wasn't the default engine for all platforms? Also, why are they migrating to WASM if one of the core features of Dart is compiling to JavaScript? Finally, how come multi window support only get viable now, after four years having desktop support?
Honestly, Flutter is an extremely enjoyable development experience I would recommend anyone I care for to stay away from. The fact it's developed by Google doesn't help: it's a matter of time before they kill it like they did with so many UI libraries and frameworks already, specially with JetBrains developing Compose Multiplatform and the Android team going all-in in the Compose strategy.
- meerita
I still prefer React Native with Expo over Flutter, mostly for practical reasons:
* Language and hiring: TypeScript has a much larger developer pool. Dart is a solid language, but finding experienced Flutter engineers is harder.
* Platform model: React Native maps much more naturally to native platform concepts. Flutter owns much more of the rendering stack, which is powerful, but also creates another abstraction layer between the app and the platform.
* Performance: Flutter can absolutely be fast, so I would not claim otherwise. My experience, however, is that RN has required less work to get interactions and animations that feel consistently native.
* Ecosystem: RN benefits from the broader React, TypeScript, JavaScript, and native ecosystems. Expo has also improved dramatically and now covers a large part of the usual mobile platform work.
* Platform-specific features: neither framework completely eliminates native code. Things like widgets, Live Activities, Dynamic Island, extensions, NFC, and other platform APIs eventually bring you back to Swift/Kotlin anyway.
* Migration to native: if the long-term destination is Swift and Kotlin, I find RN a better intermediate representation. Its component model and platform integration are closer to native concepts, which also makes the codebase easier for agents to translate incrementally into proper native applications.
That said, these are trade-offs, not claims that Flutter is bad. Flutter has improved a lot, and for teams that […]
- TheChaplain
Are Flutter and React Native still viable choices today?
I get the impression that more are going for native mobile, KMP or PWA.
- eviks
> Linux and Windows now support popup windows, allowing you to build native context menus and utility palettes.
How does such a basic feature only get added so late?
- Humphrey
Oh finally multi-window support - I might finally be able to flutter for a simple desktop app side project I've been wanting to build.
- AbuAssar
the "Text and selection" demo caught my attention, why flutter render the shortcuts bar itself and not delegate this to the underlaying os?
- feverzsj
Tested lots of flutter desktop apps on Github last year. All have sluggish animation. FPS rarely reached 60.