Get your 12.
Keep them 14 days.
Ship.
Google Play will not let you publish until 12 testers stay opted in for 14 consecutive days. TesterPool puts you in a pod of 15 developers who test each other for the same 14 days. Everyone gets their twelve. Everyone graduates together.
The tester network that won’t get your app pulled.
- developers
- 1,247
- developers
- pods forming
- 38
- pods forming
- apps greenlit
- 9,318
- apps greenlit
- PRPriya Raman@priya_builds · IN · 96 rel
- TNTomas Novak@tnovak · CZ · 91 rel
- DODani Okafor@daniokafor · NG · 88 rel
- MLMei Lin Chow@meilin · MY · 84 rel
- OBOla Berg@olaberg · SE · 97 rel
Twelve testers. Fourteen consecutive days.
No exceptions.
Every personal developer account created after 13 November 2023 has to run a closed test with at least 12 testers opted in continuously for 14 days before Google will even consider production access. Miss it by one tester on one day and the count starts over.
Day 14 arrives with twelve continuous opt-ins on record. You apply for production access with real engagement behind you.
You drop to eleven. The continuous-14-day count starts again from zero, and you find out weeks later when the application is rejected. This is the single most common way a launch slips a month.
It is not just twelve bodies
Applications get rejected for low engagement. Google asks how active your testers were and what feedback you acted on. Twelve silent installs is a rejection with extra steps.
The clock is invisible
The Play Console does not show you a live 14-day counter per tester. Most developers discover a broken streak only when the rejection email arrives.
A reset costs a month
Fourteen more days of testing, plus review time, plus the fixes you now have to squeeze in. Indie launch windows do not survive that twice.
Three steps, then you stop thinking about it
TesterPool is barter, not a marketplace. You are not buying testers; you are joining fifteen people who all need the same thing in the same fortnight.
List your app
Paste your Play closed-track opt-in link or Google Group, add a one-line brief and the two or three things you want testers to hammer. Two minutes.
Opt-in link validated before your pod starts — a broken link is the #1 silent killer.
Join a pod of 15
Fifteen developers, all shipping in the same window, all matched on device mix and timezone spread. Twelve is the requirement; fifteen is what you get.
Free pods typically fill in 3–6 days. Fast Pod starts within 24 hours.
Everyone tests everyone for 14 days
One shared clock. Daily check-in with screenshot proof, then one structured feedback report per app at the end. Your dashboard shows exactly who is holding and who is slipping.
Someone drops? A rescue tester is matched in hours, not days.
Day 15: your Evidence Pack is ready, your app is on the Launch Feed, and you apply with numbers instead of hope.
What you would otherwise be choosing between
We are not going to pretend the free tier is faster than paying a stranger $20. It is not. Everything else on this table, we win outright.
| What matters | TesterPool | Review-swap sites | $20 Fiverr gigs | Friends & family |
|---|---|---|---|---|
| Policy riskThe one that ends your account | None. Closed track only, never a review or rating | High. Incentivised reviews and installs are explicitly banned | Depends entirely on the seller; many quietly buy installs | None |
| Testers who actually open the app | Daily check-in with screenshot proof, tracked per tester | Opt-in and vanish; engagement is not the product | Usually one install, then silence for 14 days | Enthusiastic for four days, then they forget |
| Dropout replacement | Rescue tester matched in hours, included on paid plans | Not offered | Re-order and wait, if the seller is still online | You start asking again |
| Written feedback | One structured, on-rubric report per tester, privately | A five-star string you did not want | Occasionally a paragraph; rarely actionable | “Looks nice” |
| Evidence for your applicationGoogle asks for engagement levels and a feedback summary | Production Evidence Pack, generated and formatted | Nothing you could paste into the form | A screenshot of a chat thread | You write it from memory |
| Buffer above the 12 required | 15 seats free, 18 on Fast Pod, 20 on Pro | Sold as an upsell, if at all | Buy 12, pay again for more | You are lucky to reach 12 |
| Time to startWhere money genuinely buys speed | Free pods fill in 3–6 days; Fast Pod within 24 hours | Immediate | Immediate — the honest advantage of paying a stranger | As fast as people reply |
| Cost | Free if you test back, $19 if you would rather not | $15–$40, plus the risk premium you cannot price | $5–$40 per run, repeat every failed attempt | Free, paid in favours |
Prices observed across public tester-service listings, 2025. Review-swap behaviour describes services that exchange store ratings or reviews — the category Google’s policy names directly.
Nothing TesterPool does ever touches the public store
All activity happens inside your closed testing track. Closed track installs and usage do not affect store rankings, public ratings, or public install counts — they are invisible to the store surface entirely. There is nothing here for Google’s anti-manipulation systems to object to, because there is no public signal being manufactured.
Google’s developer community guidance is explicit that using a third-party service to find testers for a closed test does not violate policy. What Google prohibits is incentivising ratings, reviews and installs — and that is precisely the thing TesterPool refuses to sell. We have no product to offer you there. The database schema behind this site has no column that can hold a store review or a public rating; it was designed that way on purpose.
Feedback on TesterPool is private, structured and delivered to you — never posted anywhere public. If a tester tried to trade a five-star review for credits, there would be no mechanism to pay them.
The Reliability Score is the whole trick
Every other free tester scheme dies the same way: people opt in, collect what they need, and disappear on day four. TesterPool makes disappearing the most expensive thing you can do.
Shown on every profile, every pod roster and the leaderboard. Below 40 you cannot join a pod at all.
Check in every day
Your score climbs, and your seat stays clean
Finish a perfect streak
A Perfect 14 badge and your best score bump
Rescue someone mid-pod
+50 credits and a lasting score bump
Drop out mid-pod
−120 credits, a score collapse, and a lockout from pods
You are testing alongside people whose next launch depends on the same system working. That is a much stronger incentive than $20 ever was, and it is why pods finish at rates a marketplace cannot reach.
Answer the application with numbers, not adjectives
Google's production access form asks how engaged your testers were and what feedback you collected. Most developers answer from memory. You will answer from a generated document.
“Testers reported the onboarding flow stalling on Android 12 when notification permission was declined (4 reports). Fixed in 1.4.2 and confirmed by three testers. Offline sync was the most requested improvement (7 reports); partial sync shipped in 1.4.3. Two testers on low-end devices flagged a 2.8s cold start, reduced to 1.1s.”
Credits price the edges, never the core
Credits move between developers, they are never minted. What a tester earns comes out of the balance of the developer whose app they tested — so doing your share costs nothing, and skipping it costs exactly what it should.
- +10Confirmed installyour closed-track opt-in, verified
- +30Confirmed reporton-rubric, arbitrated
The same number, because it is the same number. Credits move between developers; nothing here mints them. A full pod earns you 560 and costs you 560, so doing your share breaks exactly even — and the currency cannot inflate, because every credit anyone earns came out of somebody’s balance.
- 145Buffer seatOne more tester above the 15 you already have
- 260Rescue seatA verified replacement, matched within hours
- 400Priority podFront of the matching queue
- 300Expert seatA long-form report from a senior tester
- 200Second appRun two apps through pods at once
Enough for a buffer seat before you have tested anything. Invite another developer and you both benefit: 75 credits for you, 50 for them.
Free if you test back. Cheap if you would rather not.
Every plan includes the buffer seats, the engagement tracking, the structured feedback and the Evidence Pack. Paying only ever buys you speed and insurance.
Free
Earn your seat by testing.
- Join a forming pod (typically 3–6 days to fill)
- 15 seats for a 12-tester requirement
- 600 credits to start — one full pod, on us
- Up to 10 installs and 10 reports a day
- Production Evidence Pack
Unlimited
Test as much as you like. Earn as fast as you can.
- No daily limit — free members bank 10 installs and 10 reports a day
- Clear a whole pod in an afternoon instead of two days
- Earn credits faster than you spend them
- A 30-day pass, bought once — no auto-renewal to cancel
- Everything in Free
Fast Pod
Skip the queue. Start tomorrow.
- Guaranteed pod start within 24 hours
- 18 seats — six spare, not three
- Free rescue tester if anyone drops
- Priority in the matching pool
- Everything in Free
Pro
For the launch you cannot afford to redo.
- 20 seats, all reliability 85+
- Two expert testers who write long-form reports
- Unlimited rescue replacements
- Reviewed Evidence Pack + application draft
- Priority arbitration and support
Rescue
Someone dropped on day 10. Fix it in hours.
- One verified replacement tester
- Matched within 6 hours
- Opt-in verified before you are charged
- Available to any plan, any time
One-off pricing per app, not a subscription. If your pod fails to reach 12 verified testers, a paid plan is refunded in full.
Developers who stopped restarting the clock
“I had eleven testers twice and got rejected twice. Joined a pod on a Tuesday, applied on day 15 with the evidence pack attached, approved first try. The part that actually mattered was the engagement numbers — I had never been able to prove them before.”
“Two people went quiet around day 6. On any other service that is a month lost. Here the dashboard flagged it the same morning and both seats were refilled by the next day, and I still had buffer left over. I never dropped below twelve.”
“I tested four apps while mine was in the pod and it cost me maybe six minutes a day. The feedback I got back was better than the paid QA round I did last year — someone found a crash on a Xiaomi device I do not own.”
The ones that decide it
Is this against Google Play policy?
No, and the distinction is worth being precise about. Google prohibits incentivised ratings, reviews and installs — paying or rewarding someone to leave a five-star review or to install from the production store listing. TesterPool has no mechanism for any of those. There is no field in our system that can hold a store review or a public rating, by design.
Everything on TesterPool happens inside your closed testing track. Closed track installs do not affect your store ranking, your public rating, or your public install count. Google’s own developer community guidance is that using a third-party testing service to find testers does not violate policy; what violates policy is buying engagement signals that reach the public store. We deliberately do not sell those.
What if someone drops out?
First, it usually does not matter. You get 15 seats for a 12-tester requirement, so three people can vanish and you still clear the bar. Competitors sell that buffer as an upsell; it is our default.
Second, we replace them. If a tester goes quiet, your dashboard flags it the same day and you can send a rescue request — a verified replacement matched from the rescue pool, typically within six hours. Rescue testers earn a bonus of 50 credits, which is why the pool is staffed. On Fast Pod and Pro, rescues are included.
Third, dropping out is expensive for the person who does it: it costs 120 credits and a serious hit to their Reliability Score, which locks them out of pods below 40. Nobody ghosts a pod twice.
Do I have to test other people’s apps?
On the free tier, yes — that is the trade, and it is what makes the network honest. Testing one app costs roughly five minutes a day: open it, do the thing, tap check-in. Testing every app in a full pod earns 560 credits — exactly what your own pod costs you, so doing your share breaks even. If you would rather not, Fast Pod at $19 buys you a seat without reciprocating.
How long until my pod starts?
Free pods fill in three to six days depending on your device requirements and how many pods are forming that week. Fast Pod guarantees a start within 24 hours. We will be blunt: if you need testers this afternoon, a Fiverr gig is faster than our free tier. It is also the one most likely to get your account flagged.
What exactly is in the Production Evidence Pack?
The numbers Google’s production access form actually asks for: how many testers you had, how many completed all 14 days, average days active, daily engagement rate, the number of approved feedback reports, how many raised significant issues, and a written digest of what testers said and what you changed in response. It exports as a document you can paste from. Pro plans get it reviewed by a human before you submit.
Can I use TesterPool for iOS TestFlight?
Android closed testing is what we do properly today, because the 12/14 rule is the specific bottleneck we were built to break. TestFlight pods are in limited beta — the same pod mechanics, the same reliability system, no 14-day requirement to satisfy. Ask for access when you sign up.
Your fourteen days start whenever you do
600 credits when you sign up, 15 seats for a 12-tester requirement, and an Evidence Pack waiting on day 15.
No card required. No store reviews. No policy risk.