Testing guide
How testing works
AppFledge is a community exchange: developers make an app available for closed testing, and other builders test it on real Android devices. The dashboard coordinates the work; Google Play remains the source of the closed-test install.
Know this before you start
- Each test page shows its exact duration; new tests normally use a 16-day window.
- The window starts when each tester confirms their Google Play opt-in, not when they first join AppFledge.
- Participation, check-ins and updates are self-reported. AppFledge does not automatically inspect Play Console.
- Completing the workflow does not guarantee production access or Google Play approval.
For app developers
- 1
Add the app
Provide the app details, Google Play closed-test link, practical tasks and the feedback questions testers should answer.
- 2
Complete readiness checks
Confirm the Play listing, data safety, declarations, closed release, opt-in link and pre-launch review before publishing the test.
- 3
Add consenting testers
Download the current tester-list file and add those Google Play emails to the correct closed-testing track. Withdrawn testers disappear from future exports.
- 4
Follow progress
Review opt-in confirmations, check-ins, device coverage and updates. Record the opted-in count shown in Play Console because AppFledge cannot read it automatically.
- 5
Use the report
At the end, review participation and feedback, then use the generated evidence as a draft for your own production-access answers. Verify every answer before submitting it to Google.
For testers
- 1
Choose an app
Review the app description, test duration and tasks before joining. You cannot test your own app.
- 2
Consent and save your setup
Confirm the Google Play email used on your device, your device model and Android version. Region is optional. You separately agree to share the Play email with that app's developer.
- 3
Join through Google Play
The developer adds your consented email to their closed-test list. Follow the Play testing link, opt in, install the app, then confirm the opt-in in AppFledge. Your individual testing clock starts at that confirmation.
- 4
Use the app through the full period
Follow the developer’s tasks, check in as you test, and keep the app installed and opted in. A check-in can include a short note and an optional screenshot.
- 5
Share useful updates
Tell the developer what you tried, what worked, what was confusing and what broke. You can add multiple updates as testing continues.
- 6
Finish and earn the reward
Stay active for the full period and share a qualifying update at or after your deadline. The server records the testing reward once; early or repeated updates do not create extra rewards.
What is shared during a test
| Information | Required? | Visible to the app developer? |
|---|---|---|
| Google Play email | Required to join, with specific consent | Yes, so the developer can add it to their closed-test list |
| Device model and Android version | Required once for tester setup | Yes, for coverage and testing reports |
| Broad region | Optional | Yes, if provided, for coverage reporting |
| Check-in screenshot and note | Optional | Yes, for the relevant test; screenshots use private storage |
| Testing updates and ratings | Updates are needed for the completion reward; categories and ratings are optional | Yes, so the developer can act on the feedback |
Authorised AppFledge administrators can also access these records to operate the beta, support users and investigate misuse. Other testers do not receive your Play email or private testing content. Read the Privacy notice for retention, providers and request options.
If you need to stop
A tester can withdraw from an active test. This stops future participation, makes the saved history read-only and removes the email from future tester-list exports. It does not erase prior activity or pull the email back from a file or Google Play Console the developer already received. A developer can stop a campaign, but already-earned rewards remain recorded.
What AppFledge does not do
- It does not distribute APK files; installs use the developer's Google Play testing link.
- It does not ask for your Google password or sign in to Google on your behalf.
- It does not automatically verify installs, continuous Play participation or production access.
- It does not promise a fixed join date, tester count beyond the campaign target, or approval from Google.