Submission & Community Requirements
To maintain an effective, safe, and collaborative ecosystem for mutual Android testing tracks, please adhere to our core directory standards.
1 Closed Testing Requirements
If your application is in a pre-release closed testing phase, you must provide clear setup parameters to help independent community testers join your track effectively.
- Credentials: If your application relies on a user account or backend authentication system, you must supply active demo login credentials within your dashboard overview instructions.
- Group Access: Ensure your Google Group or email access list is explicitly synchronized to permit directory users to sign up for beta tracking instantly.
2 Engagement and Retention Rules
Mutual support is the bedrock of indie app validation. Give as much value back to the community as you receive.
- Installation Term: Testers are expected to keep applications installed on active devices until formal production approval is granted by the Google Play Store console. Do not prematurely delete mutual tracks.
- Feedback Quality: Provide honest, constructive structural and diagnostic logs or crash environments to your peers.
💡 Pro-Tip
Apps with clear tester instructions and responsive developers typically reach their 20-tester benchmark twice as fast.