Looking for maintainers

[aqwert]

Hi community,

I have been owning and maintaining this package for nearly 7 years back when Flutter was still in Beta. It started out as a "lets see if it is possible" to unify the Material and Cupertino widgets under a single Widget. Over the years more and more widgets have been added, some straightforward some a bit opinionated in order to maintain a single widget interface to bring Material and Cupertino styles apps without too much fuss and to save time for developers.

However over the past year, for personal reasons the level of commitment I needed (and wanted) to level up the package has not been at the standard I would like it to be. As such I want to bring in a couple of maintainers that can spare the time to do the following:

• Upgrade the package to match the interface of the latest Flutter stable release. Each release may introduce new parameters to either the material or cupertino widgets or add new widgets that can be wrapped into a singular widget that we can add here.
• Review the PRs from contributors, provide feedback and to merge into the main branch.
• Upload new versions into pub.dev.
• Resolve any issues raised and come up with appropriate pragmatic solutions.
• Keep the wiki documentation up to date.

What I am asking for is an indication from the community who are willing to being a maintainer. Please leave a comment / emoji if you are interested. Ideally the right people have FOSS experience and have a good understanding of the dart language and Flutter framework. I will review interest and communicate who will become maintainers.

Thanks

[M-Ahal]

I'm using this for an app that would shortly be in production. So I'd be definitely vested in it.

[LahaLuhem]

And I've forked it into a more heavy-handed extension for the remaining platforms called flutter_extended_platform_widgets. This would be a very niche use-case, and that's the reason for the fork. And I depend on updates to this base (upstream) for it make it downstream, so I'd like to contribute more too

[aqwert]

@M-Ahal & @LahaLuhem . Would you want to be a maintainer to this project? At most I can only support major versions of flutter with adding params but I would not have the capacity beyond that.
Other people willing to help maintain would also be welcome

[M-Ahal]

Yes, I'd be up for it. I'd like some amount of support and reviewing of say my PRs as possible, as a sanity check?

[fuzailkhannn]

Hey, I would like this package to not wither away and I would like to contribute to its maintenance so all of us devs can enjoy its feature without worrying about when the package will expire and their app would crash. I would love to be a part of this team.

[LahaLuhem]

I agree with @fuzailkhannn . This is a very close and nice attempt to a 'cross-platform' development in terms of the UI/UX too. And I'd love to keep maintaining it till I can.
@aqwert Let us know what you think...

[TeeWrath]

Hi @aqwert , I use this package in almost all of my flutter projects, been using this for over 2 years now. Would love to help shape its future.

[gmr-renato]

I started to implement the same thing that this package is doing. I would love to help and contribute.

[LahaLuhem]

Google has announced that they would be decoupling the libraries.
https://youtu.be/W4olXg91iX8?t=489

The deprecating the existing libraries mash will start in early 2026. It is even more important that this project is urgently (re-)worked on.

@aqwert
By late 2026, the new Flutter SDKs are predicted to ship without Material and Cupertino libraries without them. And that would otherwise mark a hard end to this project