☂️ Bring Material 3 Expressive to Flutter
**Update: July 29, 2025** > [!IMPORTANT] > The material and cupertino libraries are being decoupled into standalone packages to accelerate feature development. All new work for Material 3 Expressive will happen in the new packages once established in flutter/packages. > > Track the overall decoupling progress in our main issue: https://github.com/flutter/flutter/issues/101479 --- <details> <summary> Update: June 10, 2025 </summary> > [!IMPORTANT] > With the recent announcements for the [next design iteration of iOS](https://github.com/flutter/flutter/issues/170310), we wanted to provide additional context to this decision and share a broader update on our strategy for design systems in Flutter. > > Our original statement continues to hold: we are not actively developing Material 3 Expressive right now, and we will not be accepting contributions for these features at this time. The arrival of major updates for both Material and now Cupertino presents a significant (and exciting!) opportunity to apply past lessons and reconsider the long-term architecture for design system integration in Flutter. > > To evaluate this, we have begun a broad investigation into our current approach. This includes exploring various architectural possibilities - for instance, we are re-evaluating the long-requested idea of [moving the Material and Cupertino libraries out of the core framework](https://github.com/flutter/flutter/issues/101479). > > This strategic pause gives us the space to
Posted by guidezpl on May 14, 2025, 9:35 AM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
☂️ Bring Material 3 Expressive to Flutter
**Update: July 29, 2025** > [!IMPORTANT] > The material and cupertino libraries are being decoupled into standalone packages to accelerate feature development. All new work for Material 3 Expressive will happen in the new packages once established in flutter/packages. > > Track the overall decoupling progress in our main issue: https://github.com/flutter/flutter/issues/101479 --- <details> <summary> Update: June 10, 2025 </summary> > [!IMPORTANT] > With the recent announcements for the [next design iteration of iOS](https://github.com/flutter/flutter/issues/170310), we wanted to provide additional context to this decision and share a broader update on our strategy for design systems in Flutter. > > Our original statement continues to hold: we are not actively developing Material 3 Expressive right now, and we will not be accepting contributions for these features at this time. The arrival of major updates for both Material and now Cupertino presents a significant (and exciting!) opportunity to apply past lessons and reconsider the long-term architecture for design system integration in Flutter. > > To evaluate this, we have begun a broad investigation into our current approach. This includes exploring various architectural possibilities - for instance, we are re-evaluating the long-requested idea of [moving the Material and Cupertino libraries out of the core framework](https://github.com/flutter/flutter/issues/101479). > > This strategic pause gives us the space to
Comments (0)
No comments yet. Start the discussion.