Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When will Material 2 (useMaterial3: false) be deprecated? #141555

Closed
Gobmichet opened this issue Jan 15, 2024 · 8 comments
Closed

When will Material 2 (useMaterial3: false) be deprecated? #141555

Gobmichet opened this issue Jan 15, 2024 · 8 comments
Labels
f: material design flutter/packages/flutter/material repository. framework flutter/packages/flutter repository. See also f: labels. P2 Important issues not at the top of the work list r: duplicate Issue is closed as a duplicate of an existing issue team-design Owned by Design Languages team triaged-design Triaged by Design Languages team

Comments

@Gobmichet
Copy link

Hi,

Material 3 recently became default with flutter 3.16.

However, Id' like to know until when will we be able to use :
useMaterial3: false,

In order to continue to use Material 2 'cause Material 3 just destroys our apps UI and we will have some work to migrate all of them...

Do we have a date ?

Will we be able to force Material 2 in our flutter apps ad vitam eternam ?

Would love it 'cause i really prefer Material 2 ! (0_o)

@huycozy huycozy added the in triage Presently being triaged by the triage team label Jan 15, 2024
@huycozy
Copy link
Member

huycozy commented Jan 15, 2024

Per Migration guide:

You can still opt out of the Material 3 version of the Material library by specifying useMaterial3: false in your MaterialApp theme.

Doesn't it work on your project? If so, could you be more specific with a specific case (sample code, steps to reproduce)?

When opening an issue, please try to provide all information indicated in the template so that we can address this issue properly (See bug issue template here).

@huycozy huycozy added the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Jan 15, 2024
@Gobmichet
Copy link
Author

Yes it does work, but i'd want to know until when ? because i read this :
Capture

And my problem is to know until when will it work ?

When won't we be able to force the Material2 design for our apps anymore ?

It is very important for us to know that in order to plan our app(s)'s migration(s) (and customization(s) in order to keep the same UI even though passing from Material 2 to 3...)

Thanks in advance.

@github-actions github-actions bot removed the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Jan 15, 2024
@zambetpentru
Copy link

zambetpentru commented Jan 15, 2024

The question I haven't wanted to ask! Hopefully it is kept for quite a long time as it is quite a change to evaluate across our apps and Material 2 works very nicely today for us - is there a Material 3 theme to mimic the size, colour and spacings of Material 2?

*I don't have a problem with breaking changes in general, the challenge with this one is it requires visual redesign.

@huycozy huycozy added framework flutter/packages/flutter repository. See also f: labels. f: material design flutter/packages/flutter/material repository. team-design Owned by Design Languages team and removed in triage Presently being triaged by the triage team labels Jan 16, 2024
@huycozy
Copy link
Member

huycozy commented Jan 16, 2024

Per Deprecation policy:

Deprecated APIs are removed after a migration grace period. This grace period is one calendar year after being released on the stable channel, or after 4 stable releases, whichever is longer.

But I'm not pretty sure when it's applied for useMaterial3 so I will keep this for other's input.

@huycozy huycozy changed the title [ Material 2 vs 3 ] When will Material 2 (useMaterial3: false) be deprecated? Jan 16, 2024
@HansMuller
Copy link
Contributor

Before we deprecate useMaterial3: false we'll introduce, likely in a separate package, an M2 compatibility theme that preserves as much of the M2 L&F as possible. We'd definitely prefer that developers migrate to M3 but understand that some of the small changes in text styles and the color scheme can be troublesome for existing apps.

CC @QuncCccccc, @TahaTesser, @Piinks

@HansMuller HansMuller added P2 Important issues not at the top of the work list triaged-design Triaged by Design Languages team labels Jan 17, 2024
@Gobmichet
Copy link
Author

Gobmichet commented Feb 15, 2024

Thanks @HansMuller !
Didnt saw those lines !

That's good news :)

Any idea of a date though ?
Even hypothetic ?

@Piinks
Copy link
Contributor

Piinks commented Feb 15, 2024

Closing in favor of #143499 as this is a question rather than an action item.
We're currently working on a backwards compatibility solution for M2, which would be established well before the useMaterial3 flag is deprecated and removed.

@Piinks Piinks closed this as completed Feb 15, 2024
@danagbemava-nc danagbemava-nc added the r: duplicate Issue is closed as a duplicate of an existing issue label Feb 15, 2024
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
f: material design flutter/packages/flutter/material repository. framework flutter/packages/flutter repository. See also f: labels. P2 Important issues not at the top of the work list r: duplicate Issue is closed as a duplicate of an existing issue team-design Owned by Design Languages team triaged-design Triaged by Design Languages team
Projects
None yet
Development

No branches or pull requests

6 participants