People ghost
Friends and random pools install once, reply «done», and disappear before day 14.
Mutual Android testing · SDK proof · On Google Play
Stop guessing who tested your app
Dozenflow is a reciprocal testing network for Play closed tests. Swap builds with other Android developers — and prove real opens with the Closed Test SDK in anyapp, not screenshots in chat.
- Same-day session proof
- 12×14 campaign signals
- Free while network grows
Built for Google Play closed & internal testing · SDK on Maven Central · Complements Play Console
The problem
Closed testing fails on trust, not intent
You need reciprocal testers and proof they actually use your build — Play Console alone often tells you too late.
Chat is not proof
Screenshots and «I tested» messages do not show sustained opens across the closed-test window.
Play stats lag
Console updates in batches. A weak UTC day can break momentum before you notice.
The fix
Mutual obligations + SDK proof
Exchange testing with developers who need the same thing you do. The SDK in your APK reports sessions — Dozenflow shows who fulfilled today.
Reciprocal network
You test their anyapp; they test yours. Invites are accepted on both sides — no silent auto-enroll into strangers' tests.
Trust engine
Closed Test SDK sends session signals from the build testers install. Organizers see roster slots, Stats, and 12×14 progress.
Connections built in
Google Group join URL and Play invite link live on the test card — reciprocal testers know exactly how to join your track.
Not a paid catalog of «300 testers for $». A trusted network with proof — recommendations over a blind warehouse.
How it works
Live in four moves
-
Add the SDK to anyapp
Maven dependency + init with owner email, Google Group URL, and Play invite link.
SDK guide → -
Install Dozenflow
Organizer app on Google Play — manage tests, Stats, reminders, and mutual invites.
Google Play → -
Open your build once
First SDK init creates the test card on the server — required before Connections work.
-
Exchange & prove
Set Connections, swap reciprocal tests as the network opens, watch real opens in Stats.
Full setup checklist →
Inside the app
Proof you can act on today
Not vanity metrics — signals that tell you whether today's closed-test day is on track.
Tap any screenshot to enlarge. Testers usually only need your Play build — not Dozenflow.
Why switch
Better than chat + spreadsheets
Without Dozenflow
- «Trust me» messages in Telegram
- Manual headcount in a sheet
- Play Console tells you yesterday's story
- No idea who went quiet mid-campaign
With Dozenflow
- SDK sessions from real anyapp opens
- Same-day roster slots and Stats
- 12×14 signals while the day is still running
- Tap a slot → see who and remind them
Two pieces
One workflow
Dozenflow app Organizer
Tests, Stats, Connections, reminders, mutual network — on your phone.
Install: Google Play
Closed Test SDK In anyapp
One Maven line in the APK testers install. Init with email + Group + invite — proof starts on first open.
Integrate: SDK guide
anyapp ≠ Dozenflow. Testers do not need the organizer app for basic SDK telemetry.
Built for
Android developers who trade tests
- Indie publishers preparing Play closed testing with a small network
- Studios without QA ops who need reciprocal help, not a hire catalog
- Developers already swapping builds who want proof the other side opened the app
Questions
- How do I get started?
- Follow the 4-step guide: SDK in anyapp → install Dozenflow → open your build once → set Connections.
- Do testers need Dozenflow?
- No for basic telemetry — they only need your Play build with the SDK. A Dozenflow account helps when joining the mutual network.
- What is anyapp?
- Your Android app under test. Embed the Closed Test SDK there — it is not the Dozenflow organizer app.
- Is this a tester marketplace?
- Yes — a reciprocal mutual-testing network with SDK proof. Not a paid list of strangers; no global browse catalog on this site yet.
- Does Dozenflow guarantee Play approval?
- No tool does. We help you see participation and run mutual tests fairly — Play policies remain your responsibility.
Your next closed test deserves proof
Add the SDK, install Dozenflow, open your build once — then swap tests with developers who show up.