Decoupling Design in Flutter →
GitHub issue →
We’re decoupling the Material and Cupertino design libraries from the core Flutter framework. Why? Because 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.
Watch along and learn about the three phase approach the Flutter team is taking to decouple Material and Cupertino, what impact Flutter developers will experience during the transition, and what you need to do to ensure your apps keep running and keep your users happy.
Chapters:
0:00 - Intro
0:45 - The current state of Flutter, Material, Cupertino, and Widgets libraries
1:38 - The problem
5:03 - How we’re decoupling design in Flutter
8:08 -Timeline
9:30 - Impact on Flutter developers & apps
Watch more Flutter Flight Plans →
🔔 Subscribe to Flutter →
#Flutter
Speaker: Justin McCandless
Products Mentioned: Material, Cupertino, Flutter
|
Join us on December 17 at 11am PT! Learn...
Decoupling Design in Flutter → GitHub i...
Jaspr on Observable Flutter → Buddyfind...
talabat - Delivering Tomorrow. → Migrat...
Verdure example → GenUI package → Giv...
Moving from asking "how" to asking "why"...
Strategic thinking moves you from asking...
🎓 These are three of the best Machine Le...
DevLaunch is my mentorship program where...
本動画の資料はこちら AWS Advanced JDBC Wrapper D...
Sometimes we work hard but still feel st...