Flutter Favorite program

The aim of the Flutter Favorite program is to identifypackages and plugins that you should first consider whenbuilding your app.This is not a guarantee of quality or suitability to yourparticular situation—you should always perform yourown evaluation of packages and plugins for your project.

Metrics

Flutter Favorite packages have passed high quality standardsusing the following metrics:

• Overall package score
• Permissive license,including (but not limited to)Apache, Artistic, BSD, CC BY, MIT, MS-PL and W3C
• GitHub version tag matches the current version frompub.dev, so you can see exactly what source is in the package
• Feature completeness—and not marked as incomplete(for example, with labels like “beta” or “under construction”)
• Verified publisher
• General usability when it comes to the overview,docs, sample/example code, and API quality
• Good runtime behavior in terms of CPU and memory usage
• High quality dependencies

Flutter Ecosystem Committee

The Flutter Ecosystem Committee (FEC) is comprised of Flutterteam members and Flutter community members spreadacross its ecosystem. One of the their jobs is to decide when a packagehas met the quality bar to become a Flutter Favorite.

The current committee members (in alphhabetical order)are as follows:

• Pooja Bhaumik
• Hillel Coren
• Thea Flowers
• Simon Lightfoot
• Lara Martín
• Chris Sells (committee chair)
• Michael Thomsen
• Diego Velasquez
• Kyle Wang

If you’d like to nominate a package or plugin as apotential future Flutter Favorite, or would liketo bring any other issues to the attention of the committee,send the committee chair an email.

Flutter Favorite usage guidelines

Flutter Favorite packages will be labeled as such on pub.devby the Flutter team.If you own a package that has been designated as a Flutter Favorite,you must adhere to the following guidelines:

• Flutter Favorite package authors may place the Flutter Favoritelogo in the package’s GitHub README, on the package’spub.dev Overview tab,and on social media as related to posts about that package.
• We encourage you to use the #FlutterFavorite hashtag in social media.
• When using the Flutter Favorite logo,the author must link to (this) Flutter Favorite landing page,to provide context for the designation.
• If a Flutter Favorite package loses its Flutter Favorite status,the author will be notified,at which point the author must immediately remove all usesof “Flutter Favorite” and the Flutter Favorite logo fromthe affected package.
• Don’t alter, distort, or modify the Flutter Favorite logo in any way,including displaying the logo with color variations or unapprovedvisual elements.
• Don’t display the Flutter Favorite logo in a manner that is misleading,unfair, defamatory, infringing, libelous, disparaging,obscene, or otherwise objectionable to Google.

What’s next

You should expect the list of Flutter Favorite packagesto grow and change as the ecosystem continues to thrive.The committee will continue working with package authorsto increase quality, as well as consider other areas of theecosystem that could benefit from the Flutter Favorite program,such as tools, consulting firms, and prolific Flutter contributors.

As the Flutter ecosystem grows,we’ll be looking at expanding the set of metrics,which might include the following:

• Use of the new pubspec.yaml format that clearlyindicates which platforms are supported.
• Support for the latest stable version of Flutter.
• Support for AndroidX.
• Support for multiple platforms, such as web, macOS,Windows, Linux, etc.
• Integration as well as unit test coverage.

Flutter Favorites

You can see the complete list ofFlutter Favorite packages on pub.dev.