If you have ever shipped a beta through Firebase App Distribution and then wondered why Google Play still says you have not completed closed testing, you are not alone. The two tools look similar — both get a pre-release build onto real phones — but Google Play only counts one of them.
Here is the difference, and how to stop wasting a test cycle on the wrong tool.
What Firebase App Distribution actually does
Firebase App Distribution is a fast way to send a build to a list of testers. You upload an APK or AAB, pick testers by email, and they install it. It is great for quick feedback loops, crash reports, and getting a build in front of stakeholders before a store release.
What it is not: a Google Play track. Nothing you do in Firebase shows up in Play Console's testing history, and Google's production access review cannot see it.
What Play Console closed testing does
A closed testing track in Play Console is the only testing Google counts toward the 12 testers for 14 days requirement. Testers opt in through a Play-generated link, install from the Play Store, and Google records their engagement on its own timeline.
That recorded history is the entire point. The production access form does not ask "did anyone test your app?" — it asks for evidence inside Play Console.
The mistake: treating them as interchangeable
A common indie workflow looks like this: distribute the build on Firebase, collect feedback for two weeks, fix bugs, then apply for production access — and get rejected because Play Console shows zero days of closed testing.
The Firebase test was real testing. It just does not count for the requirement. Two weeks of genuine feedback, zero days on Google's clock.
When to use each
Use Firebase App Distribution when you need fast, informal feedback — a design review, a smoke test with your team, a build for a client demo. It is the quicker tool for all of those.
Use Play Console closed testing when you are working toward production access. Start the closed track early, even if the build is rough. The 14-day clock only runs on the Play track, and every day you spend only on Firebase is a day the clock is not running.
Can you use both at the same time?
Yes — and for many teams that is the right answer. Run your rapid feedback loop on Firebase, and keep the same build (or a matching one) on the Play closed track with your 12 testers opted in. You get fast feedback and a running clock at the same time.
Just do not confuse the two timelines. Firebase feedback does not extend, replace, or backfill your 14 days in Play Console.
The 12-tester problem neither tool solves
Both tools assume you already have testers. Firebase needs an email list; Play Console needs 12 opted-in testers who stay engaged for 14 continuous days. Finding 12 real people with Android phones, keeping them installed, and replacing the ones who drop out is the part no distribution tool handles.
That is exactly what VerifiedTesters handles: 12 real testers on their own Android phones, opted in on your Play Console closed track and engaged for 14 continuous days, with free dropout replacement and a final report built for the production access form.
Use Firebase for speed. Use Play Console closed testing for the requirement. And get the 12 testers from someone whose job is keeping them there.
Top comments (0)