6.0 KiB
6.0 KiB
Google Play Testing & App Distribution Guide
This document is a permanent reference guide covering Google Play's 14-day closed testing requirements, how to find reciprocal testers (Telegram, Reddit, automated platforms), and the alternative distribution channels available.
1. Google Play Console Policies for Personal Accounts
The 14-Day Closed Testing Rule
For all personal developer accounts created after November 13, 2023:
- Requirement: At least 12 testers (formerly 20) must remain continuously opted-in to your closed test for 14 consecutive days.
- Activity: Testers must download, open, and occasionally interact with the app. Google detects "idle installs" where the app is never opened.
- Per-App Enforcement: This requirement applies to every new app created under a personal account. You cannot "graduate" the account to skip it for future apps.
- Updates Are Exempt: Once an app is approved and promoted to Production, all future updates (e.g. v1.17, v1.18) go straight to production with zero testing or waiting periods.
How to Permanently Skip the Rule (All Apps)
- Organization / Business Account: If you register or convert your Google Play Console account into an Organization account (requires an official company name and a free D-U-N-S number):
- The closed testing rule is completely waived.
- Every app you publish goes straight to public Production with 0 testers and 0 days of waiting.
2. How to Fulfill the Closed Testing Requirement (Free)
A. Telegram Groups & Channels
Thousands of indie Android developers coordinate mutual "test-for-test" swaps in Telegram chats:
- Search Terms in Telegram:
Android Closed TestingGoogle Play TestersTesters CommunityApp Testing Exchange
- How the Swap Works:
- You post your app's closed testing link in the chat.
- Another developer installs your app and sends you a screenshot as proof.
- You install their app and send them a screenshot in return.
- Both agree to keep the app installed for the full 14 days.
B. The "Google Group" Secret (Saves Huge Time)
Instead of manually asking for and typing 20 individual Gmail addresses into Play Console:
- Go to groups.google.com and create a free Google Group (e.g.
my-app-testers@googlegroups.com). - Set the group permission to "Public / Anyone can join".
- In Google Play Console under Closed testing → Testers, select Google Groups and paste your group email.
- Share the single Google Group link in Telegram or Reddit. Anyone who clicks "Join Group" is automatically an authorized tester without you lifting a finger!
C. Reddit Communities
The most active open forums for finding tester swaps:
- r/AndroidClosedTesting: reddit.com/r/AndroidClosedTesting
- r/TestersCommunity: reddit.com/r/TestersCommunity
- r/TestMyApp: reddit.com/r/TestMyApp
D. Automated Tester Exchange Apps
If you don't want to chat with strangers in Telegram or Reddit:
- Testers Community (testerscommunity.com):
- Downloadable directly from Google Play.
- Over 50,000+ registered Android developers.
- Do testers earn money? No. Individual testers do not get paid real cash; they earn platform credits by installing and keeping other developers' apps. Those credits are then spent to have other developers test their app (barter system).
- How the platform monetizes: The platform owners sell paid VIP/fast-track packages ($15–$25) to developers who want to skip testing others' apps.
- Built-in automated tracker monitors the 14-day countdown for you.
- Other Platforms: IndieAppCircle, BetaCircle, Dozenflow.
E. Important Testing Tips
- Aim for a Buffer (15–20 Testers): If you only have 12 testers and one person uninstalls the app on Day 10, Google resets the 14-day timer. Always recruit 15–20 to ensure you stay above 12.
- Hardware-Dependent Apps (like TPMS): Other testers will not have your USB TPMS receiver hardware plugged into their phones. That is completely fine. Google's system only checks that real Google accounts downloaded the app from Google Play and opened it.
3. Alternative Distribution Options (Zero Google Play Nonsense)
Option A: Built-in 1-Click In-App Updater (Current Setup)
- How it works: The app checks the Gitea API (
https://git.vhelectronics.com/api/v1/repos/vhadmin/Deelife-TPMS/releases/latest). When an update is published, the user taps "Update Now" and the APK downloads with a progress bar and installs via Android's nativeFileProviderprompt. - Pros: 100% independent, instant releases, works perfectly on car stereos without Google Play Services.
Option B: Self-Hosted F-Droid / Droid-ify Repository
- How it works: We configured a signed F-Droid repository directly inside Gitea (
fdroid/repo/). - Repository Address:
https://git.vhelectronics.com/vhadmin/Deelife-TPMS/raw/branch/main/fdroid/repo - Fingerprint (SHA-256):
F5757843EB4398BBF091F1BE73F228CB1975CBFBAC45201A53B4C9D3591247FF - IzzyOnDroid Inclusion: Submit an inclusion request on GitLab (gitlab.com/IzzyOnDroid/repo/-/issues/new). Once accepted, the app appears directly in Droid-ify's default global search.
Option C: Obtainium
- How it works: Open-source Android app manager that directly tracks Gitea/GitHub/GitLab release pages.
- Usage: Paste
https://git.vhelectronics.com/vhadmin/Deelife-TPMSinto Obtainium on your car head unit or phone. It detects new releases and updates them automatically.
Option D: Google Play Internal Testing
- How it works: Private test track on Google Play.
- Pros: Up to 100 testers can install and receive auto-updates from Google Play via an invite link with zero review wait time and zero 14-day requirements.