What beta includes
| Item | During beta |
|---|---|
| First app | One free app per builder |
| Credit card | Not required |
| Additional apps | Waitlist |
| Paid plans | Unavailable |
The exchange costs your time: you test other community apps and share useful updates. Tester availability depends on the pool, so there is no fixed promise of when testers will arrive or how many will join.
Starter Boost
Starter Boost is available once per account and sponsors up to three tester joins during a 14-day boost. It activates when you install a community app and report your Google Play opt-in. If the community pool is empty, the boost can activate without that contribution step.
How credits work
When tester access is ready, 10 credits or a sponsored slot is reserved. The credits or slot are used when the tester confirms installation. If the tester leaves or the access deadline expires before installation, the reservation is released.
Qualifying testing updates can earn credits; check-ins alone do not. Credits are not cash and cannot be transferred. See Starter Boost and credits for the exact reward criteria and deadlines.
Testing time and expectations
New AppFledge tests normally run for 16 days, and each test shows its exact duration. Google's requirement for eligible personal developer accounts is 14 days; check Google's current requirements and your Play Console.
See an explicitly fictional testing report example to understand the kind of record an app owner can review.
Have an Android app ready for closed testing?
AppFledge connects builders who test each other's apps. Your first app is free during beta; you contribute testing time in return. Tester availability and Google Play approval are not guaranteed.