Get your app reviewed
by 14 developers.
Then ship it.
List your app and 14 indie developers install it, use it for 14 days, and each send you one structured review — what broke, on which device, what they would change. You hear it from people who ship Android apps before you hear it from your users, and Google Play’s 12-testers-for-14-days requirement is satisfied on the way through.
Private developer reviews, inside your own closed testing track. Not Play Store reviews — those are incentivised the moment they are traded, and Google removes apps for it. That is the difference between the reviews you want and the ones that cost you the account.
- reviews on your app
- 14
- reviews on your app
- seats, so 3 can vanish and you still clear 12
- 15
- seats, so 3 can vanish and you still clear 12
- credits to start
- 600
- credits to start
You pay for them by reviewing other people’s apps. Credits move between members and testing never creates them, so the loop cannot be farmed and doing your share costs you nothing.
- DOSeverity 2@daniokafor · Pixel 6a · A13
Export to Markdown silently does nothing when the note has an attachment. No error, no file.
- PRSeverity 3@priya_builds · Redmi Note 12
Hard crash on rotate while the sync sheet is open. Repro steps attached, twice on two devices.
- OB+30@olaberg · Galaxy S21
Offline editing held up on the underground. Move the attachment button out of the overflow menu.
Every one of them private, structured, and written by someone who has shipped an Android app. None of them anywhere near your store listing.
One of the reviews, in full
This is the screen a developer sees, rendered by the same component the product uses — an example of the format, not a real member’s report. 14 of these land on your app over 14 days.
Understood what it was for from the first screen, which is rarer than it sounds. Started a note within about fifteen seconds of opening it.
Offline editing held up on the underground with no sync errors when I came back up. Undo across app restarts is genuinely good.
Export to Markdown silently does nothing when the note has an attachment. No error, no file, no toast.
1. New note, type anything 2. Attach any image 3. Menu → Export → Markdown 4. Nothing happens. Repeats on a second device.
Move the attachment button out of the overflow menu. I found it by accident on day four and I was looking for it on day one.
Written against your rubric, not theirs
You name the two or three things you want hammered when you list the app. The review answers those. A review that ignores them does not get paid, which is why nobody sends you “looks nice”.
A blocker costs you exactly what a compliment costs
Every approved review charges the same 30 credits whatever it says. If critical feedback were dearer you would learn to dispute it, and the bounty on a blocker is funded by us for the same reason: finding your worst bug must never cost you most.
You cannot quietly refuse to pay for it
Flagging a review as low-effort opens a moderator dispute. It does not reject the review and it does not withhold the tester’s credits — a human decides. Creator approval without that step is a positivity machine, which is the exact failure this was built against.
By reviewing other people’s apps
Fourteen reviews is real work by fourteen people, so the price is that you do it too. Here is all of it — three things, none of which take an evening.
Opt in
+10One tap on the developer’s closed-track link. You are in their testing track, which is the only place any of this happens.
Confirmed by screenshot proof reviewed on our side, never by your own word — that is why the credits are worth something.
Use it
Pays nothingActually use the app, then log the session. Ten seconds. Staying opted in is the part Google measures, so it is the part that counts.
Logging a session pays nothing on purpose. It builds your Reliability Score, which is what lets you hold more work at once.
Review
+30One structured review against the two or three things the developer asked you to hammer: what broke, what confused you, what you would change.
A blocker pays the same as a compliment, plus a 15-credit bounty we fund ourselves. Finding the worst bug must never cost the developer most.
A review takes about ten minutes. 14 of them is the entire cost of getting your own app to production — 560 credits out as a developer, 560 back in as a tester. Do your share and you break exactly even.
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 — which is why the number of testers you ask for should be more than twelve, and why this is a listing you keep open rather than a batch you run once.
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 anyone can join — a broken link is the #1 silent killer.
Developers pick it up from the feed
Your listing sits in front of every developer here. They take it one at a time, join your closed track and stay opted in — no cohort to fill, no start date to wait for.
You set how many testers you want. Most listings see their first the same day.
Each one installs, uses it, and reports
Screenshot proof on the way in, then one structured review written against your brief. Your dashboard shows who has installed, who has reported and what it cost.
Someone takes a seat and vanishes? It frees up and goes back in the feed.
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 |
|---|---|---|---|---|
| Written reviews you can act onThe reason you came | One structured, on-rubric review per tester, privately — 14 of them | A five-star string you did not want, and cannot use | Occasionally a paragraph; rarely actionable | “Looks nice” |
| What happens if it works too wellThe downside nobody prices | Nothing. Closed tracks are invisible to the store surface | A cluster of accounts trading public reviews is the pattern enforcement looks for, and termination travels between linked accounts | You are one of many buyers of the same seller’s accounts | Nothing |
| 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 | Enthusiastic for four days, then they forget |
| Dropout replacement | The seat frees up and goes straight back in the feed | Not offered | Re-order and wait, if the seller is still online | You start asking again |
| 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 | Ask for as many as you can fund; 18 on Fast Track, 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 | Listed in two minutes; testers arrive as they browse | 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.
The Reliability Score is the whole trick
Every other free tester scheme dies the same way: people opt in, collect what they need, disappear on day four, and the reviews you do get are four words long. TesterPool makes both of those the most expensive things you can do.
Shown on every profile, every listing and the leaderboard. Below 40 you cannot take work at all.
Finish what you take on
Your score climbs, and you can hold more at once
Write a report they act on
Your best score bump, and a badge for the specific ones
Take an abandoned seat
+50 credits and a lasting score bump
Take a seat and vanish
−120 credits, a score collapse, and a lockout
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 the reports here are worth reading at all.
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 move. Testing never mints them.
This is the property the whole network rests on, so it is worth stating before the price list. Every credit a reviewer earns came out of the balance of the developer whose app they reviewed — no amount of work creates one, which is why the loop cannot be farmed and why doing your share costs you exactly nothing. The only credits that appear from nowhere are the ones we hand you at signup.
- +10Confirmed installyour closed-track opt-in, verified
- +30Confirmed reviewon-rubric, arbitrated, private
The same number, because it is the same number. Credits move between developers; nothing here mints them. A full cycle earns you 560 and costs you 560, so doing your share breaks exactly even — and no amount of testing can inflate the supply, because every credit anyone earns came out of somebody’s balance.
- 145Buffer seatOne more tester above the target you set
- 260Rescue seatA verified replacement, found within hours
- 400Priority placementTop of the feed until you are full
- 300Expert seatA long-form report from a senior tester
- 200Second appRun two apps through testing 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.
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.
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 testers by testing.
- List an app and take testers straight off the feed
- No queue and no cohort to wait for
- 600 credits to start — a full cycle, 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 full cycle 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 Track
Top of the feed until you are full.
- Priority placement in the feed while you are collecting
- 18 testers — six spare, not three
- Free replacement if anyone abandons a seat
- Everything in Free
Pro
For the launch you cannot afford to redo.
- 20 testers, all reliability 85+
- Two expert testers who write long-form reports
- Unlimited replacements
- Reviewed Evidence Pack + application draft
- Priority arbitration and support
Rescue
Someone took a seat and vanished. Fix it in hours.
- One verified replacement tester
- Found 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 listing fails to reach 12 verified testers, a paid plan is refunded in full.
TesterPool is new. The feed is the one filling now.
Most sites in this category would put three glowing testimonials here. We do not have any yet, and inventing them would contradict the only thing that makes this worth choosing.
What you get
Your app in front of every developer here: 14 of them installing it, holding your track for 14 days, and each sending one structured review. Nothing is reserved for later members.
What we get
The exchange run end to end by people who will tell us what broke. Founding members set the standard the reviews are held to, and we would rather hear it from fifteen developers than from a launch.
What is not here yet
No apps have shipped yet, because none has finished collecting. The launch feed is empty and stays empty until one clears. Everything on this page describes how it works, not how well it has worked.
If you need 12 testers and would rather not buy them from a stranger, list your app. It goes into the feed the moment you save it, and there is nothing to wait for after that.
List your appThe ones that decide it
I came here to get reviews for my app. Is that what this is?
Partly, and the difference matters more than it sounds. You get 14 written reviews of your app from developers who ship Android apps themselves — what broke, on which device, what they would change. Detailed, private, and yours to act on.
What you do not get is Play Store reviews or star ratings, and no service can honestly sell you those. A review traded for anything — money, credits, a review back — is an incentivised review under Google’s Ratings, Reviews and Installs policy. Apps get removed for it and developer accounts get terminated for it, and the sites that offer it are selling you that risk without pricing it in.
The reason people want store reviews is almost always one of two things: they cannot publish yet, or the app is not good enough to earn reviews on its own. TesterPool is built for both. The first is the 12-tester requirement, which the feed clears. The second is what 14 critical reviews are for.
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, ask for more than twelve. You set the number of testers you want and you can raise it any time, so aiming at 15 for a 12-tester requirement means three people can vanish and you still clear the bar. Competitors sell that buffer as an upsell; here it is just a number you choose.
Second, the seat comes back. A tester who takes your app on and goes quiet is flagged on your dashboard, and their seat returns to the feed for someone else — no waiting on a match, because there is no cohort to rebuild. On Fast Track and Pro a replacement is found for you.
Third, walking away is expensive for the person who does it: it costs 120 credits and a serious hit to their Reliability Score, which throttles how much work they can hold below 40. Nobody ghosts 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 about ten minutes: install it, use it properly, write what you found. Testing a full cycle of apps earns 560 credits — exactly what a full cycle of testers costs you, so doing your share breaks even. If you would rather not, Fast Track at $19 buys the testers without reciprocating.
How long until reviewing starts?
There is nothing to wait for — your listing is live the moment you save it, and testers take it whenever they browse. How fast they arrive depends on how deep the feed is that week and how clear your brief is. Fast Track puts you at the top of it. We will be blunt: while the network is still small, a listing can sit for a day or two before anyone picks it up.
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 reviews, 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 rounds are in limited beta — the same 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, enough to pay for more testers than the 12 Google asks for, and an Evidence Pack that fills itself in as they arrive.
No card required. No store reviews. No policy risk.