Google Play Pre-Registration for a New App

Two Stops is a puzzle you can finish on a train: a small board, one rule, a clear end before the next station. You want riders to pre-register so the phone is ready on launch morning. That is a store-listing campaign, not a private beta. Closed testing is how a new personal Play account proves the build with opted-in testers. Pre-registration is how strangers on Google Play raise their hand before the game is published.

Play’s pre-registration article is the source for the limits below. The App Store version of “order it now, download it later” is a different console and a different day range. If you ship both, read the App Store pre-order guide separately. Do not copy a 180-day Apple date into Play.

Pre-registration and closed testing do different jobs

Closed testing shares a build with people you choose, by email list or Google Group, so you can fix the puzzle before the public sees it. Pre-registration does not replace that. Play says it strongly recommends a test-track release before you start pre-registration. For a personal developer account created after November 13, 2023, the requirement is firmer: production and pre-registration stay disabled until you meet the closed-test rules and apply for production access. The closed testing guide is that gate. Two Stops can be in a closed test with a dozen commuters while the store listing is still private to them. Pre-registration is the later moment when the listing is something anyone in the countries you picked can open and join. Testers who already have a test build installed will not get the launch push. Plan on telling them yourself.

The campaign is 90 days, then you launch

A pre-registration campaign can last 90 days. After that you need to launch the app to production. You can have up to two apps or games in pre-registration at a time. The 90-day clock for a country starts the first time you make pre-registration available there. Adding a country later starts that country’s window then. It does not extend the countries you already opened.

You cannot start pre-registration without the content declarations Play uses for policy and legal checks. Set them close to the production version. Play says that is what makes auto-install and the launch notification reliable. Redesigning the puzzle during the 90 days means the listing already showed a different game.

What riders see, and what happens on launch day

Closed testing distributes a build to a list you control. Pre-registration collects interest on the public listing and can notify those people when you publish.

On launch day, pre-registered users get a Play notification to install. Auto-install is narrower: Android M or newer, Play Store 19.2 or newer, and not a child account under 13 or a managed enterprise account. Apps at or under 200MB can auto-install on Wi-Fi or cellular. Above 200MB and at or under 2GB, auto-install waits for Wi-Fi. Above 2GB, it is unavailable. Other devices still get the notification, and Play retries when they qualify. Some places restrict auto-install until adult status was verified in the past year.

Countries, and a listing aimed at pre-registration

Countries are where the user is registered on Google Play, not where the train is. Add them under Test and release, Pre-registration, Countries/regions. You can add more after the campaign starts, with a fresh 90-day window for each new country. Do not add a country whose language you have not put on the listing if the puzzle’s rules are only in English. The listing URL, once pre-registration is on, is the usual Play details URL for your package name.

Custom store listings can target “users who can pre-register for your app.” That is the right place for commute-specific screenshots if your main listing is more general, or the other way around. The targeting option is documented on Play’s custom store listing page . How to build that second listing is the custom store listings guide. The main listing still needs a feature graphic, screenshots, and a short description. Pre-registration does not excuse a thin page. Play says a complete, translated listing makes it more likely pre-registered users will install.

Rewards are optional and narrow

Play lets you offer one pre-registration reward for the life of the campaign. It has to be an active one-time product you create for this purpose, not a subscription and not an inactive product. You set it up before the campaign starts. After you create it, you cannot edit or delete it. You can switch rewards on or off, but not while the campaign is active. Users get the item after they tap Pre-register, not by typing a code. If you turn rewards on and then fail to deliver them, Play says that may get the app suspended.

Two Stops does not need a reward. A clear “finish a board between stations” listing is enough. If you do offer one, use a one-time product the game can actually grant, and say so in a way the listing can keep. Do not invent a second reward type, a discount code, or a subscription trial and call it a pre-registration reward. The help page does not describe those. The app has to handle the grant the way promotions work, including the case where developer payload and order id are absent, and it should tell the player they received it.

What the commute listing should show

AppGrowthKit can frame the board, the move, and the “you finished before the stop” screen from the real UI. Those three shots are what a rider sees on the pre-registration page. The feature graphic should be the board, readable small. A video is optional and should be one puzzle, not a cinematic of a train. Store listing experiments and featuring hopes are later. This week the job is a page you are willing to leave up for 90 days.

Featuring is still editorial and is not what this button does. The Play featuring guide explains that. The launch checklist covers the rest of the listing you should not redo here. When the 90 days are up, publish to production. The notification only helps if the game that installs is the puzzle they were shown.