Flutter plugin readiness board and CLI

A nightly public board and a CLI showing which Flutter plugins will block your next iOS or Android release.

For HireFlutter, an Integrity Ventures brand Platform Web, CLI Built in 3 days 142 tests, all passing

Flutter plugin readiness board and CLI, running

The live board on 28 Sep 2026: 83 of the 145 most-downloaded iOS plugins still block apps.

More screenshots

Flutter plugin readiness board and CLI, screenshot 2

Flutter plugin readiness board and CLI, screenshot 3

Flutter plugin readiness board and CLI, screenshot 4

The brief

Flutter teams are about to hit a wall they can't see. CocoaPods goes read-only on 2 December, and a lot of the plugins we all depend on still don't ship Swift Package Manager support. On Android, Play now wants API 36 and 16 KB-aligned native libraries. Today you find out which plugin blocks you one app at a time, usually the day a release fails.
I want a public page, live on ready.hireflutter.dev, that shows the most-used plugins on pub.dev and whether each one is ready for all three, refreshed every night. I also want a command I can run in my own app, on my machine or in CI, that tells me which of my plugins will block my next release and what to switch to.
Open source, published on pub.dev under hireflutter.dev, and live before 2 December.

My brief, written before work started, unedited.

What was delivered

A public board of the most-downloaded Flutter plugins, rechecked every night
Checks each plugin for Swift Package Manager support before CocoaPods goes read-only
Checks Android plugins for 16 KB-aligned native libraries and shows their build settings
A page for every plugin, showing the evidence behind its verdict
A command you run in your own app to see which plugins will block your release
Suggested replacements for plugins that are blocked
A GitHub Action that runs the same check in CI
Open source under MIT, published on pub.dev under hireflutter.dev

How long it took

Sat 26 Sep
Brief written and committed before any work started
Sat 26 Sep
Plugin discovery and the shared readiness checks
Sun 27 Sep
Command-line check, and the board live on AWS with blocked plugins first
Sun 27 Sep
Board redesigned in HireFlutter's brand
Mon 28 Sep
Published on pub.dev as flutter_ready 0.1.0, under hireflutter.dev

Check it yourself

142 automated tests, all passing The raw test run, the commits and the repository.

$ cd packages/flutter_ready && dart test
00:00 +0: test/swiftpm_check_test.dart: checkSwiftPmReadiness tag and archive agree: both say ready
00:00 +1: test/swiftpm_check_test.dart: checkSwiftPmReadiness tag and archive agree: neither says ready
00:00 +2: test/swiftpm_check_test.dart: checkSwiftPmReadiness disagreement: tag says ready but no Package.swift in the archive
00:00 +3: test/swiftpm_check_test.dart: checkSwiftPmReadiness disagreement: archive has Package.swift but the tag is absent
00:00 +4: test/swiftpm_check_test.dart: checkSwiftPmReadiness matches a darwin/ Package.swift as well as ios/ and macos/
…
00:02 +96: All tests passed!

$ cd packages/snapshot_job && dart test
00:00 +0: test/snapshot_assembler_test.dart: assembleSnapshot: federated plugin checks the federated ios/android packages, tag stays app-facing
00:00 +1: test/snapshot_assembler_test.dart: assembleSnapshot: non-federated plugin checks the plugin's own archive once for both ios and android
00:00 +2: test/snapshot_assembler_test.dart: assembleSnapshot: iOS resolution rework (e2-s1) path_provider shape: a dartPluginClass-only federated package is not native iOS
00:00 +3: test/snapshot_assembler_test.dart: assembleSnapshot: iOS resolution rework (e2-s1) flutter_keyboard_visibility shape: an inline iOS pluginClass is never resolved via the macOS default_package
…
00:00 +10: All tests passed!

$ cd site && dart test
00:00 +0: test/header_footer_test.dart: Header (the one-row top bar every page shares) renders the HireFlutter.dev wordmark linking home and the Powered by 10xs pill
  - ensure that a '.client.dart' file with the same name as the '.server.dart' entrypoint exists, or
  - add a `script(src: '<filename>.client.dart.js', defer: true)` to `Document(head: [...])` manually.
00:00 +1: test/header_footer_test.dart: Hero (the page title plus one line of explanation) renders the Flutter Ready title and the given subtitle
00:00 +2: test/header_footer_test.dart: Footer (the company credit on every page) renders "Integrity Ventures Private Limited" linking to ivp.life
…
00:01 +36: All tests passed!

Commitsf9cc6437b4ef02578e3f60b7b8400a7511d7cea5737b4b3900d1cc3e

github.com/Integrity-Ventures/flutter-ready →

Let's talk about your project