How to Pass the Google Play 20-Tester Rule for TWA Apps

Understanding the Google Play 20-Tester Rule

For personal developer accounts created after November 2023, Google Play requires a closed test involving at least 20 active testers for a minimum of 14 consecutive days before you can apply for production access. For developers converting a Progressive Web App into an Android app using a Trusted Web Activity, this testing period has specific technical and procedural requirements.

This testing policy is designed to ensure that apps launched on the Play Store are stable, functional, and secure. Because a TWA is essentially a web application loaded inside a native system wrapper, your testing strategy must address both the web application layers and the native container components. Failing to maintain 20 active testers or failing to configure your web assets correctly during this 14-day window will result in Google rejecting your production application, forcing you to restart the testing period.

Configuring the Closed Testing Track for a TWA

To begin the testing process, you must generate a signed Android App Bundle (AAB) of your TWA. This bundle is uploaded to the Closed Testing track within your Google Play Console. Setting up this track requires selecting a distribution method and establishing your tester base.

In the Google Play Console, navigate to the Closed Testing section and create a new release. You have two primary methods for enrolling testers:

• Google Groups: This is the highly recommended approach. You create a single Google Group, add the email addresses of your 20 or more testers to it, and link the group to your closed testing track. Testers can then join using a single opt-in link.
• Email Lists: You manually input individual email addresses. This is harder to manage at scale as any updates to the tester group require manual list modifications within the Play Console.

Ensure that your testers are registered with the primary email addresses they use on their Android devices. If a tester attempts to opt in using a non-Android Google account, they will not be able to download the application from the Play Store link.

Managing Digital Asset Links During Testing

The most common failure point during TWA testing is a broken Digital Asset Link connection. When testing on a closed track, the asset link verification must remain fully functional so testers do not see a web browser URL bar at the top of the application wrapper.

To prevent the URL bar from showing during testing, your production domain must serve the correct SHA-256 fingerprint in the assetlinks.json file. This gets complicated because Google Play App Signing often changes the signing key of your application package when it is uploaded to the store.

If your assetlinks.json file only contains the fingerprint from your local upload keystore, the app downloaded by your closed testers from the Google Play Store will fail verification, displaying the browser address bar. You must retrieve the App Signing SHA-256 fingerprint from the Google Play Console and append it to your website server configuration before inviting users to test.

Recruiting and Tracking Your 20 Testers

The 20-tester rule is strict: 20 separate users must remain opted in to your closed test for 14 continuous days. If a tester opts out on day 10, dropping your active tester count to 19, the 14-day counter resets.

To ensure compliance, you should recruit at least 25 to 30 testers to build a safety margin. When tracking opt-ins, keep the following rules in mind:

• Active Status: Testers must download and install the app on their device. Merely clicking the opt-in link without downloading the software does not count toward the active tester metric.
• Device Activity: While testers do not need to use the app every hour, Google monitors whether the app is installed and interacting with the device lifecycle. Instruct your testers not to uninstall the app during the 14-day tracking period.
• Updates: If you deploy web-side updates to your PWA during the 14-day period, these will stream automatically to your testers because of the TWA architecture. This does not disrupt the 14-day timeline. However, if you update the native container app and upload a new AAB, ensure your testers' devices successfully download the update to maintain active testing metrics.

Preparing Your Final Production Access Application

Once you complete the 14 consecutive days of testing with at least 20 active testers, the option to apply for Production Access will become available in your Google Play Console. This application is not approved automatically; a Google specialist manually reviews your submission.

You must answer several detailed questions about your testing process. Prepare your answers based on these criteria:

• Testing Methodology: Detail how you recruited your testers, what instructions they were given, and what types of devices they used to verify the app. Highlight that you verified the TWA on multiple screen sizes and Android OS versions.
• Feedback Mechanisms: Describe how testers reported issues to you. You can set up a simple feedback form on your website or use a support email address. Provide examples of constructive feedback received during the test.
• Bug Fixes and Technical Improvements: Explain what bugs were discovered and how they were resolved. For a TWA, this often involves detailing how you optimised service worker caching, adjusted CSS layouts for specific aspect ratios, or improved offline error pages during the 14-day testing run.