· 11 min read
App store launch checklist: Apple and Google Play
An app store launch checklist for Apple and Google Play: accounts, listing assets, privacy forms, review times and update release dates, with a PDF to print.
Updated

This app store launch checklist covers everything that has to be ready before an iPhone and Android app can go live, apart from the app itself. Most of it is paperwork, and most of it takes longer than founders expect. Developer accounts need verifying, store listings need assets, privacy forms need careful answers, and both stores review your app before anyone can download it.
Start these jobs in the first week of the build, not the last. Here is the list we work through on every mobile project. You can also download the checklist as a PDF to print or share with your team.
1. Developer accounts in your company's name
The single most important item. Your app should be published from your own company's accounts, not your agency's. Moving a live app between accounts later is possible but slow, and while it is in someone else's account, so are its reviews, its users and its payouts. Who owns the accounts is also one of the questions in our guide on how to choose an MVP development agency.
Apple. Enrol in the Apple Developer Program as an organisation. Apple asks for a legal entity, a D-U-N-S number, a work email on your company's domain, a public website on that domain, and an Account Holder with authority to sign agreements for the company. Membership is 99 USD a year, and Apple notes that prices may vary by region.
Google. Create a Play Console developer account, which carries a one-time registration fee of US$25. An organisation account also needs a D-U-N-S number, and Google warns that getting one can take up to 30 days. Personal accounts have an extra hurdle: those created after 13 November 2023 must run a closed test with at least 12 testers for 14 days in a row before applying for production access.
Once your accounts exist, invite your developers as users with the access they need. Do not hand over your own sign-in.
- D-U-N-S number requested or confirmed
- Apple Developer Program enrolment, as an organisation
- Google Play Console account, as an organisation
- Agency invited as users, not owners
2. Store listing assets
Each store has its own listing, with its own fields and image sizes. Gather these early, because the screenshots depend on finished screens and the text depends on decisions about positioning.
- App name, checked against existing apps in both stores
- Apple subtitle and keywords; Google short description
- Full description for each store
- App icon at the required sizes
- Screenshots for each device size the stores ask for
- Google Play feature graphic
- Optional preview video
- Category, and the age rating questionnaire in each store
- Support URL and contact email, monitored by a real person
Screenshots sell the app. Show the main job being done, with short captions, rather than a sign-in screen.
3. Privacy policy and data forms
Both stores require a privacy policy, and both ask you to describe your app's data practices in a structured form shown on the listing.
The privacy policy must be reachable from the store listing and, for Apple, from inside the app. Apple's App Review Guidelines say it must explain what data the app collects, how, and what it is used for, confirm that third parties receiving that data protect it equally, and explain how users can ask for their data to be deleted.
Apple's App Privacy details ask what data the app collects, whether it is linked to the user and whether it is used for tracking. This includes data collected by third-party SDKs, such as analytics and crash reporting tools, as Apple's App Privacy Details page explains.
Google's Data safety form covers similar ground and is required for nearly every app on Google Play, even one that collects no data at all, as set out in Google's Data safety guide.
- Privacy policy published on your own domain
- Linked in both listings and inside the app
- A list of every SDK in the app and what it collects
- Apple App Privacy answers completed
- Google Data safety form completed
- Account deletion inside the app, if users can create accounts (an Apple requirement)
Answer these forms carefully and keep them current. When you add an analytics tool later, the answers change too.
4. Testing tracks before the public launch
Both stores let you share a build with testers before release. Use them. Real phones on real networks find problems a simulator never will.
TestFlight on Apple lets you invite internal testers from your team and up to 10,000 external testers. The first build you share externally is reviewed by Apple first, as the TestFlight page notes, so allow for that.
Google Play offers internal, closed and open tests. An internal test can have up to 100 testers and is the quickest way to get a build onto your team's phones; closed and open tests reach wider groups. Google's guide to setting up a test explains each track. Our own Android apps, Zakat Calculator, Lead Diary and Headroom, are all in closed testing on Google Play.
- Internal testers set up in both stores
- A test plan for the main journey, on at least one older phone
- Closed test running, if you have a personal Google account
- Crash reporting and analytics checked in the test builds
5. Review information and review times
Reviewers need to be able to use your app. If it has a sign-in, Apple asks for a demo account and for your backend to be live during review. Add short notes explaining anything that is not obvious, such as a feature that only works in certain locations.
On timing, plan with a buffer. Apple says on its App Review page that it typically reviews at least half of submissions in under 24 hours and 90% in under 48 hours, and that incomplete submissions can be delayed. Google says that certain apps and developer accounts can face review times of up to seven days or longer in exceptional cases.
| Apple App Store | Google Play | |
|---|---|---|
| Typical review time | At least half of submissions in under 24 hours, 90% in under 48 hours | Updates to existing apps are published "as soon as possible" |
| The slow case | An incomplete submission can be delayed or fail review | Up to seven days or longer for certain apps and developer accounts |
| After approval | A version you release yourself can take up to 24 hours to appear | A change you publish is on Google Play within a few minutes |
For a first release, plan for the slow case in both stores. We allow a full week.
If the app does not pass. A rejection, even a minor one, adds another round. Apple lets you reply to App Review in App Store Connect and resolve the issue before you resubmit the build. If you think the decision is wrong, you can appeal to the App Review Board, with one appeal for each submission that did not pass. The checks above are there to prevent the avoidable ones: a demo account that does not work, a backend that is offline during review, or a privacy form that does not match the app.
- Demo account and reviewer notes ready
- Backend live and stable during review
- Submission at least a week before any date you have announced
- Time set aside to answer questions from either store
6. Launch day and the first weeks
- Release the approved build manually, so launch happens when you choose
- Open both live listings on a real phone and check the screenshots, text, price and links
- Watch crash reports and reviews daily for the first two weeks
- Reply to early reviews, especially the critical ones
- Keep version numbers and release notes tidy for the next update
7. App updates: choosing the launch date
The launch is the first release, not the last. Every update goes through review too, so an update that has to be live on a set day (a campaign, a price change, a seasonal feature) needs the same planning as the launch itself.
Approval and release are separate steps, if you set them up that way.
- Apple gives each version one of three release options: release it yourself, release it automatically after approval, or release it automatically after approval but no earlier than a date you choose. A version you release yourself waits as "Pending Developer Release" for as long as you like, and Apple sends a reminder if it sits there for more than 30 days.
- Google publishes approved changes automatically unless you turn on managed publishing, which holds them until you decide to publish.
With both set up, review can finish days early without anything going live.
Work back from the date. This is the plan we use for an update with a fixed day:
| When | What to do |
|---|---|
| 10 days before | Finish the build and test it on real phones through TestFlight and a Google Play test track |
| 7 days before | Submit to both stores, with a manual or dated release on Apple and managed publishing on Google |
| 7 to 2 days before | Answer reviewer questions the same day; fix and resubmit if a build does not pass |
| The day before | Both builds approved and waiting. Release on Apple now if you are releasing manually, since it can take up to 24 hours to appear |
| The day | Publish on Google Play, check both listings on a real phone, then announce |
If a feature must not be seen before the day, ship it switched off and turn it on from your server. The store release can then happen early, and the date no longer depends on either store.
Release gradually when there is no date. Both stores can send an update to a share of users first, so a bad release reaches fewer people.
- Apple's phased release spreads an update over seven days: 1%, 2%, 5%, 10%, 20%, 50% and then 100% of users who have automatic updates on. Anyone can still get the update by hand from the App Store, and you can pause the release for up to 30 days in total.
- Google's staged rollout goes to the percentage of users you choose. It does not grow by itself: you raise it over time, or halt it if something is wrong. Staged rollouts are for updates only, not for the first release of an app.
A gradual release is the wrong tool for a date, because on the first day of an Apple phased release only 1% of those users receive it. Use it for risky updates, and release to everyone when the day matters.
When a fix is urgent. Apple accepts requests for an expedited review in extenuating circumstances, such as a critical bug fix or a release tied to an event. For a bug fix, include the steps to reproduce the bug in the current version. Apple also says that if App Review finds other issues while reviewing a bug fix, you can resolve them in your next submission, as long as there are no legal or safety concerns.
- Release option chosen in App Store Connect: manual, or a date
- Managed publishing turned on in Play Console
- Update submitted a week before the date
- Date-critical features behind a switch on your server
- Phased release or staged rollout for risky updates with no fixed date
- Release notes written for each store
Questions founders ask
How long does app store review take?
Apple says it typically reviews at least half of submissions in under 24 hours and 90% in under 48 hours. Google publishes most updates quickly, but says certain apps and developer accounts can wait up to seven days or longer. For a first release, plan a week for each store.
Can I choose the exact day my app or update goes live?
Yes, in both stores. On Apple, choose to release the version yourself, or set a date it cannot be released before. On Google Play, turn on managed publishing so approved changes wait until you publish them. Submit about a week early, so review is finished before the day.
Do app updates go through review again?
Yes. Both stores review every new version, not only the first one. Google says updates to existing apps are processed as soon as possible, but an update that does not pass still costs a round, so keep the buffer.
Can I launch to a small group of users first?
For a first release, use the test tracks: TestFlight on Apple, and a closed or open test on Google Play. For updates, use Apple's phased release or a staged rollout on Google Play.
What happens if my app is rejected?
The store tells you why. On Apple you can reply to App Review, fix the issue and resubmit, or appeal if you think the decision is wrong. Each round adds review time, which is why the submission date matters more than the release date.
Using this app store launch checklist
Most of these steps need decisions or documents from your side, which is why they belong at the start of a project. We set up store accounts in the client's name in the first week, build the listings alongside the app, and run test builds well before launch. Our post on how long it takes to build an MVP shows where launch fits in the overall timeline. If you have not picked a framework yet, our comparison of React Native vs Flutter covers that choice, and we build with both: see React Native app development and Flutter app development.
You can read more about how we take apps from first sketch to both stores on our mobile app development page. The whole list is also a two-page PDF you can print. If your app is nearly ready and you are not sure what is missing, send us a note and we will go through this list with you.
- Mobile apps
- Launch
- App stores
Building a first version of your product?
We scope it in a week and launch it in 8–12, for a fixed price. Tell us what you want to build.
Keep reading

· 8 min read
How to build a doctor appointment app: lessons from DocRadar
Doctor appointment app development, from a Flutter app we built: real-time availability, doctors nearby on a map, in-app payments, roles and store review.
Read the guide
· 6 min read
React Native vs Flutter: which should your startup pick?
React Native vs Flutter for a startup's first app: hiring, performance, UI, packages, web reuse and when to go native, with real projects built on each.
Read the guide
· 6 min read
Web app or mobile app first: how founders decide
Web app or mobile app first? How to decide from where your users are, what the phone must do, how people find you, and when a PWA is enough to start.
Read the guide