Setting Up Google Play Pre-Registration for TWA Apps

Launching a new mobile app requires strategic planning to build early momentum. For web developers, SaaS founders, and indie makers launching an Android app using a Trusted Web Activity (TWA), Google Play offers a powerful tool: pre-registration. By setting up a pre-registration campaign, you can capture user interest before your application officially launches, and Google Play will automatically install the app on users devices once you publish it.

The Value of Pre-Registration for Web-Based Apps

Pre-registration is not reserved solely for native Kotlin or Java applications. Because a TWA is compiled into a standard Android App Bundle (AAB), it is treated by the Google Play Console as a standard Android application. This allows web-based applications to leverage identical marketing and pre-launch features as native mobile games or enterprise platforms.

For TWA developers, pre-registration offers a unique advantage. Since the core of your app resides on your web server rather than inside the compiled binary, you can run a pre-registration campaign for up to 90 days while continuing to develop, refine, and test your web-side features. The wrapper configuration itself is highly stable and rarely changes. Once the pre-registration period ends, the app installs, downloads your service worker, caches your assets, and serves your web app seamlessly.

Prerequisites for TWA Pre-Registration

Before initiating a campaign in the Google Play Console, you must ensure your technical foundations are in place. You will need:

• A registered Google Play Developer Account, which requires a one-off 25 USD registration fee.
• A production-ready Android App Bundle (AAB) containing your TWA wrapper configuration, including your correct web app launch URL, theme colours, and package name.
• A verified Digital Asset Links association between your production domain and your app signing key, ensuring the URL bar is completely hidden upon installation.
• A complete Store Listing with promotional graphics, description text, screenshots for various screen sizes, and a privacy policy.

Step-by-Step Configuration in Google Play Console

To begin the pre-registration setup, log into your Google Play Console and select your application. Follow these structured steps:

1. Complete the Initial App Setup Tasks

Google Play requires you to complete a series of mandatory declaration forms before you can release any build. This includes declaring content ratings, target audiences, news app status, data safety practices, and financial or health features. You must complete all of these declarations within the App Setup section of the console dashboard.

2. Upload Your AAB to the Release Track

Navigate to Release on the left menu, and click on Testing or Production. To run a pre-registration campaign, you must upload your signed TWA AEP or AAB file to the Production track. Creating a release in the production track is required because Google Play needs to review and approve the actual binary that users will receive when the app launches.

Ensure you select your signing key carefully during this step, as your Digital Asset Links SHA-256 fingerprint must match the certificate used by Google Play App Signing.

3. Configure Countries and Regions

Once your binary is uploaded, navigate to the Pre-registration tab under the Release section. Here, you must select the specific countries and regions where you want to offer pre-registration. You can choose to run pre-registration globally, or limit it to specific geographic markets where your SaaS or service operates.

4. Submit Your Release for Review

After selecting your regions and linking your production-ready TWA bundle, click on Review and Start Rollout for Pre-registration. Your app listing, metadata, and the AAB itself will enter Google's review queue. This review process typically takes a few days, during which Google checks your app against standard policies, content ratings, and platform requirements.

Comparing Pre-Registration vs Direct Production Rollout

The following table outlines the key operational differences between launching your TWA app directly and running a pre-registration campaign first:

Technical Best Practices During the Campaign

While your TWA app is sitting in the pre-registration phase, your work is not complete. Because the wrapper points directly to your web server, any updates you make to your web application will immediately affect users on launch day. Keep the following technical points in mind:

First, maintain absolute domain stability. Since the AAB points to a hardcoded URL, any breaking changes to your domain pathing, routing, or SSL configurations will prevent pre-registered users from loading the application when it auto-installs.

Second, implement robust service worker caching. When thousands of pre-registered users receive the automatic download on launch day, their devices will open your application and hit your server to fetch assets. A highly optimized service worker utilizing cache-first strategies for static assets ensures your web server handles the sudden influx of initial traffic without degradation.

Third, verify Digital Asset Links compatibility. Use online verification tools to double-check that your server's assetlinks.json file matches both your local development keys and the official Google Play App Signing certificate. If there is a mismatch, your newly installed users will see an address bar at the top of their app on launch day, creating a poor initial user experience.

Transitioning from Pre-Registration to Live Production

Once your pre-registration campaign has reached its target audience or the 90-day limit approaches, you can transition your app to live production. In the Google Play Console, go to the Release overview page, locate your active pre-registration release, and click on Release to Production. After a short replication delay, Google Play will notify pre-registered users and begin silently installing the app over Wi-Fi, converting your early marketing efforts into active mobile users.