Material, Cupertino, and You in the Post-SDK Split Era
summary
Announcements that Material and Cupertino move out of the SDK into separate packages, with the codebase refactored into raw widgets mandated and cross‑imports removed so apps get lighter. Audit of ~260 tests finds 48% convenience imports, driving the split and rewritten tests. Migration is phased: core refactor by Dec 2025 refactor, beta packages early 2026, gradual removals later; apps keep working but pubspec updates and the improved dotfix tool are required to fix imports.
AI-written summary · about
chapters (12)
- 0:00Flutter’s monolith past
- 1:03Splitting Material and Cupertino
- 3:13Migration pain points
- 6:04Import scandal and flaws
- 7:07Raw widgets and lighter SDK
- 9:17Three-phase roadmap
- 11:23Freedom risks and UI
- 12:25Breaking changes and compatibility
- 13:48Avoiding cross-layer imports
- 15:31Adaptive widgets and independence
- 16:32Theming challenges
- 17:56Gradual rollout and future
related talks
46mScaling Up With SwiftUI: Migrating iOS Apps To SwiftUI
45mEverything Material All At Once
30mGetting your apps ready for Material 3
32mHow Flutter Stays Ahead of iOS Releases
41mWe dropped Material 3
32mBeyond Mobile: Material Design, Adaptable UIs, and Flutter
30mAdding Flutter to your app - what are they not telling you?
22mIntroduction to Flutter