Key takeaways
- Set up your developer accounts early. Verification can take days and should not block your launch.
- Store listings, screenshots and privacy answers are part of the product. Prepare them while development is still running.
- Most rejections come from crashes, missing privacy information or broken sign-in flows, all of which are testable in advance.
- Launch to a small audience first, watch crash and review data, then widen the release.
Getting the app built is only part of the job. A smooth launch depends on a dozen small tasks that are easy to leave until the last day. This checklist gathers them in the order we usually work through them.
1. Accounts and ownership
- Create an Apple Developer account and a Google Play Console account under your organisation, so you own the app and its data.
- Complete identity or business verification early. It can take several days.
- Add team members with the right roles instead of sharing a single login.
2. Store listing assets
- App name, subtitle and a short, clear description that explains the main benefit.
- Screenshots for each required device size, showing real screens with short captions.
- An app icon that stays recognisable at small sizes.
- Support and privacy policy URLs that actually work.
- Keywords and category chosen on purpose.
Write the listing before launch week
Screenshots and copy take longer than expected. Drafting them during development keeps launch day calm.
3. Privacy and compliance
- Publish a privacy policy that matches what your app really collects.
- Complete Apple’s privacy details and Google’s data safety form accurately. Mismatches are a common cause of review problems.
- If the app handles health, financial or children’s data, confirm the extra requirements early.
- Provide a working demo account if the app requires sign-in, so reviewers can get past the login screen.
4. Testing before you submit
- Test on real devices, not only simulators, across a range of screen sizes and OS versions.
- Check every flow: sign-up, sign-in, payments, notifications and offline behaviour.
- Run performance and security checks and fix crashes first.
- Use TestFlight (iOS) and internal or closed testing tracks (Android) to give real people a pre-release build.
5. Submission and review
- Build the release version and upload it through App Store Connect and Play Console.
- Answer the review questions honestly and include notes explaining anything unusual.
- Expect a short wait, and keep a few days of buffer in case changes are requested.
| Common rejection reason | How to avoid it |
|---|---|
| Crashes or broken features | Test on real devices and fix before submitting |
| Missing or inaccurate privacy details | Match the forms to what the app collects |
| Reviewer cannot sign in | Provide a demo account and notes |
| Placeholder content or links | Replace dummy text and check every link |
6. Launch and after
Release in stages where the store allows it, starting with a small percentage of users. Watch crash reports, ratings and reviews closely in the first days, respond to feedback, and ship quick fixes. Then plan regular updates for OS changes and new features.
Published November 2, 2026.
