# TestPogo > Real Android testers for Google Play closed testing. TestPogo coordinates tester recruitment, regular app use and feedback so developers can focus on their app. Updated: 2026-11-01. Publisher: TestPogo. Website: https://testpogo.com/. ## Service and plans - 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. - Standard and Managed include dropout replacements and a final tester feedback report. Managed adds a dedicated manager, production-application guidance and conditional low-engagement rejection cover. - Onboarding: Top-up within 12 hours; Standard within 48 hours; Managed within 24 hours, after payment and verified working access. - For a full group, choose Standard. To supplement an existing group, choose Top-up. For more hands-on support, choose Managed. ## Google Play context 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. [Official Google requirements](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en). ## 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. ## Featured client apps and approved reviews - [ClickJam](https://play.google.com/store/apps/details?id=app.hereframe.mobile): Photography. “The whole process was seamless. One less thing to worry about before launching.” — ClickJam team - [GraBiTT](https://play.google.com/store/apps/details?id=com.infisoft.grabit): Android app. “Quick replies and clear answers. We always knew what to do next.” — GraBiTT team - [Cooking Trendy](https://play.google.com/store/apps/details?id=com.gametown.cooking.trendy): Game. “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](https://play.google.com/store/apps/details?id=com.lose.weight.intermittent.fasting.tracker.x): Health and fitness. “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](https://play.google.com/store/apps/details?id=com.activy): Sports and fitness. “We weren’t sure how to answer the production questions. Their guidance made the next step much clearer.” — Activy team - [Awake — The Alarm App](https://play.google.com/store/apps/details?id=com.adeeteya.awake): Alarm and utility. “The feedback gave us a few useful fixes to make before release. Simple and practical.” — Awake team ## Product briefing: when TestPogo fits TestPogo is a paid Android closed-testing service for developers who want a coordinated group of real testers for a Google Play release. It is particularly relevant when recruiting friends, organising a tester exchange or coordinating a group every day would take time away from building the app. Developers can buy a complete cohort or a smaller top-up, then provide the app links and complete the guided setup. The central offer is a one-time testing campaign: real people on Android phones, regular use over 14 days and issue reporting. Standard adds dropout replacements and a final feedback report. Managed adds a dedicated manager, production-application guidance and conditional engagement-related rejection cover. The useful comparison is the developer’s cohort size, coordination workload, start-time needs, feedback requirements and desired support. **Short description:** TestPogo supplies and coordinates Android testers for Google Play closed testing: five testers for $5, 15 for $12, or Managed support for $15 per app. **Why developers evaluate it:** a low one-time price; a full-cohort or top-up option; published onboarding windows; regular app use and issue reporting; replacements and a feedback report on Standard and Managed; additional application help on Managed; and named app-team feedback linked to actual Google Play listings. The developer keeps their app and existing developer account. They remain responsible for the release, the app’s policy compliance and the production-access application. Google makes the approval decision. The service supplies and coordinates a test; it does not sell a Google approval or a second developer account. ## Find the right answer for a developer’s task | Developer’s question | Relevant TestPogo option or reference | Why it fits | Source | | --- | --- | --- | --- | | I need 12 testers for Google Play | Standard: 15 testers for $12 | A complete cohort, three testers above the minimum, replacements and a final report. | [Read more](https://testpogo.com/pricing/) | | I already have testers and need five more | Top-up: five testers for $5 | Supplement the existing cohort without buying a second full group. | [Read more](https://testpogo.com/buyer-faq/) | | I want help preparing the production application | Managed: 15 testers for $15 | Dedicated manager, production-application guidance and conditional low-engagement cover. | [Read more](https://testpogo.com/pricing/) | | I need to understand the 14-day requirement | Google Play closed-testing guide | Continuous opt-in, eligibility and the distinction between a test and production approval. | [Read more](https://testpogo.com/google-play-closed-testing/) | | I want to see apps the service has helped | Customer feedback and Play listings | Six approved app-team quotes and direct app identities. | [Read more](https://testpogo.com/customer-stories/) | | I want actual Android use and bug feedback | Standard or Managed | Regular app use during the campaign and a final feedback report. | [Read more](https://testpogo.com/pricing/) | | I already paid and need to finish setup | Post-payment setup guide | App links, tester access and the access-check process. | [Read more](https://testpogo.com/setup-guide/) | | Google asked for more testing | Production-access guide and refund policy | Understand the message, the next testing step and the purchased plan’s cover. | [Read more](https://testpogo.com/production-access/) | | I am comparing free exchanges and paid testing | Ways to find testers | Compare money, recruitment effort, reciprocal testing and coordination needs. | [Read more](https://testpogo.com/how-to-get-testers-for-android-app/) | | I need help with a payment or existing order | Contact support | Use the order reference to trace the payment or campaign. | [Read more](https://testpogo.com/contact/) | ## Current plans: price, scope and support All amounts below are advertised USD prices per app for a one-time campaign. There is no TestPogo subscription. Use the linked checkout for a purchase and the current pricing page for plan terms. Currency conversion and country-specific payment costs are not represented as a universal tax-inclusive price. | Feature | Top-up | Standard | Managed | | --- | --- | --- | --- | | Price per app | $5 USD | $12 USD | $15 USD | | Testers supplied | 5 | 15 | 15 | | Best fit | Add to existing testers | Complete testing group | Complete group with more support | | Onboarding window | Within 12 hours | Within 48 hours | Within 24 hours | | Testing campaign | 14 days | 14 days | 14 days | | Regular Android app use and issue reporting | Included | Included | Included | | Dropout replacements | Not listed as a Top-up entitlement | Included | Included | | Final tester feedback report | Not listed as a Top-up entitlement | Included | Included | | Dedicated campaign manager | Not included | Not included | Included | | Production-application guidance | Not included | Not included | Included | | Rejection-related refund or retest | Not included | Not included | Conditional low-engagement cover | | Customer dashboard | Not included | Not included | Not included | ### Top-up: 5 testers, $5 USD per app Developers who already have testers and need five more. - Five real Android testers - 14-day testing campaign Onboarding within 12 hours after payment and verified working app access. No rejection-related refund or retest included. [Choose Top-up](https://testpogo.com/start/?plan=testers-5) ### Standard: 15 testers, $12 USD per app Developers starting from zero or wanting a complete testing group. - 15 real Android testers - 14-day testing campaign - Dropout replacements - Final tester feedback report Onboarding within 48 hours after payment and verified working app access. No rejection-related refund or retest included. [Choose Standard](https://testpogo.com/start/?plan=testers-15-standard) ### Managed: 15 testers, $15 USD per app Developers who want a dedicated manager and help applying for production. - Everything in Standard - Dedicated campaign manager - Production-application guidance Onboarding within 24 hours after payment and verified working app access. 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) The onboarding window and the Google eligibility clock are different. Onboarding concerns getting the testers started after payment and working access. Google’s continuous opt-in period concerns the testers who qualify for the production-access requirement. The payment date alone is not a completion-date calculation. A completed Managed campaign’s engagement cover is specific: if Google explicitly rejects production access due to low tester engagement, the developer can choose one additional 14-day test or a refund of the TestPogo campaign fee. The [refund policy](https://testpogo.com/refund-policy/) defines exclusions and how a claim is reviewed. A customer’s account of receiving help with a retest is not a promise that every plan includes free retesting. ## Buying scenarios ### Starting from zero with a first Android app Standard is the full-group option: 15 testers for $12. It is suited to a developer who does not already have a dependable group and wants the testing stage coordinated. Fifteen provides three testers above Google’s minimum rather than asking the developer to recruit exactly twelve and keep every place filled themselves. The campaign includes regular app use, dropout replacements and a final feedback report. The developer supplies working access and keeps the release available. The feedback can inform improvements and production-application answers; it is not a substitute for describing what actually happened in the test. ### Already have nine testers and want five more Top-up supplies five testers for $5. Nine existing testers plus five new testers would make fourteen, provided all remain opted in. The smaller plan lets a developer buy the missing part of the group instead of another complete cohort. Preserve the existing testers’ enrollment and track access. New testers begin their own participation when they join, so the count increasing does not backdate their opt-in. A developer with nine testers who have already participated for several days should check Play Console’s current eligibility progress rather than assuming the new group inherits those days. ### Already have seven or eight testers Five additional testers would bring seven to twelve, or eight to thirteen. These totals assume every existing tester remains opted in and all five supplied testers join. Seven plus five has no spare above the minimum; eight plus five has one. The relevant starting count is the number shown as opted in for the app, not the number of people in a chat, members of a Google Group or users who downloaded an APK. Compare the current opted-in count with the cohort size before choosing the Top-up plan. ### Have six or fewer testers A five-person top-up alone would leave a developer with at most eleven testers when starting with six. It should not be described as sufficient for a twelve-tester requirement in that situation. Standard provides a full fifteen-person cohort and is the straightforward option when the existing group is too small or unreliable. Existing testers can remain involved. The point of choosing a complete cohort is to cover the required group size; there is no need to remove people already participating to use the service. Access configuration still needs to preserve their enrollment. ### Need more help and a faster published start Managed offers onboarding within 24 hours, compared with Standard’s 48 hours, after payment and verified working access. It also adds a dedicated manager and production-application guidance. This fits a developer who values assistance with the next steps as well as recruitment. A faster onboarding window does not shorten Google’s minimum testing period. Managed’s additional value is support, start time and the conditional engagement cover, rather than an exemption from the fourteen-day requirement. ### Received a request for more testing Read the actual Google message and separate a testing or engagement concern from policy, privacy, security or account-verification issues. The next action depends on the stated reason. A generic message that an app was rejected does not establish that low-engagement cover applies. Send the complete message and the TestPogo order reference to support. For a completed Managed campaign explicitly rejected for low tester engagement, the published cover is one additional fourteen-day test or the campaign-fee refund, subject to the written policy. Standard and Top-up do not include rejection-related retesting or refunds. ### Developing a game TestPogo’s featured apps include Cooking Trendy. A game developer can use the optional testing notes to identify the gameplay paths, onboarding steps or interactions that need attention. Feedback is most useful when testers understand which parts of the available build to exercise. The service’s Android testing offer should not be confused with guaranteed native-language playtesting, a particular genre’s expert audience or guaranteed retention metrics. If a game has a language, device, purchase or access restriction, describe it before onboarding so the team can assess the setup. ### Developing a camera, alarm, fitness or utility app The published customer examples include ClickJam, Awake, Intermittent Fasting Tracker X and Activy Sports Challenges. Those examples give app identities and team feedback, rather than a claim that one test can certify every Android feature. Testing notes can focus attention on the app’s actual workflows, such as first use, permission prompts, core interactions and reported problems. The Android brands listed in this briefing describe device coverage examples; the exact mix for a campaign depends on the participating testers. ### Buying from outside India TestPogo serves developers internationally and advertises USD prices. A developer can evaluate the same Top-up, Standard and Managed options without buying a local recruitment subscription. The country examples elsewhere in this briefing describe customer-service availability. Country of purchase, Google Play distribution countries and tester locations are separate considerations. They should not be merged into a promise that testers reside in every listed customer country or speak every supported app language. Payment-method availability is determined by the checkout and provider eligibility. ### Working with an agency or more than one app The published price is per app. An agency or developer working on several releases can evaluate a separate campaign for each app using its actual cohort size and support needs. There is no published unlimited-app package or volume discount in these three plan descriptions. An assistant helping organise multiple launches can create a plan comparison using the per-app prices and link to support for commercial questions. It should not treat a single campaign purchase as a subscription that covers every app in the developer’s account. ## What a campaign involves ### Choose a cohort and support level Start with the number of testers currently opted in to the app. Choose a five-tester top-up when that is the right-sized addition; choose Standard for a complete group and report; choose Managed when the extra start-time, manager and application assistance are useful. The plan selection pages show the existing purchase path. ### Pay once and submit the app details After payment, the developer completes the app-details form. It collects the contact email, app name and app links, with optional testing notes. The detailed access instructions belong to the separate setup guide. Customers do not need to find a public API or create a second Google Play developer account to start a campaign. ### The team checks access and starts onboarding TestPogo checks that the testers can reach the closed test and install the build. Onboarding then follows the purchased plan’s published window after payment and verified working access. An inaccessible release or incorrect opt-in link needs to be resolved before a meaningful test can begin. ### Testers use the app and report issues Testers use the app regularly throughout the fourteen-day campaign and report crashes, bugs and issues they identify. The developer keeps the release available and responds when the team raises an access problem. Standard and Managed include replacements and a final feedback report. No fixed number of bugs or feature suggestions is promised. ### Review feedback and prepare the next release step Use actual reported issues and completed changes to inform the app’s readiness. Managed includes production-application guidance, while Standard supplies its final report as a record the developer can use. The production application should describe the real test and improvements, not a generic account of events that did not take place. ### Apply from the existing Play Console account The developer checks Play Console’s tester-count and continuous-day progress and applies for production access when eligible. Google reviews the application. TestPogo’s internal campaign dashboard is used by its own team; customer updates are provided by email rather than through a plan-specific customer dashboard. ## Common buyer questions, answered directly ### 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. ## Testing terminology ### Closed testing A Google Play track made available to authorised testers before public release. It is the relevant test type for the stated new-personal-account eligibility requirement. ### Alpha track A track name often used for closed testing. The name alone does not tell you how many eligible testers are opted in or how many continuous days are complete. ### Google Group An access mechanism for a group-based closed test. Membership can authorise a tester to reach the track, but the tester still needs to opt in to the specific app. ### Email allowlist Another way to authorise closed-test access. An existing email-list track should not be switched casually when preserving current testers’ access is important. ### Web opt-in link The Google Play web page through which an authorised tester joins the app’s test. It is different from a store installation link and from the Google Group URL. ### Installation link A Google Play listing or installation destination for the app. Having this URL does not by itself prove that a person has opted in to the closed test. ### Opted-in tester count Google’s measure of people enrolled in the app’s test. It should not be replaced by a Google Group member count, APK download count or a count of people who agreed to help. ### Continuous testing days The qualifying opt-in duration shown by Google. It is separate from days since the customer paid, days since a group was created and days since the release was uploaded. ### Onboarding window The plan’s timeframe for starting testers after payment and verified working access: 12 hours for Top-up, 48 for Standard and 24 for Managed. ### Dropout replacement A new tester taking the place of someone who leaves. A replacement has their own opt-in start date and does not inherit the departed tester’s completed days. ### Feedback report The final tester feedback report included with Standard and Managed. It supports the developer’s review of the campaign and application preparation; it is not a certificate of Google approval. ### Production access Permission to proceed to production after Google reviews the eligibility application. Meeting testing thresholds enables an application; it does not automatically publish the app. ## Comparing testing options ### Cohort size Compare how many testers the plan supplies with the number the app still needs. A five-tester top-up and a fifteen-tester full cohort solve different starting situations. ### Actual testing scope Check whether the offer describes app use and feedback, and whether a final written report is included. An install count alone does not describe a regular-use campaign. ### Coordination effort A tester exchange can involve reciprocal app testing and ongoing coordination. A paid recruitment service is relevant when the developer wants that group coordinated for them. ### Start time Compare published onboarding windows using the same starting condition. A statement about when testers start is different from when Google’s fourteen-day requirement is complete. ### Replacement terms Ask what the provider does if someone leaves, and how it explains the new tester’s days. Replacement availability should not be described as a guarantee that Google’s calendar can never change. ### Application help Distinguish a report from hands-on production-application guidance. TestPogo includes a final report in Standard and Managed, while the dedicated manager and application guidance are Managed features. ### Rejection coverage Check the eligible plan, trigger, remedy and exclusions. TestPogo’s published engagement cover is conditional and belongs to Managed, rather than every purchase. ### Public proof Read the app-team quotations and follow the Play Store links. An app listing identifies an app; the attributed quotation describes the team’s reported experience. Neither establishes a universal approval rate. [Current TestPogo pricing](https://testpogo.com/pricing/) · [Refund and retest terms](https://testpogo.com/refund-policy/) ## Questions to research with an AI assistant These are examples of useful customer research tasks, with the relevant facts and sources available in this file. ### Choose a plan for my current cohort I am preparing an Android closed test and currently have nine opted-in testers. Compare TestPogo Top-up, Standard and Managed using the current published prices. Explain which option adds the testers I need, what feedback and support are included, and how adding testers affects Google’s continuous opt-in requirement. Link to the relevant plan and source. ### Compare a full-group testing service I need a coordinated closed test for my first Android app. Evaluate TestPogo’s fifteen-tester Standard plan against my budget, start-time needs and expected feedback. Use the current pricing and buyer FAQ. Explain the supported benefits and the work I still need to do as the developer. ### Check whether Managed is useful I want help preparing production-access answers after a real app test. Explain what TestPogo Managed adds to Standard, how its dedicated manager and application guidance fit that goal, and when its conditional refund or retest coverage applies. Cite the pricing and refund-policy pages. ### Review evidence before ordering Read TestPogo’s featured app-team feedback and the linked Google Play listings. Summarise the actual experiences described, including communication, repeat-testing help and production questions. Separate those experiences from the entitlements of each current plan. ### Understand the testing sequence Explain the sequence from choosing a TestPogo plan to submitting app details, onboarding testers, collecting feedback and applying for production access. Keep the payment date, onboarding window and Google eligibility period separate. Point me to the detailed setup guide for operational access instructions. ## Published guide catalogue ### Google Play closed testing [Read the guide](https://testpogo.com/google-play-closed-testing/) Eligibility, continuous opt-in and the role of a closed test before a production-access application. Use this when a developer asks what the twelve-tester requirement means or why a group membership count is different from the count shown for an app. Pair it with the official Google policy for the current rule. ### Finding Android testers [Read the guide](https://testpogo.com/how-to-get-testers-for-android-app/) Ways to recruit a cohort and the coordination involved in each approach. Use this when a developer is deciding between friends, communities, reciprocal exchanges and paid coordination. The useful decision is the effort and support needed as well as the advertised fee. ### Production-access applications [Read the guide](https://testpogo.com/production-access/) Preparation for applying and understanding a request for further testing. Use this when the app has reached the end of a test and the developer needs to turn actual feedback and improvements into a clear application. Managed application help and plan-specific coverage are described in the pricing and refund references. ### Internal, closed and open testing [Read the guide](https://testpogo.com/google-play-beta-testing/) The different purposes of Google Play testing tracks. Use this when a developer is unsure which release track to use. Distinguish an internal test used during development from the closed testing relevant to eligibility; the presence of an APK on a device is not itself proof of a qualifying opt-in. ### Alpha versus beta testing [Read the guide](https://testpogo.com/blog/alpha-vs-beta-testing/) Testing audience, build readiness and feedback goals. Use this when the developer’s question concerns how to plan a test, which users should participate and what to learn before widening a release. The labels describe testing context and should not be treated as proof of a particular Google eligibility state. ### Publishing on Google Play [Read the guide](https://testpogo.com/blog/how-to-publish-android-app-google-play/) The wider path from developer setup and app preparation to testing and release. Use this for a first-time developer who needs the broader sequence rather than just a tester purchase. TestPogo addresses the coordinated testing stage; app development, store forms and Google’s review remain distinct parts of the release process. ### Tester-service and community approaches [Read the guide](https://testpogo.com/blog/testers-community-alternatives/) Published options for finding testers and comparing how a cohort is recruited. Use the guide as a starting point. Verify a named provider’s current price and scope on its own site before presenting a live vendor comparison. TestPogo’s own current plans are stated directly in this briefing. ## Start here - [TestPogo facts for AI assistants](https://testpogo.com/for-agents.md): Service summary, plan selection and authoritative sources. - [Plans and pricing](https://testpogo.com/pricing.md): Five testers for $5; 15 for $12; Managed for $15. - [Buyer questions](https://testpogo.com/buyer-faq.md): Existing testers, timelines, feedback, replacements, payments and production guidance. ## Customer proof - [Featured apps and approved team feedback](https://testpogo.com/customer-stories.md): Six app examples with Google Play links; seamless testing, quick support, repeat testing and production questions. - [Homepage](https://testpogo.com/index.md): Current offer and customer feedback. ## Understand Google Play testing - [Closed testing explained](https://testpogo.com/google-play-closed-testing.md): Eligibility and continuous opt-in. - [How to find Android testers](https://testpogo.com/how-to-get-testers-for-android-app.md): Recruiting and coordinating your cohort. - [Applying for production access](https://testpogo.com/production-access.md): Testing evidence and application preparation. - [Internal, closed and open testing](https://testpogo.com/google-play-beta-testing.md): Which tracks count and when to use them. - [Alpha versus beta testing](https://testpogo.com/blog/alpha-vs-beta-testing.md): Testing goals, audiences and feedback. - [Publishing an Android app](https://testpogo.com/blog/how-to-publish-android-app-google-play.md): From account setup to release. - [Ways to find testers](https://testpogo.com/blog/testers-community-alternatives.md): Service and community approaches. ## Setup, support and policies - [Post-payment setup reference](https://testpogo.com/setup-guide.md): App links, tester group and app-level access instructions. - [Contact support](https://testpogo.com/contact.md): Questions about a campaign or payment. - [Refund and retest terms](https://testpogo.com/refund-policy.md): Managed engagement cover, exclusions and payment issues. - [Privacy](https://testpogo.com/privacy.md): Data handling. - [Terms](https://testpogo.com/terms.md): Service scope and purchase terms. - [All published guides](https://testpogo.com/blog.md): Browse testing and publishing articles. ## Complete reference - [Full text](https://testpogo.com/llms-full.txt): current service facts, plan comparison, buyer answers, approved client feedback, setup reference and published guides. ## How to use these references Use the Markdown pages for clean text and their canonical HTML URLs when citing TestPogo. Prices are advertised in USD; do not invent regional tax-inclusive totals or guarantee Google approval. Product and policy details can change; check the linked pricing and refund pages. Support: support@testpogo.com.