Choosing a Package on pub.dev

Sprout needs to send a notification when a plant is due. You could write that yourself for Android and iOS, or reuse a package that thousands of apps already rely on. pub.dev is where Dart and Flutter packages are published. Adding one takes seconds; picking the right one takes a minute of judgement.

The rule

Check platform, health and publisher before popularity.

Every package page on pub.dev shows signals at the top:

• Platform tags: Android, iOS, Web, Windows, macOS, Linux. If a platform you ship on is missing, stop there.
• Pub points: a score from automated checks on documentation, code analysis, platform support and up-to-date dependencies.
• Likes and downloads: how many developers use or appreciate it.
• Publisher: a verified publisher, shown with a badge and a domain, tells you who stands behind the package.
• Versions and changelog: recent releases suggest it is maintained.
• The Example, Installing and Versions tabs, plus a link to the source repository and its issues.

Some packages are also marked Flutter Favorite, a label given to packages the Flutter team recommends for quality.

A package page also says whether it is a Dart package (works anywhere Dart runs) or a Flutter plugin (contains platform code, so a full rebuild is needed after adding it).

The shortcut

Run the checks in the order that eliminates candidates fastest.

The trap is picking the package with the most likes. Popularity can outlive maintenance, and a well-liked package is no help if it does not support iOS.

Drills

Answer fast — trust the rule.

Remember

• Check platform, health and publisher before popularity.
• Order of checks: platforms, health, publisher and licence, then the example.
• Trap: choosing by likes alone.