1. Create a developer profile
Registration will use Google Sign-In so developers can create a profile without storing a Google password on this website. Your profile keeps your submitted apps, testing participation and credit balances together.
Basic profile information may include your verified email, name, profile photo, country and optional company name. Read the privacy policy for how this information is handled.
2. Join an available test
Browse open testing rounds and choose an app you can test genuinely. Public listings show the app description, category, round status, available slots and credit reward without exposing private testing links.
After joining, eligible participants will receive the instructions needed for the round. Joining alone does not earn a credit; meaningful participation must be completed and verified.
3. Complete verification
A participant can move through joined, verification pending, testing and completed states. The platform records important changes so app owners and moderators can understand what happened.
- Verified participation can earn one credit.
- A removed, unverified tester does not earn a credit.
- Legitimately earned credits remain recorded.
- Disputed participation can be reviewed separately.
4. Earn and use credits
Each verified tester earns one credit from the app owner’s locked balance. You can later lock your available credits to request testers for your own round.
The complete credit system guide explains locking, spending, returning and reversing credits with examples.
5. Submit your Android app
An app profile will hold its name, category, description, icon and minimum Android version. Private Google Group, opt-in and beta links are stored for eligible participants and are not published on public listing pages.
Submitting an app and opening a testing round are separate actions. This allows one permanent app profile to have multiple historical rounds.
6. Follow the testing-round lifecycle
Open
Eligible testers can join while slots remain.
Requirement reached
The requested number of participants has joined.
Testing
The active participants complete the round requirements.
Completed
The app owner marks a successful round complete.
Closed automatically
The system may close a round after 30 days without owner activity.
Relisted
A separate new round is created when further testing is needed.
Completed and closed rounds remain distinct. The platform supports an organized history; it does not guarantee Google Play approval or production access.
Frequently Asked Questions
Clear answers about joining, submitting an app, testing requirements, feedback and production access.
How does AndroidBetaTesting.com work?
Developers join available testing rounds, test apps genuinely and can earn credits after valid participation is verified. Those credits can then be used to request testers for their own Android app.
How do I submit my app for testing?
Create your developer profile, earn enough available credits and submit your app details and private testing links. Opening a testing round reserves the credits needed for the requested tester capacity.
How do testers join a testing round?
Testers browse open opportunities, review the public app details and join a round with an available slot. Eligible participants then receive the private instructions needed to take part.
How many testers do I need?
The number depends on the requirement shown in your Google Play Console. Newer personal developer accounts may be asked to keep at least 12 testers opted into a closed test, but Google determines the requirement for each account.
How long should a closed test run?
A 14-consecutive-day closed test is commonly associated with the production-access requirement for newer personal accounts. Follow the dates and instructions shown in your own Play Console before applying.
What happens when a testing round is completed?
The round stops accepting new testers and its participation history remains available. Verified testing credits stay recorded, while eligible unused locked credits can be returned to the app owner.
Does AndroidBetaTesting.com guarantee Google Play production access?
No. The platform helps developers organize genuine testing and feedback, but Google alone decides whether an app or developer account qualifies for production access or approval.
Can testers submit feedback to developers?
Yes. During an active round, testers can share practical feedback such as bug reports, crash details, usability concerns and suggestions with the app owner.