[!IMPORTANT]
With the recent announcements for the next design iteration of iOS, 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.

This strategic pause gives us the space to ensure the long-term health and maintainability of Flutter's design libraries. We are committed to being transparent with our contributor community as we explore these options and will have more to share on our findings and future direction in the coming weeks. 💙

[!IMPORTANT]
Currently, we are not actively developing Material 3 Expressive, and we will not be accepting contributions for Expressive features or updates at this time.

This decision is to ensure that if and when such features are adopted, they align with a consistent design pattern and a planned rollout, benefiting the overall quality and maintainability of Flutter's material library. We learned a lot from our migration to Material 3, and want to approach future updates with those lessons in mind.

We will revisit this as the project and our roadmap evolve, for now we want to communicate early and continue to maintain transparency with our contributor community. 💙