Direct answers about our testing service, Google Play closed testing, pricing, and guarantees — organized by topic.
General
02
What is AppsTestLab?
AppsTestLab is an independent Android app testing service. We coordinate real people to test your app on real Android devices, then collect and structure their feedback so you know what to fix before launch. We are not affiliated with Google — Google makes all final decisions about your app and account.
What kinds of apps do you test?
We test Android applications — new apps preparing for their first release as well as existing apps shipping updates or bug fixes. Testers install your app on their own physical devices and use it the way real users would, then report what they find. If you're unsure whether your app fits, message us on WhatsApp and we'll confirm before you commit.
Getting Started
06
How do I get started?
Contact us on WhatsApp with a short description of your app and what you're trying to accomplish. We'll confirm what applies to your situation, recommend a package, and set up the testing track. After you've chosen a package, we confirm the details on WhatsApp and testing starts shortly after.
What do I need to provide to AppsTestLab?
For our standard Google Play testing service you need: 1) your app available on the appropriate Google Play testing track, 2) our tester group added to that track — appstestlab@googlegroups.com, 3) the Google Play testing / opt-in link, 4) test credentials if your app requires login, and 5) optionally, testing instructions or specific flows you want us to focus on. You do not need to send us an APK or AAB — our testers access your app through Google Play.
Do I need a Google Play developer account?
You need a developer account to run a closed test on Google Play — Play Console is where the app, tester list, and production application live. You don't need one to start testing itself. We coordinate testing either way and can guide you through account setup if you haven't created one yet.
Do I need to send you my APK or AAB?
No. For our standard Google Play testing service, you do not need to send us the APK or AAB directly. Add appstestlab@googlegroups.com to the appropriate Google Play testing track and send us the Google Play testing / opt-in link.
How do I give AppsTestLab access to my app?
Open your Google Play Console and go to your testing track, add this Google Group as a tester — appstestlab@googlegroups.com — save or publish the configuration, copy your Google Play testing link, and send the link to us on WhatsApp. Our testers then access and install your app through Google Play. If your app requires login, share the test credentials on WhatsApp too — never post credentials publicly.
How do I share my app with testers?
We handle distribution for you. You add appstestlab@googlegroups.com to the testers section of your Google Play testing track and send us the resulting testing link on WhatsApp. You don't talk to individual testers — we manage invitations, installs, and follow-ups so you stay in one conversation: with us.
Testing Process
04
How does the testing process work?
You tell us about your app on WhatsApp, we agree on a package and a testing method, then we coordinate testers to install and use your app on real Android devices over a 16-day cycle. Testers report bugs and observations, we collect and structure the feedback, and you receive a report with findings and actionable next steps.
What happens after I contact you?
We reply within a few hours. We'll ask a few questions to understand your app, your target users, and your timeline, recommend the right package, and confirm the testing plan on WhatsApp. If something isn't ready — a missing build, credentials, or account — we'll tell you exactly what's needed before testers start.
What feedback will I receive?
Testers report bugs, crashes, usability observations, and suggestions from their real-device sessions. Depending on your package, you receive structured feedback and issue reports; the Premium package includes a detailed testing report organized by severity and category, built from real users testing on real devices.
Can I update my app during testing?
Yes. You can push an updated build during the cycle — it's your app and feedback should reflect your latest version. Message us on WhatsApp and we'll coordinate distribution of the update to the testers on the same day, so the feedback you receive covers your newest release.
Google Play & Closed Testing
07
Is AppsTestLab affiliated with Google?
No. AppsTestLab is an independent service, not affiliated with, endorsed by, or connected to Google or Google Play. We help developers organize testing and prepare for launch, and our experience across more than 5,000 apps helps us do that well — but Google alone decides what happens to your account and app.
Where do I find my Google Play testing link?
In Play Console, open your app, go to your testing track, and open the Testers tab — the shareable link for that track is available there. If your closed test uses a Google Group, testers need to join the group before opting in, and the opt-in link is only available once the track's release is published.
Does AppsTestLab help with Google Play closed testing?
Yes. We coordinate the closed testing process end to end: we recruit and confirm testers, make sure they opt in and stay opted in, and track that your account keeps enough testers during the requirement window. We're an independent service — Google makes all final decisions about your account and production access.
How many testers do I need for Google Play closed testing?
Google's current requirement for eligible personal developer accounts created after November 13, 2023 is a closed test with at least 12 testers opted in for at least 14 continuous days before you can apply for production access. Requirements differ by account type and can change over time, so we confirm what applies to your account before you commit.
How long must testers stay opted in?
Google requires at least 12 testers to be opted in for at least 14 continuous days before production access is requested for eligible accounts. Our standard testing cycle runs 16 days, so the continuous 14-day window is comfortably covered while testers put real usage time into your app. Google makes the final call on your application.
Will my app be approved by Google?
No service can guarantee Google approval — Google makes every final decision. What we guarantee is our own work: we historically helped roughly 99% of the apps we tested reach launch, and if your app is not approved after our eligible testing, you get a full refund under our money-back guarantee.
Can you help if my app gets rejected?
Yes. Beyond testing, we help diagnose why an app was rejected and prepare a response. Our pre-submission policy audit catches issues before you submit, and our rejection appeal drafting service helps you respond when Google Play rejects an app — both are separate from testing and handled by our team.
Testers & Devices
04
What devices do testers use?
Real Android devices — never emulators. Our tester pool covers phones and tablets across different manufacturers, Android versions, and screen sizes, so your app is exercised on hardware that matches what real users hold. We won't claim a device mix we can't deliver; on WhatsApp we'll tell you the devices available for your app before testing starts.
Who are the testers?
Real people with real devices, coordinated by our team. They're given clear instructions on your app's core flows, they install and use the app like actual users, and they report what they find. We manage the tester pool directly, including replacing anyone who drops out, so your cycle stays on track.
What happens if a tester becomes inactive?
We replace them — an inactive tester never leaves your cycle short. Replacement is included in our Standard and Premium packages and available as an add-on for Basic. For Google Play closed testing we also watch opt-in continuity, because a tester who opts out resets their own continuous period.
Can you test a specific device or Android version?
If you need validation on a specific device, manufacturer, or Android version — for example a crash that only appears on certain hardware — tell us on WhatsApp before your cycle starts. We'll confirm whether a matching device is available in the pool before you commit, and target sessions at that configuration where possible.
Timelines & Delivery
04
How long does a testing cycle take?
Our standard cycle runs 16 days — long enough for testers to genuinely use the app, and long enough to cover the 14 continuous days Google asks for in eligible closed tests. Initial feedback usually arrives within the first few days; the full report arrives when the cycle completes.
When will I receive the report?
Individual findings come in as testers report them during the cycle, and your organized report is delivered when the 16-day cycle completes. Depth depends on package: Basic gives core feedback, Standard adds structured issue reports, and Premium includes a detailed report organized by severity and category.
Can I shorten or extend the cycle?
Yes. If you're on a deadline or want broader coverage, we can adjust the cycle length. Tell us what you need on WhatsApp and we'll agree on a timeline before testers start — it's confirmed up front, with no surprises later.
How fast can testing start after I commit?
We typically kick off within a few business days of confirming a package on WhatsApp. Setup includes preparing the install link or closed test track and briefing testers. If testers are already opted in on your Google Play account, we can often start sooner.
Pricing & Guarantee
04
How much does testing cost?
Testing is a flat fee per app: Basic (12 testers) is $10, Standard (15 testers) is $15, and Premium (20 testers) is $20. Every package covers a 16-day testing cycle with real testers on real devices. There are no hidden fees — the price is agreed on WhatsApp before testing starts.
How does the 100% money-back guarantee work?
If your app is not approved after our testing, you get a full refund of your eligible testing order — no questions asked. The guarantee covers eligible app testing orders; store listing, ASO, design, and other non-testing services are not covered. Ask us on WhatsApp if you're unsure whether your order qualifies.
Does the guarantee mean Google approval is guaranteed?
No. Google makes every final approval decision, and no service can guarantee it. Our guarantee is a promise about our own work: if your app is not approved after our eligible testing service, we refund that service. Combined with our historically strong approval rate, it's how we stand behind our testing.
What does “after our testing” mean?
It means after the completion of the app testing service you purchased from us. The guarantee covers the testing service itself, not services performed by other providers or work outside the testing you bought — for example store listing or design work. Message us on WhatsApp and we'll confirm refund details directly.
Play Console & Support
03
Do you help with Play Console setup?
Yes. Beyond testing we help with developer account setup, paid app setup, Data Safety forms, content rating questionnaires, Play App Signing, and target audience declarations — the configuration work that sits next to testing. We can also run a Play Console health check to catch issues in an existing listing.
Do you help with store listing?
Yes. After testing we offer store listing creation, screenshot and graphic design, and ASO keyword optimization to prepare your Google Play page for launch. Testing and listing can be combined into a single launch flow — tell us your goal and we'll recommend the right combination.
What support do you offer during testing?
24/7 real human support on WhatsApp throughout the cycle. When testers need a new build, a device configuration changes, or a tester drops out, you message us and we handle it. You get one point of contact and direct answers — not a support queue or tickets.