App launch checklist: iOS and Android, step by step
A launch goes wrong in predictable places: a build nobody outside the team has tried, a privacy form filled in at the last minute, a Google Play account that cannot publish yet, or an update that reaches every user at once with a crash in it. This checklist walks through those steps in order, using only what Apple and Google publish themselves, as their pages read on 27 September 2026.
Launch tools side by side
From App Store Connect help, Apple’s TestFlight and pre-order pages, and Google Play Console help.
| Step | App Store | Google Play |
|---|---|---|
| Testing with your team | TestFlight, up to 100 internal testers | internal testing, up to 100 testers |
| Testing with outsiders | TestFlight, up to 10,000 external testers, invite by email or public link | closed testing or open testing |
| Required before first release | App Review of every new app and update | personal accounts created after 13 November 2023: a closed test with at least 12 testers for 14 days in a row |
| Privacy disclosure | app privacy details in App Store Connect, required for new apps and updates | Data safety section, required |
| Taking orders before launch | pre-order, release 2 to 180 days after the pre-order goes live for a new app | pre-registration, a campaign lasts up to 90 days |
| Releasing gradually | phased release of an update over 7 days, pause up to 30 days | staged rollout to a percentage of users, which you can halt |
1. Test with people outside the team
Both stores give you a testing lane before production. On iOS, TestFlight lets you add up to 100 internal testers from your team and invite up to 10,000 external testers by email or through a public link you can post anywhere. External testing needs a beta app description and beta review information first. On Android, Play Console has internal testing for up to 100 testers, closed testing for a group you control, and open testing that anyone can join from Google Play. Finding those first testers is itself a launch task: a public TestFlight link or an open test is something you can already share in communities and directories.
2. On Google Play, check whether you can publish yet
This catches many first-time Android launches. Google Play says developers with personal accounts created after 13 November 2023 must run a closed test with at least 12 testers who stay opted in for 14 days in a row before they can apply for production access in the Play Console dashboard. When you apply, you answer questions about the app, the testing and your readiness. Put those 14 days into your launch plan from the start, not the week before.
3. Fill in the privacy disclosures early
Apple requires app privacy details in App Store Connect to submit new apps and app updates, and they cover the practices of any third-party code in your app too, such as analytics or ad SDKs. Google Play requires the Data safety section, where you describe what data the app collects and shares and how it is protected. Both show on your store page before anyone installs, so treat them as part of the listing. Go through every SDK you ship before you start the form, not after.
4. Plan around review
Apple reviews every new app and update. Its own page says that on average, 90% of submissions are reviewed in less than 24 hours, and that incomplete submissions can take longer. If a release has to land on a fixed date for an event you are part of, or you need to fix a critical bug, you can ask for an expedited review; if the app is rejected, you can appeal once per submission. Submit with complete review notes and a working demo account if the app needs a login, and leave yourself slack before any date you announce. Check the build requirements first: uploads must be built with Xcode 26 and the iOS 26 SDK, and the first In-App Purchase of each type goes to review with an app version.
5. Take sign-ups before launch day
You do not have to launch cold. On the App Store, a pre-order lets people order the app before release; it downloads onto their devices on release day and they get a notification. For a brand-new app the release date can be 2 to 180 days after the pre-order goes live. On Google Play, pre-registration does a similar job: a campaign can last up to 90 days, after which the app has to launch to production, and you can run it for up to two apps at a time. Google recommends testing on a track before switching pre-registration on, and for new personal accounts the testing requirement above still applies.
6. Release updates in stages
The first version goes out to everyone, but the updates after it do not have to. Apple’s phased release spreads an automatic update over 7 days, from 1% of users on the first day to 100% on the seventh, and you can pause it for up to 30 days; anyone can still update by hand from the App Store. Google Play’s staged rollout sends an update to the percentage of users you choose, optionally in chosen countries, and you can halt it and resume it later for the same group. If a crash shows up, a small share of users sees it instead of all of them.
7. Have the store page and the web ready
Launch traffic lands on your store page, so the name, subtitle, screenshots and description should be final before release day. Our ASO checklist covers every field limit and the rules that get a listing rejected. Outside the stores, list the app where makers and early adopters look for new apps; our checked list of free app promotion sites shows which directories give a followed link. For how attention is spread across app categories, see the indie app landscape study.
Where Censuus fits
Censuus ranks apps by the visits they draw and by sponsorship. Adding your app is free on the List my app form, and from then on it can rise on the visits it earns. Sponsorship raises placement and adds a followed link to your website; the details are on the sponsor page. We do not promise downloads or rankings in the stores.
Frequently asked questions
How many testers do I need to publish on Google Play?
If your personal developer account was created after 13 November 2023, Google Play requires a closed test with at least 12 testers who stay opted in for 14 days in a row before you can apply for production access.
How long does App Store review take?
Apple says that on average 90% of submissions are reviewed in less than 24 hours. Incomplete submissions can take longer, and you can request an expedited review for a critical bug fix or a date tied to an event.
Can people sign up for my app before it launches?
Yes. The App Store offers pre-orders, with a release 2 to 180 days after the pre-order goes live for a new app. Google Play offers pre-registration campaigns of up to 90 days.
How do I release an update to only some users first?
Use phased release on the App Store, which spreads an automatic update over 7 days and can be paused, or a staged rollout on Google Play, which goes to a percentage of users you choose and can be halted.
Guides for app developers
- Google Play’s 12 testers for 14 days rule, explained
- How to find beta testers for your app
- App Store phased release and Google Play staged rollouts
- How to market an app: a stage-by-stage plan
- App store optimization checklist: what Apple and Google actually say
- How to promote an app on Google Play with Play Console’s own tools
Put your app in the ranking
Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.