Decoupling Material and Cupertino @flutterdev

Decoupling Material and Cupertino @flutterdev

Uploaded January 2026 | Updated September 2026, 1 week ago

We’re decoupling the Material and Cupertino design libraries from the core Flutter framework. Decoupling will empower the Flutter community to contribute to Material and Cupertino without having to worry about how their contribution could become a regression in the framework.

#Flutter

Decoupling Material and Cupertino

CupertinoSlidingSegmentedControl (Widget of the Week)

Vibe-coding with Gemini CLI, part 2 | Observable Flutter #68

Building the Cloud Next demo (yet again) | Observable Flutter #87

How Flutter makes the most of your platforms

Dart Code Metrics | Observable Flutter #63

Ecosystem and platform modularity with Flutter 3.41

BlocSignal | Observable Flutter #93

Flutter’s streamlined onboarding process

Anatomy of a widget

Introducing the Full-stack developer guide (Flutter, Firebase, Angular)

Iterable (Technique of the Week)

Decoupling Material and Cupertino