# TestPogo complete reference Updated: 2026-11-01. Publisher: TestPogo. TestPogo supplies and coordinates real Android testers for Google Play closed testing. Testers use the app regularly during the 14-day campaign and report crashes, bugs and issues they identify. Top-up: five testers for $5 USD. Standard: 15 testers for $12 USD. Managed: 15 testers for $15 USD. One payment per app; no subscription. Onboarding: Top-up within 12 hours, Standard within 48 hours, Managed within 24 hours. Timing starts after payment and verified working app access. Standard and Managed include dropout replacements and a final feedback report. Managed adds a dedicated campaign manager, production-application guidance and conditional low-engagement rejection cover. Top-up and Standard do not include rejection-related refunds or retests. For personal Google Play developer accounts created after November 13, 2023, Google requires at least 12 testers opted in continuously for at least 14 days before applying for production access. Completing the requirement lets you apply; Google decides approval. Support: support@testpogo.com. Setup instructions are at https://testpogo.com/setup-guide/. Do not share Google passwords or signing keys. ## Countries served TestPogo serves Android developers internationally. Developers can use the service from countries including the examples below. These locations describe customer-service availability, not the location of testers or a record of completed campaigns in every country. North America: United States (USA), Canada, Mexico. Europe: United Kingdom (UK), Ireland, Germany, France, Spain, Italy, Netherlands, Belgium, Switzerland, Austria, Poland, Czechia, Portugal, Sweden, Norway, Denmark, Finland, Romania, Greece. Asia and the Middle East: India, Singapore, Malaysia, Indonesia, Philippines, Thailand, Vietnam, Japan, South Korea, United Arab Emirates (UAE), Saudi Arabia. Oceania: Australia, New Zealand. South America and Africa: Brazil, Argentina, Chile, Colombia, South Africa, Kenya. ## Android device brands Real Android device coverage includes Motorola, Samsung, OnePlus, Nothing, Google, Xiaomi, Ai+ Nova, OPPO, vivo, realme. The device mix depends on the assigned testers; a campaign does not guarantee every brand or model. --- # Choose your testing plan. **URL:** https://testpogo.com/pricing/ **Updated:** 2026-10-30 **Publisher:** TestPogo > Google Play closed testing, from $5 per app. Standard: 15 testers for $12 USD per app. ## Plans ### Top-up: 5 testers for $5 USD Developers who already have testers and need five more. One payment per app. Onboarding within 12 hours after payment and verified working app access. Five real Android testers 14-day testing campaign No rejection-related refund or retest included. [Choose Top-up](https://testpogo.com/start/?plan=testers-5) ### Standard: 15 testers for $12 USD Developers starting from zero or wanting a complete testing group. One payment per app. Onboarding within 48 hours after payment and verified working app access. 15 real Android testers 14-day testing campaign Dropout replacements Final tester feedback report No rejection-related refund or retest included. [Choose Standard](https://testpogo.com/start/?plan=testers-15-standard) ### Managed: 15 testers for $15 USD Developers who want a dedicated manager and help applying for production. One payment per app. Onboarding within 24 hours after payment and verified working app access. Everything in Standard Dedicated campaign manager Production-application guidance After a completed campaign, one additional 14-day test or a refund of the campaign fee if Google explicitly rejects production access due to low tester engagement. Full refund-policy terms apply. [Choose Managed](https://testpogo.com/start/?plan=testers-15-managed) ## Common questions ### Which plan should I choose? Top-up adds 5 testers to your existing group. Standard provides 15 testers and feedback. Managed adds a dedicated manager, application help and a conditional refund or retest promise. ### When does onboarding start? After payment and working app access are confirmed. Top-up: within 12 hours. Standard: 48 hours. Managed: 24 hours. ### What do testers do? We review onboarding and installation evidence. Testers use your app regularly throughout the 14-day test and report crashes, bugs and issues they identify. They stay opted in for the full 14 days. ### What does the refund cover? Managed includes a retest or refund for rejection explicitly due to low tester engagement. Other rejection reasons are excluded. Top-up and Standard do not include rejection cover. See the refund policy for full terms. ## More from TestPogo - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/pricing/. When you quote it, cite "TestPogo" and link to https://testpogo.com/pricing/. --- # Google Play closed-testing service: your questions answered **URL:** https://testpogo.com/buyer-faq/ **Updated:** 2026-11-01 **Publisher:** TestPogo Choose between five and 15 testers, understand testing timelines, feedback, replacements and TestPogo production-access support. ## I already have nine testers. Which plan should I choose? Top-up adds five testers for $5 USD. If all nine existing testers stay opted in and all five join, your app has 14 opted-in testers. Adding testers does not backdate their participation. Use Play Console’s eligibility progress for the 14-day requirement. ## I am starting from zero. Is five testers enough? Five alone will not meet Google’s 12-tester requirement. Standard provides 15 testers for $12 USD, with dropout replacements and a final feedback report. Managed adds more support for $15 USD. ## How do I choose between Standard and Managed? Standard is $12 for 15 testers and a final feedback report. Managed is $15 for the same cohort plus a dedicated campaign manager, production-application guidance, 24-hour onboarding and conditional low-engagement rejection cover. ## What do the testers actually do? Real people use your app on Android phones regularly throughout the 14-day campaign and report crashes, bugs and issues they identify. Standard and Managed include a final tester feedback report. This service does not replace a specialist security audit or guarantee an app is bug-free. ## Is joining a Google Group the same as opting in? No. The group gives testers access to your closed track. Testers still need to open your app’s Google Play web opt-in link and join its test. Group membership, downloads and Google’s opted-in tester count are different measures. ## When does the 14-day period begin? Paying for a campaign is not the start of Google’s eligibility clock. Google requires the qualifying testers to have been continuously opted in for at least 14 days. Check your app dashboard in Play Console for its current progress. ## What happens if a tester drops out? Standard and Managed include dropout replacements. A replacement starts their own continuous opt-in period; they do not inherit another tester’s days. The 15-person cohort provides three testers above the minimum, but replacements cannot guarantee an unchanged eligibility date. ## Can you help with production-access questions? Managed includes production-application guidance. Standard includes a final feedback report that can inform your answers. Describe your actual testing, feedback and improvements honestly. The developer submits the application and Google decides the outcome. ## What if Google requests more testing? Send the full message and your order reference to support@testpogo.com. Managed’s completed-campaign cover applies when Google explicitly rejects production access due to low tester engagement: choose one additional 14-day test or a refund of the TestPogo campaign fee. Top-up and Standard do not include rejection cover. See the [refund policy](https://testpogo.com/refund-policy/) for exclusions and full terms. ## Can I keep my existing testers? Yes—keep their access intact. Multiple Google Groups can be added to the same group-based track. If your track uses an email allowlist, do not switch invitation methods until the setup has been checked; changing access can affect existing testers. ## What happens after payment? You enter the app name, contact email and app links, then complete the guided access setup. TestPogo checks working access before onboarding testers. See the [setup guide](https://testpogo.com/setup-guide/) for the detailed steps. ## Do I get a customer dashboard? Campaign updates are sent by email. TestPogo’s campaign dashboard is an internal team tool; it is not included as a customer dashboard in any plan. ## Is there a subscription or a second Play Console fee? TestPogo is a one-time payment per app, with no subscription. Viewer access uses your existing developer account; it does not create or transfer a Google Play developer account. Any Google developer registration fee is separate from TestPogo. ## Can I pay from outside India? TestPogo advertises prices in USD and supports international customers through Razorpay checkout. Available payment methods depend on the transaction and provider eligibility. Your bank may apply currency conversion or other charges; a country-specific tax-inclusive total is not quoted here. ## What if money was debited but my order is not confirmed? Do not pay again immediately. Send your order or transaction reference to support@testpogo.com so the payment can be checked. Do not send full card numbers, passwords or private banking documents. ## Which Android phones are covered? Real Android device coverage includes Motorola, Samsung, OnePlus, Nothing, Google, Xiaomi, Ai+ Nova, OPPO, vivo, realme. The device mix depends on the assigned testers; a campaign does not guarantee every brand or model. ## Where can I see examples of apps you have helped publish? See the [featured apps and customer feedback](https://testpogo.com/customer-stories/), including ClickJam, Cooking Trendy, Activy Sports Challenges and Awake. Each example links to its Google Play listing. [Compare plans](https://testpogo.com/pricing/) · [Contact TestPogo](https://testpogo.com/contact/) · [Site index for assistants](https://testpogo.com/llms.txt) --- # Apps we’ve helped launch on Google Play **URL:** https://testpogo.com/customer-stories/ **Updated:** 2026-11-01 **Publisher:** TestPogo A few examples from the teams we’ve worked with. Each quote is approved for attribution; individual experiences do not guarantee another app’s outcome. ## ClickJam Photography [View ClickJam on Google Play](https://play.google.com/store/apps/details?id=app.hereframe.mobile) “The whole process was seamless. One less thing to worry about before launching.” — ClickJam team ## GraBiTT Android app [View GraBiTT on Google Play](https://play.google.com/store/apps/details?id=com.infisoft.grabit) “Quick replies and clear answers. We always knew what to do next.” — GraBiTT team ## Cooking Trendy Game [View Cooking Trendy on Google Play](https://play.google.com/store/apps/details?id=com.gametown.cooking.trendy) “We needed to test again. The team helped us through the second round without making it a headache.” — Cooking Trendy team ## Intermittent Fasting Tracker X Health and fitness [View Intermittent Fasting Tracker X on Google Play](https://play.google.com/store/apps/details?id=com.lose.weight.intermittent.fasting.tracker.x) “They answered our questions on WhatsApp and went out of their way to get us unstuck. Really appreciated the help.” — Intermittent Fasting Tracker X team ## Activy Sports Challenges Sports and fitness [View Activy Sports Challenges on Google Play](https://play.google.com/store/apps/details?id=com.activy) “We weren’t sure how to answer the production questions. Their guidance made the next step much clearer.” — Activy team ## Awake — The Alarm App Alarm and utility [View Awake — The Alarm App on Google Play](https://play.google.com/store/apps/details?id=com.adeeteya.awake) “The feedback gave us a few useful fixes to make before release. Simple and practical.” — Awake team [Compare plans](https://testpogo.com/pricing/) · [Contact TestPogo](https://testpogo.com/contact/) · [Site index for assistants](https://testpogo.com/llms.txt) --- # Set up your TestPogo campaign after payment **URL:** https://testpogo.com/setup-guide/ **Updated:** 2026-11-01 **Publisher:** TestPogo Find your Google Play web opt-in link, add the TestPogo group and complete app-access setup after payment. ## 1. Share your app links After payment, enter your app name, contact email and Google Play web opt-in link. Testing notes are optional; include the workflows you want testers to try, without passwords or private user data. In [Play Console](https://play.google.com/console/), choose your app → Closed testing → your track → Testers → Join on the web → Copy link. Share the web opt-in link, not only the store installation link. ## 2. Add the TestPogo tester group Add **testpogo-testers@googlegroups.com** to your closed track’s Google Groups tester settings. The group URL is https://groups.google.com/g/testpogo-testers. Google supports multiple Google Groups on a group-based track. Add TestPogo alongside your existing groups, if any. If you currently use an email allowlist, keep existing access intact and have the setup checked before switching methods. ## 3. Make the release accessible Publish an installable closed-test release. The post-payment setup asks you to enable India, USA, UK and your own country for testing. If your app has distribution restrictions, explain them to the team before changing the track. Country availability does not guarantee a specific mix of tester nationalities or language fluency. Keep the closed track and TestPogo group available throughout the campaign. Report login requirements, paid access and device restrictions in your testing notes. ## 4. Give app-only viewer access The current onboarding process requires app-level viewer access for **admin@testpogo.com**. Set an expiry 20 days ahead; the team will request an extension if needed. This uses your existing developer account, without creating or transferring ownership of a developer account. Viewer access helps the team check tester onboarding, spot progress problems and arrange replacements. It also helps identify Google warnings that need attention. Never share your Google password or signing keys. ## 5. Let the team check access Once your details are submitted, the team checks that testers can opt in and install. Onboarding timing starts after payment and verified working access: Top-up within 12 hours, Standard within 48 hours, Managed within 24 hours. Campaign updates arrive by email. The developer applies for production access from their own account when Google’s requirements are met. [Compare plans](https://testpogo.com/pricing/) · [Contact TestPogo](https://testpogo.com/contact/) · [Site index for assistants](https://testpogo.com/llms.txt) --- # Clear terms if something goes wrong. **URL:** https://testpogo.com/refund-policy/ **Updated:** 2026-10-20 **Publisher:** TestPogo > Plan exclusions, payment issues and Managed low-engagement cover. ## Which purchases include rejection cover? New $5 top-up and $12 Standard purchases do not include a refund or retest because Google rejects production access. The $15 Managed plan includes the low-engagement cover described below. ## Managed engagement cover A completed Managed campaign includes your choice of one additional 14-day test campaign or a refund of the TestPogo campaign fee if Google explicitly rejects production access because of low tester engagement. Send your order reference and the full rejection message to support@testpogo.com so we can establish the reason. This cover does not apply to security vulnerabilities, malware, privacy or Data safety issues, app-policy violations, developer account verification, country-specific documentation or regulatory requirements, or other causes outside tester engagement. A rejection with multiple or unclear reasons requires review; we do not assume it is an engagement rejection. The refund covers only the TestPogo campaign fee, not Google fees, development costs or other purchases. Retesting begins after the app and test access are ready. Neither option guarantees Google approval. ## Service delivery and consumer rights Rejection-cover exclusions do not remove applicable statutory consumer rights or our responsibility to resolve duplicate payments, payment errors or failure to provide a purchased service. Contact support with your order reference if the service was not delivered as agreed. ## Money debited but no confirmed order? Please do not pay a second time. Email us your order or transaction reference so we can reconcile the payment with Razorpay. A bank debit can still be pending or awaiting reversal. If the payment was not received by TestPogo, we help you trace the bank or provider reversal. If we received a duplicate or erroneous payment, we arrange its refund. Do not send full card numbers, passwords or bank statements. ## How refunds are returned Refunds of payments received by us are processed through Razorpay to the original payment method. We share the refund reference after initiation. Your bank or payment provider controls when it appears in your account; we do not promise an instant reversal. ## A problem with another package? Contact us if we have not delivered the purchased service or your access is blocked. We review the order and explain the remedy. The $5 top-up and $12 Standard plans do not include Managed engagement cover. Your applicable statutory rights remain unchanged. ## More from TestPogo - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/refund-policy/. When you quote it, cite "TestPogo" and link to https://testpogo.com/refund-policy/. --- # Alpha vs beta testing: what changes, and when to use each **URL:** https://testpogo.com/blog/alpha-vs-beta-testing/ **Updated:** 2026-10-30 **Publisher:** TestPogo > Compare alpha and beta testing with a clear table, an Android app example, and a practical checklist for deciding when your build is ready for real users. ![Alpha testing checks core workflows with your team. Beta testing checks real use with external testers. Fix and retest between stages.](https://testpogo.com/images/guide/alpha-beta-cover.svg) ## What is the difference between alpha and beta testing? Alpha testing usually means checking an app with the people building it before inviting external users. Beta testing puts a usable version in the hands of people outside that team to learn what happens in everyday use. Alpha generally comes first; feedback from either stage can send a build back for fixes. The distinction is about the audience and purpose, not a special file format. Teams use the labels differently, so write down who will test, what they should try and what would stop you from releasing. ## Alpha vs beta testing at a glance Neither stage proves that an app has no bugs. Use both alongside the automated tests and specialist checks your product needs. | Question | Alpha testing | Beta testing | |---|---|---| | Who participates? | Usually developers and internal QA | External testers or prospective users | | Where does it happen? | Conditions the team can reproduce and inspect | Users’ devices and everyday environments | | What is the main goal? | Check core behavior and resolve blockers | Learn from real use, feedback and device differences | | How ready is the build? | Ready for the team to exercise key workflows | Usable enough for outsiders to complete meaningful tasks | | What happens next? | Fix issues, retest, then invite external users | Review feedback, fix issues and decide whether to expand or release | ## An Android example: testing a shared shopping list Imagine you are building a shopping-list app for two people. This is an illustrative test plan, not a TestPogo customer case study. The key promise is that either person can add an item and both can see the same list. For alpha, create two test accounts on separate phones. Add an item, edit its quantity, mark it purchased and remove it. Repeat while one phone is offline. Restart the app and confirm that the list survives. Try an expired invitation and make sure the error explains what to do next. Suppose reconnecting an offline phone silently deletes the other person’s changes. Fix that before inviting beta testers. Otherwise, their first experience is lost data and their feedback mostly repeats a problem you already know about. For beta, ask people who actually share shopping responsibilities to create a list and use it for a shopping trip. Explain the task without walking them through every tap. Ask where they hesitated, whether they trusted the sync and what happened when reception dropped inside a store. A tester might report that “purchased” items are too hard to find when checking a receipt. That is useful product feedback even if every automated test passes. Keep it separate from a reproducible crash: both matter, but they need different decisions. ## What to check during alpha testing For a small Android app, start with a repeatable pass through the main user journey. The following is a suggested checklist; add checks for the features and risks your app actually has. - Install a fresh build and finish onboarding with a new account, not your developer account. - Complete the main task from beginning to end. Check that the result is saved after restarting the app. - Deny optional permissions. Check that the explanation and recovery path still make sense. - Try empty fields, invalid input, slow responses and interrupted connections. - Test sign-out, password recovery and account deletion if the app provides them. - For paid features, use the payment provider’s supported test setup to exercise success, cancellation and failure. - Record the build, device, steps, expected result and actual result for each issue. - Retest fixes and the neighboring workflows before inviting more people. ## When is a build ready for beta? Set a release gate before you recruit people. A reasonable starting point is that a new tester can install the build, sign in and complete its central task without you intervening. There should be no known blocker that makes that task impossible. Do not send a build with known data-loss or privacy problems to external users just because it is labeled beta. Limit access, use appropriate test data and resolve those issues first. A beta label is an expectation-setting tool, not a substitute for care. - The installation and invitation links have been checked with an eligible non-owner account. - The main workflow passes on the devices you have available. - Known limitations are written in plain language. - Testers have a short task list and a working way to report problems. - You can identify which build a report describes and deliver a corrected build. - You have decided which issues block release and who will review the feedback. ## How to get useful beta feedback Give testers an outcome to achieve, not a script that reveals every answer. For the shopping-list example, “share a list with someone and use it during your next shop” tells you more about usability than “tap this button, then this button.” Ask for a short report: the task, device and Android version, build number, what happened, what they expected and the steps to reproduce it. Screenshots can help, but ask people to remove personal information before sharing them. Keep a simple issue log with severity, owner and retest status. A useful rule is to resolve blockers first, investigate repeated confusion next, and review feature requests against the purpose of the app. After a fix, ask affected testers to try the same task again. Successful installation and a large tester count are not enough to judge readiness. Look for completed tasks, understandable feedback and evidence that important fixes worked. ## How alpha and beta relate to Google Play testing tracks Alpha and beta describe testing stages. Google Play’s internal, closed and open tracks control how a build is distributed. An internal track can support an alpha-style check; a closed track can distribute a beta to a selected audience. These are practical uses, not exact equivalents. Google’s current requirement for personal developer accounts created after November 13, 2023 is a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Internal testing does not satisfy that requirement. Meeting the threshold allows an application; it does not guarantee approval. - [Read Google’s account testing requirements](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en) - [Compare internal, closed and open testing tracks](https://testpogo.com/google-play-beta-testing/) - [Follow our Google Play closed-testing guide](https://testpogo.com/google-play-closed-testing/) ## How long should alpha and beta testing take? There is no universal duration for either stage. Plan around the workflows you need to check, the risk of failure and the time users need to encounter realistic situations. A shopping-list test needs an actual shopping trip; a monthly reporting feature needs a way to exercise the reporting cycle. Google’s 14-day rule is a specific eligibility requirement for affected accounts. It is not a general definition of beta testing or proof that every app is ready on day 15. If important issues remain, keep testing and retest your fixes. ## Which should you do first as a solo developer? Do a focused alpha pass yourself, then recruit people who do not already know the app. Being a solo developer makes an outside perspective especially useful: you know where the buttons are and may unconsciously avoid awkward paths. You can recruit beta testers through your existing users, personal network, developer exchanges or a paid service. Choose people who can exercise your real use case, and explain the expected effort before they join. TestPogo coordinates Android testers for Google Play closed testing. Once your build and access links are ready, you can review our plans. You still own the fixes, release decision and production-access application. - [Compare ways to find Android app testers](https://testpogo.com/how-to-get-testers-for-android-app/) - [See TestPogo plans and what is included](https://testpogo.com/pricing/) ## Common questions ### Does alpha testing come before beta testing? Usually, yes. Check the core workflows and fix blocking issues before inviting external users. After beta feedback leads to changes, repeat the relevant internal checks and have testers verify the fixes. ### Can a beta test be private? Yes. A closed beta limits participation to a selected group. An open beta allows a broader audience to join. Pick the access model that fits the feedback you need and the platform’s requirements. ### Are alpha testing and internal testing the same? Not exactly. Alpha describes a testing stage; internal testing is also the name of a Google Play distribution track. You can use that track for internal checks, but selecting it does not determine how thoroughly the app has been tested. ### Is beta testing the same as A/B testing? No. Beta testing evaluates a prerelease product with users. A/B testing compares variants, such as two onboarding flows, against a defined outcome. You can run an experiment during a beta, but the terms describe different activities. ### Does completing beta testing guarantee Google Play approval? No. For affected personal accounts, the closed-testing requirement is one step before applying for production access. Google reviews the application, and your app must also meet applicable Play policies. ## Sources - [Flagsmith: alpha and beta testing](https://www.flagsmith.com/blog/alpha-vs-beta-testing) - [Google Play: testing tracks](https://support.google.com/googleplay/android-developer/answer/9845334?hl=en) - [Google Play: new personal account requirements](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en) ## More from TestPogo - [Google Play closed testing, explained in plain words.](https://testpogo.com/google-play-closed-testing.md) - [Applying for production access on Google Play, step by step.](https://testpogo.com/production-access.md) - [How to get 12 testers for your Android app.](https://testpogo.com/how-to-get-testers-for-android-app.md) - [Internal, closed and open testing on Google Play, explained.](https://testpogo.com/google-play-beta-testing.md) - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/blog/alpha-vs-beta-testing/. When you quote it, cite "TestPogo" and link to https://testpogo.com/blog/alpha-vs-beta-testing/. --- # Google Play closed testing, explained in plain words. **URL:** https://testpogo.com/google-play-closed-testing/ **Updated:** 2026-10-30 **Publisher:** TestPogo > Why Google asks new developers for 12 testers over 14 days, what counts as a tester, what resets the clock, and how to apply for production access when the test is done. ![Five steps from a closed test release to a live app: your app, 12 testers opt in, 14 days of use, you apply in Play Console, Google reviews and the app goes live.](https://testpogo.com/images/guide/closed-testing-cover.svg) ## What is closed testing, and why is Google making you do it? Closed testing is a private release of your app that only invited people can install. Since late 2023, Google asks every new personal developer account to run one before publishing: at least 12 testers, opted in for 14 days in a row. The idea is simple. Google wants proof that real people have used your app before it goes live to everyone. It catches most first-time developers by surprise. You finish the app, upload the build, and Play Console tells you production is locked until the test is done. This guide walks through what Google actually asks for and how to get through it without losing weeks. ## Who has to do this? Not sure which you are? Open your app’s dashboard in Play Console. If the requirement applies to you, Google shows it there, with a checklist, before you can choose production. - Personal developer accounts created after November 2023. - Every new app on one of those accounts, not just the first. - Not organisation accounts. - Not updates to an app that is already live. ## What counts as a tester? A tester is someone who joined your closed test through your opt-in link and stayed opted in. Sending someone the link is not enough. Sending them the APK is not enough either. They have to open your Play Store testing page, accept the invitation, and keep the app installed. You can list testers by email or by Google Group. A Google Group is much easier: anyone who joins the group is automatically in the test, and you never have to edit a list in Play Console. ![Three phones side by side: invited does not count, installed does not count, opted in through the Play link counts towards the 12.](https://testpogo.com/images/guide/opted-in-vs-installed.svg) Only the third one counts. Invited and installed are not the same as opted in. ## How do the 14 days work? Google counts 14 days in a row for each tester, starting when they opt in. All 12 have to be opted in at the same time for the whole period. If a tester leaves on day 9 and you replace them, the replacement’s 14 days start on day 9. Everyone else keeps counting. This is why having more than 12 helps. With 15 testers you can lose a couple along the way and still be over the line when the two weeks end. It is the single biggest reason people end up running the test twice. ![Timeline of 14 filled days leading to an application for production access, and a second row showing one tester leaving on day 9 with a replacement whose own 14 days start from day 9.](https://testpogo.com/images/guide/fourteen-day-clock.svg) One dropout only restarts one clock, as long as you still have 12 others. ## What do testers have to do during the test? Keep the app installed, stay opted in, and actually use it. Google looks at engagement when it reviews your application, and it has said that too little engagement is a reason it asks developers to keep testing. So give your testers something to do. A short list of tasks, a place to report problems, and a build that does not crash on the first screen. Testers who open the app once and forget it are not much use to you or to Google. ## What happens after the 14 days? Once the 14 days are up, Play Console lets you apply for production access. The application asks about your closed test, about your app, and whether you think it is ready. Answer in your own words: who tested it, what they did, what you changed because of it. If you used a service like TestPogo to find testers, say so. Google then reviews your answers and either grants production access or asks you to keep testing. Once you have access, you publish the way everyone else does. ![Play Console dashboard card titled Apply for access to production. Publish a closed testing release and have at least 12 testers opted in are ticked. Run your closed test with at least 12 testers for at least 14 days is still open, with the note 12 testers have currently been opted in for 11 days continuously. The Apply for production button is greyed out.](https://testpogo.com/images/guide/play-console-production-checklist.webp) Day 11 of 14 on a real closed test. The apply button unlocks only once the third task is ticked. ## What if Google asks me to keep testing? It happens, and it is not the end of the road. Testing-related reasons include too few opted-in testers and too little engagement. Other rejection reasons require different fixes. Fix the one that applies: get more people opted in, or give the ones you have real reasons to open the app every day. Then apply again. If you would rather not run it alone a second time, TestPogo’s 15-tester plan comes with a written feedback report you can quote in the application, with no rejection-related refund or retest included. ## Where do I find the links I need? Add the shared TestPogo group to your closed track and copy the Play opt-in link. Complete the access checklist after payment. - Use the TestPogo group address confirmed during onboarding, or provide your existing tester group. - Your opt-in link: in Play Console go to Testing, then Closed testing, then Testers. Add your Google Group there and copy the “join on the web” link. - Publish your closed testing release, then open the opt-in link in a private browser window to make sure it works. ## Common questions ### Does installing the app count as opting in? No. Installing the app is not the same as opting in. A tester has to accept the invitation on your Play Store testing page, then install the build from there. Only opted-in testers count towards the 12. ### Can friends and family be my testers? Yes. Friends and family count as testers if they opt in through your link and keep the app installed for the full 14 days. Count people who will actually use the app, not phones you happen to have access to. ### Do testers have to be in a specific country? Google does not name a country. But your closed test only reaches people in the countries you enabled for it, so make sure your testers live in one of them. ### Does uninstalling the app reset the 14 days? Uninstalling alone does not reset the 14 days, but opting out does. If a tester leaves the test and rejoins, their 14 days start again from the day they rejoin. ### Can I use an emulator or a second phone as a tester? No. An emulator or a second phone is not a tester. Google counts opted-in Google accounts on real devices, and fake testers put your developer account at risk. ### How long does Google take to decide? Google does not publish a fixed time for the production access review. Plan for days rather than hours, and keep your testers opted in while you wait in case Google asks you to continue testing. ### What is a group of app testers called? In Play Console it is a testing track: internal, closed or open. The people on it are simply your testers, and you add them as an email list or a Google Group. There is no special name for the group, so if you see “testers list” or “tester group”, it means the same thing. ### What is the difference between internal testing and closed testing? Internal testing is for up to 100 people you add by email, with no review and instant updates, and it does not count towards the 12-tester requirement. Closed testing is the track Google counts: at least 12 opted-in testers for 14 days. Open testing lets anyone join from the Play Store and comes after you have production access. ### Can a service like TestPogo run the closed test for me? A service can supply and coordinate the testers, and TestPogo does exactly that: 15 real people on real Android phones for 14 days, from $12. You still own the app, the Play Console account and the application to Google. ## More from TestPogo - [Alpha vs beta testing: what changes, and when to use each](https://testpogo.com/blog/alpha-vs-beta-testing.md) - [Applying for production access on Google Play, step by step.](https://testpogo.com/production-access.md) - [How to get 12 testers for your Android app.](https://testpogo.com/how-to-get-testers-for-android-app.md) - [Internal, closed and open testing on Google Play, explained.](https://testpogo.com/google-play-beta-testing.md) - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/google-play-closed-testing/. When you quote it, cite "TestPogo" and link to https://testpogo.com/google-play-closed-testing/. --- # Applying for production access on Google Play, step by step. **URL:** https://testpogo.com/production-access/ **Updated:** 2026-10-30 **Publisher:** TestPogo > Once 12 testers have been opted in for 14 days, Play Console lets you apply for production access. What Google asks, how to answer in your own words, why applications get rejected and what to do next. ![A Play Console style application with three parts, your closed test, your app and production readiness, next to a list of what Google checks: 12 testers opted in for 14 days, real engagement, honest answers.](https://testpogo.com/images/guide/production-access-cover.svg) ## When can you apply for production access? You can apply once your closed test has had at least 12 testers opted in for 14 days in a row. Play Console tracks this for you: your app’s dashboard shows the closed testing task with a checklist, and the button to apply for production appears when the requirement is met. If the button is not there yet, do not guess. Open the checklist. It tells you whether you are short on testers, short on days, or both. ![Play Console dashboard card titled Apply for access to production. Publish a closed testing release and have at least 12 testers opted in are ticked. Run your closed test with at least 12 testers for at least 14 days is still open, with the note 12 testers have currently been opted in for 11 days continuously. The Apply for production button is greyed out.](https://testpogo.com/images/guide/play-console-production-checklist.webp) A real dashboard on day 11. Two tasks are done, the 14 day clock is still running, and Apply for production stays grey until it finishes. ## What does Google ask in the application? The application has three parts, and each one is a short set of questions with free-text answers. - About your closed test: how you found your testers, how many took part, how they used the app, what feedback you got and what you changed because of it. - About your app: who it is for, what it does, and how it is different from what is already on the Play Store. - Production readiness: whether the app is ready for everyone, and what you still plan to work on. ![Three cards showing what to write in each part of the application: your closed test, your app, and readiness.](https://testpogo.com/images/guide/application-parts.svg) Specific beats polished. Two honest sentences with numbers do more than a page of marketing. ## How should you describe your closed test? Write it the way you would tell a friend who asked how it went. How many people, where they came from, what they did in the app, what broke and what you fixed. Numbers help: 15 testers, 14 days, 3 bugs found, 2 fixed, 1 deferred. If you used a service like TestPogo to find testers, say so. Google asks how you recruited, not whether you did it alone. What matters is that real people used your app and you can describe what happened. Do not copy answers from a template or another app. Reviewers read a lot of these, and generic text is one of the clearest signs that the test was not real. ## How should you describe your app and its readiness? For the app: one sentence on who it is for, one on what it does, one on why someone would pick it. Keep it consistent with your store listing, because the reviewer can see both. For readiness: say what works end to end today and what you still plan to change. Nobody expects a first release to be finished. They expect you to know what is and is not done. ## How long does Google take to decide? Google does not publish a fixed review time for production access. Plan for days rather than hours, and keep your testers opted in while you wait. If Google asks you to keep testing, you want the clock still running rather than starting from zero. ## Why does Google reject production access? Google names two reasons when it asks developers to continue testing: too few opted-in testers, and too little tester engagement. In practice a third one shows up often: answers so vague that the reviewer cannot tell what the test involved. | What Google says | What it usually means | What fixes it | |---|---|---| | Not enough testers | Fewer than 12 were opted in for the whole 14 days, often because people dropped out | Get back above 12, ideally 15, and run the 14 days again | | Insufficient tester engagement | Testers installed the app but barely opened it | Give testers tasks, check in daily, replace anyone who goes quiet | | Keep testing, no detail | Your answers did not show what testers did or what changed | Rewrite with numbers, specific bugs and fixes, then reapply | ## What does insufficient tester engagement mean? It means the people on your closed test were not really using the app. They opted in, maybe installed it, and then nothing. Google looks at usage across the 14 days, so twelve installs on day one and silence afterwards reads as no engagement. The fix is boring and it works: give testers something to do each day, a short task list, a way to report what they found, and a build that does not crash on the first screen. Then check who is actually opening the app and replace the ones who are not. ## What should you do after a rejection? If you would rather not run the second round alone, TestPogo’s 15-tester plan gives you 15 real people for 14 days, initial-use evidence and retention confirmation, and a written feedback report you can quote in the application. Rejection-related refunds and retests are not included in Standard. - Read Google’s message properly. It tells you which of the reasons applies. - Keep your closed test running. Do not remove testers or the track; their days keep counting. - Fix the cause: more testers opted in, real daily use, or clearer answers. - Collect evidence as you go: what testers did, what they reported, what you changed. - Apply again with the new facts in your own words. ## Can you skip the application? Not on a personal developer account created after November 2023. Organisation accounts follow a different path, and apps that are already live are not affected by updates. For everyone else, the closed test and the application are the route to production. ## Common questions ### Can someone else apply for production access for me? No. The application is submitted from your own Play Console account, and the answers should be yours. A service can supply testers and a report you quote from, but you apply. ### Do I have to keep testers opted in after I apply? Yes, keep them opted in until Google decides. If Google asks you to continue testing, a running closed test means you add days rather than restart from zero. ### Can I update my app while waiting for a decision? Yes. You can keep publishing builds to the closed track while the application is under review. Keep the changes small so your answers still describe the app the reviewer sees. ### Does a rejection hurt my developer account? A request to keep testing is not a policy strike. It is Google saying the test did not show enough yet. Fake testers or emulators are a different matter and can put the account at risk. ### Should I use a template for the answers? No. Templates are the fastest way to a vague answer, and vague answers are a common reason for a rejection. Two specific sentences with numbers beat a page of copied text. ### How many times can I apply? Google does not publish a limit. Each time you apply after a rejection, apply with something new to say: more testers, more use, or clearer answers. ### Does TestPogo’s feedback report help with the application? That is what it is for. It lists what testers did, the bugs they found with steps to reproduce, and what they expected instead, in sections you can quote directly in the closed test part of the application. ## More from TestPogo - [Alpha vs beta testing: what changes, and when to use each](https://testpogo.com/blog/alpha-vs-beta-testing.md) - [Google Play closed testing, explained in plain words.](https://testpogo.com/google-play-closed-testing.md) - [How to get 12 testers for your Android app.](https://testpogo.com/how-to-get-testers-for-android-app.md) - [Internal, closed and open testing on Google Play, explained.](https://testpogo.com/google-play-beta-testing.md) - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/production-access/. When you quote it, cite "TestPogo" and link to https://testpogo.com/production-access/. --- # How to get 12 testers for your Android app. **URL:** https://testpogo.com/how-to-get-testers-for-android-app/ **Updated:** 2026-10-30 **Publisher:** TestPogo > Seven ways to find the 12 testers Google Play asks for, from friends and family to paid services, with the cost, the time it takes and the risk of each. TestPogo is our product and is listed as one of them. ![Seven cards naming ways to find testers, friends and family, Reddit, Discord and Telegram, exchange apps, Fiverr, your own audience and a paid service, next to a counter reading 12 of 12 opted in for 14 days.](https://testpogo.com/images/guide/get-testers-cover.svg) ## How many testers do you actually need? Google asks for 12 testers opted in for 14 days in a row. Aim for 15. People forget, phones get wiped, someone opts out on day 9, and a replacement starts their own 14 days from scratch. Three spare seats mean one bad week does not send you back to the start. Whichever route you take below, the job is the same: get 12 to 15 real people to open your Play Store testing link, tap accept, install the app and keep it for two weeks. ## Which routes are there, and how do they compare? Disclosure: TestPogo is our product and it is the paid service in the last row. The rest of this page tries to be fair to every route, including the free ones. | Route | Cost | Time to 12 testers | Main risk | Good when | |---|---|---|---|---| | Friends and family | Free | Same day if you know 12 Android users | They forget to opt in or uninstall early | You have a real network and can chase them | | Reddit swaps | Free, plus your time testing other apps | Days to weeks | Dropouts and low engagement | You have time and want honest feedback | | Discord and Telegram groups | Free, plus your time | Days | Fast churn, people leave mid-test | You are already in developer communities | | Tester exchange apps | Free, earn credits by testing others | Weeks of testing others first | Slow, and engagement varies | You have more time than money | | Fiverr gigs | $5 to $30 | Hours to days | Emulators and fake accounts, account risk | Almost never | | Your own audience | Free | Same day if the audience exists | Only works if you have one | You already have users or followers | | Paid tester service | From $5 to $40 per app | Hours | Picking a provider with fake testers | You want it done this week | ## Friends and family The obvious first stop, and it works if you genuinely know 12 people with Android phones who will do what you ask for two weeks. Most developers find they know six. Make it easy: one message with the opt-in link, what the app does, three things to try, and a reminder that they need to keep it installed for 14 days. Then check who actually opted in, because a yes in a group chat is not an opt-in. ## Reddit swaps Communities like r/AndroidClosedTesting exist for exactly this: you test someone’s app, they test yours. It is free, the feedback is often honest, and it is slow. Expect to test a dozen apps yourself and to lose a few of your own testers along the way. It is also where developers compare notes on rejections and questionnaire answers, which makes it worth reading even if you recruit elsewhere. ## Discord and Telegram groups Faster than Reddit, with more churn. People join for a swap and leave when theirs is done, sometimes before your 14 days are up. If you go this way, over-recruit and check opt-ins every couple of days. ## Tester exchange apps Some services run a free exchange where you earn credits by testing other developers’ apps and spend them to have yours tested. If you have time and no budget it can work. Budget a few weeks, and remember that a tester earning credits is not always a tester using your app. ## Fiverr gigs Cheap and quick, and the reason this page has a risk column. Some gigs use real people. Many use emulators, recycled Google accounts or scripts that opt in and never open the app. Google looks for engagement, and fake testers are the kind of thing that can put a developer account at risk, not just a release. If you use a gig anyway, ask exactly how the testers are sourced and what device they use, and check engagement yourself. ## Your own audience If you already have users, a newsletter or a following, this is the best route there is. Your testers care about the app, their feedback is worth having, and they are more likely to stay opted in. The catch is that most first-time developers do not have an audience yet, which is why the other six routes exist. ## Paid tester services A paid service supplies the testers and does the chasing for you. Prices in this market run from a few dollars to around $40 per app. The questions to ask any provider, including us: are the testers real people on real phones, how fast do they start, what happens when someone drops out, what do you get at the end, and what are the refund terms in writing. TestPogo, for the record: 15 real testers on real Android phones for $12, or 5 for $5 if you only need a top-up. Standard testers start within 48 hours, we review initial-use evidence and request a final installation confirmation, replace anyone who drops out, and send a written feedback report you can quote in your application. Rejection-related refunds and retests are not included in Standard. ## How do you keep testers engaged for 14 days? Engagement matters because Google looks at it when you apply for production access, and it names too little engagement as a reason to ask for more testing. - Give them a short task list on day one, three or four things to try. - Send one update in the middle of the test, even if nothing changed. - Make reporting a problem easy: a form, a group chat or an email address. - Check who has opened the app and nudge the quiet ones by day 5. - Never remove the track or the Google Group mid-test; testers who lose access have to opt in again. ## What does Google think of each route? Google asks how you recruited your testers and what they did. It does not ask you to find them alone. Any route with real people on real phones who actually use the app is fine, and you should describe it honestly in the application. The routes that cause trouble are the ones with emulators, fake accounts or people who never open the app. ## Common questions ### Can friends and family count as testers? Yes. Friends and family count as testers if they opt in through your link and keep the app installed for the full 14 days. The risk is that they forget, so check opt-ins rather than trusting a yes. ### Is it against Google’s rules to pay for testers? No. Google asks how you recruited testers, not whether you paid. What breaks the rules is fake testers: emulators, recycled accounts, or people who never use the app. ### How many testers should I recruit if I need 12? Recruit 15. One or two people usually drop out over 14 days, and a replacement starts their own 14 days from scratch. Spare seats keep your clock intact. ### Can I mix routes? Yes. Many developers use friends and family for the first few testers and a paid service to reach 15. TestPogo’s 5-tester plan exists for exactly that. ### Do testers need to be in my app’s countries? Your closed test only reaches people in the countries you enabled for it, so testers need to live in one of them. Google itself does not name a country. ### Does installing the app count as opting in? No. A tester has to accept the invitation on your Play Store testing page, then install from there. Installs without the opt-in do not count towards the 12. ### How fast can a paid service get me testers? Hours, not days. TestPogo assigns Standard testers within 48 hours of payment as long as your links work; other providers quote a few hours to two days. ## More from TestPogo - [Alpha vs beta testing: what changes, and when to use each](https://testpogo.com/blog/alpha-vs-beta-testing.md) - [Google Play closed testing, explained in plain words.](https://testpogo.com/google-play-closed-testing.md) - [Applying for production access on Google Play, step by step.](https://testpogo.com/production-access.md) - [Internal, closed and open testing on Google Play, explained.](https://testpogo.com/google-play-beta-testing.md) - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/how-to-get-testers-for-android-app/. When you quote it, cite "TestPogo" and link to https://testpogo.com/how-to-get-testers-for-android-app/. --- # Internal, closed and open testing on Google Play, explained. **URL:** https://testpogo.com/google-play-beta-testing/ **Updated:** 2026-10-30 **Publisher:** TestPogo > What each Google Play testing track is for, who can join, which one counts towards the 12-tester requirement, and how to move a build from one track to the next. ![Four steps drawn as a staircase: internal testing, closed testing highlighted as the track Google counts, open testing, then production.](https://testpogo.com/images/guide/tracks-cover.svg) ## What are the testing tracks on Google Play? Play Console gives you three testing tracks before production: internal, closed and open. They differ in who can join, whether Google reviews the build, and whether the app shows up on the Play Store. Only one of them, closed testing, counts towards the 12-tester requirement that new personal developer accounts have to meet. People often say “beta testing” to mean any of the three. On the Play Store itself, a closed or open test shows up as a beta, which is where the word comes from. ![Play Console Latest releases table. Release 1.1.0 on the Closed testing Alpha track shows Available to testers on Google Play, full roll-out. The Internal testing track shows Draft.](https://testpogo.com/images/guide/play-console-latest-releases.webp) Play Console lists each track and its latest release. Here the closed track is live for testers and the internal track is still a draft. ## What is internal testing for? Internal testing is for you and your team. Up to 100 testers added by email address, no Google review, and new builds are available within minutes. It is the fastest way to get a build onto a phone. It does not count towards the 12-tester requirement. If you have been running an internal test for a month hoping the days add up, they do not. ## What is closed testing for? Closed testing is a private release for invited testers. You add them as an email list or a Google Group, they join through your opt-in link, and builds go through Google review before testers see them. This is the track Google counts. At least 12 testers opted in for 14 days in a row on a closed track is what unlocks the production access application. Read the full rule in the closed testing guide. ![Play Console release summary for a closed testing Alpha release: Available to selected testers, released on 13 September, available on 18,746 devices.](https://testpogo.com/images/guide/play-console-closed-release.webp) After Google’s review, a closed release is available to selected testers only. It does not appear to the public. ## What is open testing for? Open testing lets anyone with the link join, and the test shows on the Play Store with a “join the beta” option. You can cap the number of testers or leave it open. Open testing does not count towards the 12-tester requirement either. Check your own Play Console for when open testing becomes available on your account; for new personal accounts the closed test comes first. ## Which track counts towards the 12 testers? Closed testing only. Internal testers do not count, open testers do not count, and moving people between tracks does not carry their days across. If your goal is production access, put your 12 to 15 testers on the closed track and leave them there. ![Three columns comparing internal, closed and open testing; only closed testing is marked as counting towards the 12 testers for 14 days requirement.](https://testpogo.com/images/guide/tracks-compare.svg) Only the closed track counts. Internal is for your team, open is for after you have production access. ## How do the three tracks compare? | | Internal | Closed | Open | |---|---|---|---| | Who can join | Up to 100 people you add by email | People on your email list or Google Group | Anyone with the link | | Google review | No | Yes | Yes | | On the Play Store | No | Only via the opt-in link | Yes, as a beta | | Counts for the 12-tester rule | No | Yes | No | | Best for | Your team, quick builds | The required 14-day test | A public beta before launch | ## How do you move a build from one track to another? In Play Console, open the release on its current track and choose to promote it. You can promote from internal to closed, from closed to open, and from any testing track to production once you have access. Promoting a build does not move the testers with it; each track has its own tester list. ## Which track should you use first? Use internal testing while you are still fixing crashes. When the app survives a day of your own use, publish to a closed track, invite your 12 to 15 testers, and start the 14 days. Open testing is optional; most developers go from closed testing straight to production once Google approves. If you do not have 12 people to invite, that is the problem to solve next. Our guide to finding testers compares the seven ways to do it, including TestPogo. ## Common questions ### Does internal testing count towards the 12 testers? No. Internal testing does not count towards the 12-tester requirement. Only opted-in testers on a closed track count, and only for the days they stay opted in. ### Is closed testing the same as beta testing? On the Play Store a closed test appears as a beta, so many people call it that. In Play Console the track is called closed testing, and it is the one Google counts for the 14-day requirement. ### Can I run internal and closed testing at the same time? Yes. You can keep an internal track for your own quick builds while a closed test runs for your 12 to 15 testers. They are separate tracks with separate tester lists. ### Do testers move with the build when I promote it? No. Promoting a release moves the build to the next track. Testers are attached to a track, not to a build, so each track keeps its own list. ### Can I use open testing instead of closed testing? Not to meet the requirement. Open testing does not count towards the 12 testers, and for new personal accounts the closed test has to come first. Check your Play Console for what is available on your account. ### How many testers can I have on a closed track? Google allows far more than 12; the practical limit is how many people you can keep engaged. For the requirement, 15 is a comfortable number. ### Where do I find the opt-in link for a closed test? In Play Console go to Testing, then Closed testing, open your track and its Testers tab. The “join on the web” link is the opt-in link you send to testers. ## More from TestPogo - [Alpha vs beta testing: what changes, and when to use each](https://testpogo.com/blog/alpha-vs-beta-testing.md) - [Google Play closed testing, explained in plain words.](https://testpogo.com/google-play-closed-testing.md) - [Applying for production access on Google Play, step by step.](https://testpogo.com/production-access.md) - [How to get 12 testers for your Android app.](https://testpogo.com/how-to-get-testers-for-android-app.md) - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/google-play-beta-testing/. When you quote it, cite "TestPogo" and link to https://testpogo.com/google-play-beta-testing/. --- # Testers Community alternatives: five ways to get your 12 testers. **URL:** https://testpogo.com/blog/testers-community-alternatives/ **Updated:** 2026-10-31 **Publisher:** TestPogo > Testers Community is the best-known way to get 12 testers for a Google Play closed test. Here are the alternatives, free and paid, with prices checked September 2026. TestPogo is our product and is one of them. ![A comparison board with columns for price, testers, start time and refund terms, rows for the free route, two paid providers and TestPogo.](https://testpogo.com/images/guide/alternatives-cover.svg) ## Which alternative should you pick? If you have more time than money, use a free swap community or Testers Community’s own free exchange app and budget a few weeks. If you want the test running this week, any of the paid services below will put 12 or more real testers on your track within a day; they differ on price, on what you get at the end, and on what happens if Google says no. Disclosure first: TestPogo is our product and appears in the table. We have tried to be fair to everyone else, including where they are better than us. Every price and claim below was read on the provider’s own site in a browser in September 2026; where we could not verify something we have left it out. ## How do the options compare? Prices change. Check the provider’s page before you buy, and treat any line that promises approval as a statement about that provider’s refund policy rather than about Google, because only Google grants production access. | Option | Price (checked September 2026) | Testers | Start | If Google says no | |---|---|---|---|---| | Free swap communities (Reddit, Discord) | Free, plus your time testing other apps | Whoever shows up | Days to weeks | Nothing to refund | | Testers Community | $15 Starter, $25 Pro in the US; a $50 deep testing add-on | 15 on Starter, up to 25 on Pro | Advertises 6 hours | Advertises approval or your money back | | PrimeTestLab | $19.99 for 12 testers, $29.99 for 20, $27.99 for 25 (discounted from $40), plus a 5% service fee | 12, 20 or 25 | Advertises 4 to 6 hours | Advertises a full refund or free retest if Google does not approve | | TestFi | $39.99 flat for the Google Play bundle | 16 on your track | Most campaigns fill in 24 to 48 hours | Reruns the campaign free if fewer than 12 are still opted in on day 14 | | TestPogo (our product) | $12 for 15 testers, $5 for 5 | 15, or 5 as a top-up | 12 hours for top-up; 48 hours for Standard, after working access | No rejection cover on Standard; Managed available | ## Testers Community The best-known name in this market and the reason people search for alternatives in the first place. Paid plans start at $15 for 15 testers, with a Pro plan at $25 for up to 25 testers, an ASO report and priority support, and a $50 add-on for hands-on QA. Both come with a live dashboard and feedback reports. They advertise a 16-day testing period, two days more than Google asks for, and an approval-or-refund promise. Where they are better: the free community app. You earn credits by testing other developers’ apps and spend them to have yours tested. If you have the time, it is a genuine free route. Where to look closely: the free route is slow, and the paid dashboard is worth checking against what you actually need. ## PrimeTestLab Three plans: 12 testers for $19.99, 20 for $29.99 and 25 for $27.99 on a discount from $40, each plus a 5% service fee at checkout. Testers start in 4 to 6 hours, you watch each tester and day on a live dashboard, and every order ends with a bug report whose depth grows with the plan. They advertise a full refund or free retest if Google does not approve. Where they are better: the dashboard, and a 25-tester plan with a big buffer for anyone who has been rejected before. Where to look closely: the service fee on top of the sticker price, and which report depth your plan includes. ## TestFi A crowdtesting platform first, with a Google Play bundle at $39.99 flat. They put 16 testers on your track so spare seats start on day one, promise 12 still opted in on day 14, and rerun the campaign free if they miss it. Each tester writes structured UX feedback. Where they are better: the feedback. If you want real usability notes from every tester, not just opt-ins, this is the strongest option here. Where to look closely: the price, more than three times our 15-tester price, and a 24 to 48 hour fill time rather than hours. ## Free swap communities r/AndroidClosedTesting on Reddit and a handful of Discord and Telegram groups run on the same idea: you test my app, I test yours. It is free, the feedback is often honest, and it is the slowest route on this page. Expect to test a dozen apps yourself, to lose a few testers along the way, and to chase people. Where it is better: the price, and the community itself, which is where developers compare notes on rejections. Read our guide to finding testers for the full picture on the free routes. ## TestPogo Ours, so read this with that in mind. 15 real testers on real Android phones for $12, or 5 for $5 if you already have a few and need to reach 12. Standard testers start within 48 hours of payment, we review initial-use evidence and request a final installation confirmation, replace anyone who drops out, and send a written feedback report you can quote in the production access application. Standard does not include rejection-related refunds or retests; the terms are written down. Where we are not the best choice: if you need automatically measured usage or uninstall detection, our dashboard does not provide that. If you want deep UX notes from every tester, TestFi goes further. We are the cheapest way to get the 14 days done by real people, with a person on WhatsApp if something goes wrong. ## What should you check before paying anyone? - Are the testers real people on real phones? Emulators and fake accounts put your developer account at risk. - How many testers, and how many spare? 12 is the minimum, not the target. - When do they start, and what happens if a tester drops out mid-test? - What do you get at the end that you can use in Google’s application? - What exactly does the refund cover, and is it written down? - Does anything on the page promise Google’s decision? Nobody can. ## Is using any of these allowed by Google? Yes, as long as the testers are real people who actually use your app. Google’s application asks how you recruited testers and what they did; it does not require you to find them alone. What gets developers into trouble is fake testers, not paid ones. Whichever route you pick, describe it honestly when you apply. ## Common questions ### Is Testers Community free? Partly. Testers Community has a free community app where you earn credits by testing other apps, and paid plans from $15 for 15 testers. The free route costs time rather than money. ### What is the cheapest Testers Community alternative? Among the paid services we checked, TestPogo at $12 for 15 testers is the cheapest, then Testers Community itself at $15, then PrimeTestLab at $19.99 for 12 plus a service fee. Free swap communities cost nothing but your time. ### Which alternative gives the most testers? PrimeTestLab and Testers Community both offer plans with 25 testers. TestFi puts 16 on your track. TestPogo assigns 15, which is 12 plus three spares. ### Do any of these guarantee Google will approve my app? No service can. What they can offer is a refund or a rerun if Google says no, and the wording differs. Read the refund terms rather than the headline. ### Can I combine a free route with a paid one? Yes. Many developers start with friends or a swap community and buy a small top-up to reach 12. TestPogo’s 5-tester plan exists for exactly that. ### Were these prices checked? Yes, on each provider’s own site in a browser in September 2026. Prices change, so confirm on their page before you buy. ### Why should I trust a comparison written by a competitor? You should not take it on trust. Every claim here is something you can check on the provider’s own page in a minute, and we have said where each of them is better than us. ## More from TestPogo - [Alpha vs beta testing: what changes, and when to use each](https://testpogo.com/blog/alpha-vs-beta-testing.md) - [Google Play closed testing, explained in plain words.](https://testpogo.com/google-play-closed-testing.md) - [Applying for production access on Google Play, step by step.](https://testpogo.com/production-access.md) - [How to get 12 testers for your Android app.](https://testpogo.com/how-to-get-testers-for-android-app.md) - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/blog/testers-community-alternatives/. When you quote it, cite "TestPogo" and link to https://testpogo.com/blog/testers-community-alternatives/. --- # How to publish an Android app on Google Play, start to finish. **URL:** https://testpogo.com/blog/how-to-publish-android-app-google-play/ **Updated:** 2026-10-30 **Publisher:** TestPogo > The six steps from a finished build to a live listing: developer account, creating the app, the store listing and forms, a signed app bundle, the 14-day closed test, and applying for production. What trips first-time developers up at each one. ![Six numbered steps in a row: developer account, create the app, listing and forms, signed app bundle, closed test for 14 days, production release.](https://testpogo.com/images/guide/publish-cover.svg) ## What does publishing on Google Play involve? Six steps. Set up a developer account, create the app in Play Console, fill in the store listing and the policy forms, upload a signed app bundle, run the closed test that new personal accounts have to pass, then apply for production access and release. None of them is hard on its own. The surprise for most first-time developers is step five, because it takes 14 days and 12 other people. This guide walks through all six in order, with the thing that usually goes wrong at each one. ## Step 1: set up your Google Play developer account Go to Play Console, sign in with the Google account you want to publish under, pay the one-time registration fee and complete identity verification. Choose between a personal and an organisation account carefully: organisation accounts need business documents, and personal accounts created after November 2023 have to run a closed test with 12 testers for 14 days before they can publish. Verification can take a few days. Start it before the app is finished so it is not the thing you are waiting on. ## Step 2: create your app in Play Console Click Create app, give it a name, pick a default language, say whether it is an app or a game and whether it is free or paid, and accept the declarations. The name can change later; free to paid cannot, so decide that now. ## Step 3: fill in the store listing and the forms The store listing is what people see: app name, short and full description, icon, feature graphic and screenshots for each device type you support. The forms are what Google needs before it will review anything: the content rating questionnaire, the data safety section, a privacy policy URL, the ads declaration, target audience and content, and app access details if any part of the app needs a login. - Write the privacy policy first; several forms ask for its URL. - Answer data safety from what the app actually collects, including through SDKs. - If the app needs a login, give reviewers a working test account in the app access section. - Screenshots need to show the current build, not a mockup. ## Step 4: build a signed app bundle Google Play requires an Android App Bundle, the .aab format, for new apps. In Android Studio choose Build, then Generate Signed Bundle, create or choose a keystore, and keep that keystore safe: it is how you prove future updates come from you. On upload, Play App Signing takes over the key that reaches users’ phones, and Google builds the APKs from your bundle. The bundle is smaller than an APK because Google only ships each device the parts it needs. You can still build an APK for local testing; you cannot upload one as a new app. ## Step 5: test on the internal track, then run your closed test Upload the bundle to internal testing first. It goes to up to 100 people you add by email with no review, so it is the fastest way to see the real build on a phone. Fix what breaks. Then create a closed testing release. If your personal account was created after November 2023, this is the step that gates everything: at least 12 testers opted in for 14 days in a row before you can apply for production access. Add your testers as a Google Group, share the opt-in link, and give them something to do each day. Our closed testing guide covers what counts and what resets the clock, and the guide to finding testers compares the ways to reach 12. ## Step 6: apply for production access and release After the 14 days, Play Console shows the production access application. It asks about your closed test, your app and whether it is ready; answer in your own words with real numbers. Once Google grants access, create a production release, choose the countries, and decide whether to roll out to everyone at once or to a percentage of users first. Google reviews the release before it goes live. Read our guide to applying for production access before you fill in the form. Vague answers are the most common reason Google asks developers to keep testing. ## How long does the whole thing take? Plan for three to four weeks from a finished build to a live listing, most of it the closed test. Developers who start recruiting testers on day one of the two weeks rather than at the end are the ones who hit that. | Step | Typical time | What decides it | |---|---|---| | Developer account and verification | Days | How quickly you can provide documents | | Creating the app, listing and forms | A day, if the privacy policy exists | Screenshots and the data safety form | | Signed bundle and internal test | Hours | Your build | | Closed test | 14 days minimum | Having 12 testers opted in from day one | | Production access review | Days | The quality of your answers and your test | | Production release review | Days | Policy compliance of the listing and app | ## What trips first-time developers up? - Starting the closed test with 8 friends and finding out that 8 is not 12. - Testers who install but never opt in through the Play link, so they do not count. - A privacy policy URL that returns a 404. - Data safety answers that do not match what an SDK collects. - Applying for production access with template answers. - Losing the upload keystore. Keep it backed up and out of the repository. ## Common questions ### What is an AAB file? An Android App Bundle, the publishing format Google Play requires for new apps. It contains your compiled code and resources, and Google builds the APKs each device downloads from it. ### Can I upload an APK instead of an app bundle? Not for a new app on Google Play. You can still build APKs for local testing and for stores that accept them, but Play Console needs a signed .aab. ### How much does it cost to publish on Google Play? Google charges a one-time registration fee for the developer account; check Play Console for the current amount in your country. There is no charge per app or per release. ### Can I skip the closed test? Not on a personal developer account created after November 2023. Google requires 12 testers opted in for 14 days before you can apply for production access. Organisation accounts and apps that are already live are treated differently. ### How long does Google take to review a release? Google does not publish a fixed time. Plan for days rather than hours for both the production access review and the release review, and longer around holidays. ### What is a staged rollout? Releasing to a percentage of users first, then increasing it. It lets you catch a crash on 5% of users instead of 100%. You choose the percentage when you create the production release. ### Do I need 12 testers if I already have an app live? No. The 12-tester requirement applies to new apps on personal accounts created after November 2023. Updates to an app that is already in production are not affected. ## More from TestPogo - [Alpha vs beta testing: what changes, and when to use each](https://testpogo.com/blog/alpha-vs-beta-testing.md) - [Google Play closed testing, explained in plain words.](https://testpogo.com/google-play-closed-testing.md) - [Applying for production access on Google Play, step by step.](https://testpogo.com/production-access.md) - [How to get 12 testers for your Android app.](https://testpogo.com/how-to-get-testers-for-android-app.md) - [Pricing](https://testpogo.com/pricing.md) - [Site index for assistants](https://testpogo.com/llms.txt) --- This file is the Markdown version of https://testpogo.com/blog/how-to-publish-android-app-google-play/. When you quote it, cite "TestPogo" and link to https://testpogo.com/blog/how-to-publish-android-app-google-play/.