Flutter team announces several packages to be discontinued

Help General
21

The conversation has continued on the team, and we’re is aware of the concerns that have been brought up here and elsewhere. I’m not sure I have anything else to say here re: outcomes or changes to the original decision. I believe the main outcome is that changes like this will be more inclusive of the community in future. I don’t think theres any intention to reverse the decision, nor do I believe there should be.

I do believe that our adaptive-app experience could (and should) be improved, but I don’t think this package is the answer. Improving the adaptive-app experience is on the radar of everyone the team, so I’m sure it’ll be prioritized at some point. But the long-short of it is that there are X number of resources on the team and maintaining these packages would require the team to have X+1 resources.

1000% agree.

IMO, The team should focus on building the primitives first and foremost. I don’t think striving for for 100% implementation of Material 3 spec (or any other spec) is worth the effort. (Importantly, a lot of folks on the team would probably disagree with me, and this is a personal opinion that doesn’t reflect the team’s overall position.)

3 Likes
22

Thanks for checking in on this in the meantime.

23

Where do I submit my application?

2 Likes
24

I’m new to the Flutter system. Do discontinued packages get pulled entirely and can no longer be used? Or is it just that further maintenance will not be done by the Flutter team? (but possibly someone who forks it)

1 Like
25

Keep in mind that publishing is forever. As soon as you publish your package, users can depend on it. Once they start doing that, removing the package would break theirs. To avoid that, the pub.dev policy disallows unpublishing packages except for very few cases.

But, then again, code rot is a thing… and it’s a problem on pub.dev.

1 Like
26

Thank you for your response.

1 Like