Google Play pre-registration: a pre-launch timeline
Short answer: Google Play pre-registration publishes your store listing before launch so people can sign up; when you release, they get a notification and eligible devices install the app automatically. A campaign can run for up to 90 days, and Google suggests switching it on three to six weeks before launch. Prepare the store listing, a tested build and your content declarations first, and decide early about a reward, because it can't be changed once the campaign starts. On iPhone, the equivalent is an App Store pre-order.
Pre-registration turns your marketing before launch into a list of people who will receive your app on day one. It's mostly paperwork and timing, which makes it easy to leave too late. Here's a timeline working back from launch day, based on Google's Play Console Help article on pre-registration.
T-60 days: check you can use it
A few requirements come before anything else:
- Testing first. Google strongly recommends rolling out a release to a test track and testing before starting pre-registration. Developers with personal accounts created after November 13, 2023, must meet specific testing requirements before they can publish, and therefore before they can use pre-registration.
- Content information. You can't use pre-registration until you've provided information about your app's content as part of preparing for review.
- Two at a time. A developer can have up to two apps or games available for pre-registration at once.
- A 90-day limit. The campaign can last only 90 days, after which the app has to launch to production. Count back from a realistic launch date, not a hopeful one.
If your launch date is still moving, hold off. Starting too early burns the 90 days.
T-45 days: build the store listing
Pre-registration means your listing is public before the app is. Google recommends a complete listing with graphic assets and translations before you start, as it can make pre-registered users more likely to install.
For a Canadian launch, that often means English and French listings, plus screenshots that show the real app, not mock-ups you'll replace later.
Google's pre-registration business page also suggests creating a custom store listing during pre-registration, so you can tailor what pre-launch visitors see.
T-40 days: decide on auto install
If your app is eligible for auto install, Play can deliver it to the devices of users who opted in on launch day. Google lists what makes an app eligible:
- Declare whether your app contains ads.
- If the app offers one-time products, the app bundle on your pre-registration track must include the billing permission in its manifest.
There are user and size conditions too. The Help article states that users need an Android M+ device and Play Store version 19.2 or later. Apps up to 200 MB can auto install over Wi-Fi or mobile data, apps between 200 MB and 2 GB only on Wi-Fi, and apps over 2 GB not at all. Accounts of children under 13 and managed enterprise accounts can't auto install. Ineligible devices still get the launch notification.
If your launch build will be large, it's worth knowing which group you're in.
T-35 days: decide on a reward (or not)
A pre-registration reward gives users a free one-time product, such as an in-game item or a feature unlock, after they pre-register. Google's rules are strict:
- One reward for the lifetime of the campaign, and it can't be edited or deleted after creation.
- It must be set up before the campaign starts and can't be switched on or off while it's active.
- It has to be a new, active one-time product created specifically for the reward, not a subscription.
- Your app must handle delivering it, similar to promotions, and tell users about it in the app.
- Google warns that failing to deliver rewards may lead to your app being suspended.
You can test delivery by generating and redeeming a promo code for the reward product. If your app has no in-app products, skip rewards; pre-registration works without them.
T-30 days: set devices and countries
In Play Console, under Test and release > Pre-registration:
- Supported devices: upload app bundles. Google uses the manifest to decide which devices can pre-register; these bundles aren't released to users.
- Countries/regions: choose where users can pre-register. These are the countries where the user is registered on Google Play, not where they physically are. You can add countries later, and the 90-day window for each country starts when you first open it.
- Rewards: choose a reward or select no reward, and save.
T-28 to T-21 days: start and promote
Start pre-registration, in line with Google's suggested three to six weeks before launch. Your listing lives at the standard Play URL for your package name, and Google provides an official pre-registration badge for your website.
Promote it where your audience already is: your website, email list, social accounts, partner newsletters. A hypothetical timeline for a Toronto fitness app might use launch-countdown emails each week, a short demo video, and the badge on the homepage hero.
The iOS side: App Store pre-orders
Apple's pre-order page describes a similar feature. You configure it in App Store Connect under Pricing and Availability, with an expected release date and regions. For brand-new apps, the release date can be 2 to 180 days after the pre-order is published, and the pre-order can be published once the app has been reviewed by App Review. On release day, the app downloads automatically onto pre-ordering devices.
Apple adds an important caution: people who pre-order aren't notified by Apple if the date changes or the pre-order is removed, so you need to tell them yourself. Avoid putting the date in marketing if it might move.
T-7 days: final checks
- Production build tested on a range of devices
- Store listing final, in every language you support
- Reward delivery tested, if used
- Launch announcement, emails and social posts scheduled
- Support inbox and FAQ ready for day-one questions
Launch day
Publish to production in your pre-registration countries. Pre-registered users receive a push notification, and eligible devices auto install. Google notes that users who already have a test version installed won't receive the notification, so tell your testers separately. Update your website badge to the normal "Get it on Google Play" badge and your iOS badge from pre-order to download.
FAQ
Can I extend the 90 days?
The Help article says campaigns last only 90 days and then you need to launch. Plan your start date so the window covers your launch with room to spare.
Do pre-registered users have to install?
No. They get a notification, and eligible users who opted in get an automatic install. They can still remove the app.
Is pre-registration only for games?
No. Google's documentation covers both apps and games.
Do I need both pre-registration and pre-orders?
If you launch on Android and iPhone together, yes: each store has its own version, configured separately.
Planning the weeks before an app launch across both stores is fiddly, so walk us through your launch date and we'll map the steps.