Skip to content

☂️ Bring Material 3 Expressive to Flutter #168813

Description

@guidezpl

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: #101479


Update: June 10, 2025

[!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. 💙


Update: May 14, 2025

[!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. 💙


showcase image of mobile-based expressive designs

M3 Expressive is an expansion of the Material 3 design system (added to Flutter in #91605). It’s a set of new features, updated components, and design tactics for creating emotionally impactful UX. It was announced in May 2025. Learn more at Start building with Material 3 Expressive, and see Better, Easier, Emotional UX for the research behind it.

This is an umbrella issue for all potential work bringing Material 3 Expressive to Flutter, and which replicates the structure from Start building with Material 3 Expressive.

As of writing, this work is not planned, so if this interests you, please +1 and subscribe to this issue, respect issue hygiene, and consider offering to contribute on the hackers-framework Discord channel! :)

Expressive components

Fifteen new or updated components now feature more configuration capabilities, shape options, emphasized text, and other expressive updates.

Image

Expressive styles

  • Motion-physics system

new showcase for component motion

  • Visually emphasized typography

new emphasized typographic styles

  • Expanded shape library

35 new shapes

  • Vibrant color schemes

examples of vibrant color schemes

Activity

  1. added theissue type on May 14, 2025
  2. added
    frameworkflutter/packages/flutter repository. See also f: labels.
    p: material_uimaterial_ui package in flutter/packages
    on May 14, 2025
  3. added
    P3Issues that are less important to the Flutter project
    triaged-designTriaged by Design Languages team
    on May 14, 2025
  4. jiperez11 commented on May 14, 2025

    @jiperez11
  5. Piinks commented on May 14, 2025

    @Piinks
    Contributor

    Thank you @guidezpl for kicking this off!

    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. 💙

  6. added
    c: new featureNothing broken; request for a new capability
    c: new widgetMust also have "c: new feature". Request for a new widget.
    on May 14, 2025
  7. sunderee commented on May 14, 2025

    @sunderee

    I would love to see the Flutter team reconsider this stance in favor of at least starting with collecting requirements/technical documentation needed to bring Material 3 Expressive (M3E, or maybe M3X) to Flutter. I completely understand it's easier said than done, but from an outsider's point of view, these changes bring less of a friction than migration/change from M2 to M3.

  8. Piinks commented on May 14, 2025

    @Piinks
    Contributor

    starting with collecting requirements/technical documentation needed to bring Material 3 Expressive (M3E, or maybe M3X) to Flutter

    This is exactly what we are doing! 🙂
    And while we are doing this, we are not actively implementing or accepting contributions for Expressive.

  9. sunderee commented on May 14, 2025

    @sunderee

    My apologies, I misunderstood you. I was under the impression that nothing will be done at all, until further notice. Thanks for the clarification!

  10. brennschlus commented on May 14, 2025

    @brennschlus

    Systematic and thoughtful process sounds very mature, I wish you all luck with this implementation. Shapes, colours and typography looks awesome but motion system is something that I most excited about

  11. MitchellGoodwin commented on May 14, 2025

    @MitchellGoodwin
    Contributor

    Adding on: we've been pushing on improving Cupertino recently, but with a focus on doing work that either strengthens the whole framework, or targets work that would be excessively time consuming for an app developer to do themselves. We've been seeing a lot of success and improvements we are really excited about through work in the core framework area that benefits Flutter as a whole. We've been watching Material 3 Expressive coming down the pipes, and while the design is very exciting to us, the idea of pivoting from our current mindset to working on Expressive feels like going backwards. If we build out Expressive, we'd like to do it from the stronger foundations we are working on.

    Expressive is an interesting case too, since it represents an advancement in Material design, but, at least as of now, does not seem to be a requirement to implement in order to make your app look like it belongs on an Android device. So it provides an opportunity to consider alternative options. One of our more popular issues #101479 involves moving Cupertino and Material outside of the core framework, and Expressive could represent a good trial run of that. Us supporting the community as they flesh out Expressive feels more natural to what we should be doing.

    However we are very interested in hearing about and investigating what challenges would exist to make implementing Expressive difficult for the community. "I want to do X thing, and it would be much easier if I had Y tool, or it feels like the framework is fighting against me in Z way." are things that we want to hear, and are likely to be a sign in where we should focus our attention.

    To get ahead of things, "Is this because of layoffs/ lack of Google support/ is Google going to kill Flutter?" No. We do have limited resources and this is a part of an effort to make sure we are using those resources in a way that provides the most value to the community. But part of why we are considering this approach is because we feel like we are comfortable enough in where we are within Google that we can focus on the work that we think needs doing rather than rushing to get a product out the door that we all pay for later.

    So TLDR, we have no plans yet on how exactly we want to handle Expressive, but we are taking a look. As Kate said, we won't be taking PRs while we are "measuring twice".

  12. 80 remaining items

  13. bharathwajv commented on Dec 18, 2025

    @bharathwajv
  14. linghengqian commented on Jun 27, 2026

    @linghengqian

    The statement at https://m3.material.io/develop seems to indicate that Material 3 Expressive will not be implemented in Flutter.

    Material’s Android Views (MDC-Android), Flutter, and web libraries are in maintenance mode. They’re still available to use, but will no longer receive feature updates from Material.

    Image

    However, it appears the current issue is being iterated on at https://github.com/flutter/packages . Am I missing something? The https://m3.material.io/develop webpage appears to be for closed-source collaboration.

  15. guidezpl commented on Jun 30, 2026

    @guidezpl
    MemberAuthor

    Thanks for raising, let me get that fixed

  16. CarlosMendonca commented on Jun 30, 2026

    @CarlosMendonca

    @linghengqian, thanks for flagging this issue. The documentation on material.io is inaccurate, and we are already working with the Material team to fix it. Flutter remains fully committed to supporting both Cupertino and Material, and we will continue to follow both design systems closely. The decoupling effort mentioned in this issue is the first step toward becoming faster in delivering updates. Once that work lands, we will follow up with details on how M3 Expressive updates will gradually roll out in collaboration with other community members that have already implemented some features. For more details on our plans to develop M3 Expressive, check out the design proposal here.

  17. paadevelopments commented on Jul 28, 2026

    @paadevelopments
  18. TheLastFlame commented on Jul 29, 2026

    @TheLastFlame
    Contributor
  19. added 2 commits that reference this issue on Aug 14, 2026
  20. Henry-Hiles commented on Aug 17, 2026

    @Henry-Hiles

    Now that the packages are decoupled, is this being worked on?

  21. alex-medinsh commented on Aug 17, 2026

    @alex-medinsh
    Contributor
  22. added
    packageflutter/packages repository. See also p: labels.
    and removed
    frameworkflutter/packages/flutter repository. See also f: labels.
    on Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectc: new featureNothing broken; request for a new capabilityc: new widgetMust also have "c: new feature". Request for a new widget.customer: crowdAffects or could affect many people, though not necessarily a specific customer.p: material_uimaterial_ui package in flutter/packagespackageflutter/packages repository. See also p: labels.team-designOwned by Design Languages teamtriaged-designTriaged by Design Languages team

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions