A failed launch is expensive: bad first reviews, crashes on popular devices or a rejection from the App Store on launch day. Most of these problems are avoidable with a checklist. Here's ours.
Product and quality
- Core user journey works end to end on real devices: sign-up, main task, payment, logout.
- Tested on a range of devices: older and newer iPhones, several Android brands and screen sizes.
- Tested on slow and offline connections.
- Crash reporting installed and checked.
- Performance checked: launch time, smooth scrolling, battery use.
- Accessibility basics: dynamic text sizes, screen reader labels, contrast. See WCAG 2.2 checklist.
- Dark mode supported or deliberately handled. Read dark mode design.
- Beta test with real users through TestFlight (iOS) and testing tracks in Google Play.
- Onboarding gets users to a first win quickly. See onboarding UX.
- Error messages are helpful, and there's a way to contact support.
Accounts, legal and privacy
- Developer accounts in your company's name: Apple Developer Program and Google Play Console.
- Privacy policy published on a public URL.
- Terms of service if needed.
- App Store privacy labels and Google Play data safety form completed accurately.
- Permission prompts explained in plain language before the system prompt appears.
- Account deletion available in the app if users can create accounts (both stores require it).
- Tracking consent handled correctly (Apple's App Tracking Transparency where applicable).
- Age rating questionnaire completed honestly.
- Payments follow store rules for digital goods. See app store fees and external payments.
- AI features disclosed where relevant. See EU AI Act transparency.
Store listing (App Store Optimisation)
- App name clear and memorable, with a keyword if natural.
- Subtitle (iOS) and short description (Android) that say what the app does.
- Keywords field (iOS) filled with relevant terms.
- Full description benefit-led and scannable.
- Screenshots for required device sizes, showing benefits, not just screens.
- App preview video (optional but useful).
- App icon that's simple and recognisable at small sizes.
- Category chosen carefully.
- Support URL and marketing URL working.
- Localised listings for key markets.
Our app store optimisation guide goes deeper.
Analytics and operations
- Analytics events for key actions (sign-up, activation, purchase, retention).
- Attribution for marketing campaigns where needed.
- Backend monitoring and alerts for servers and APIs.
- Scalability checked for launch-day traffic spikes.
- Support process ready: who answers, how fast, where questions go.
Launch plan
- Submit for review at least a week early and use manual release to control the launch date.
- Website landing page with store badges, screenshots and a clear benefit. See landing page elements that convert.
- Email your list and partners; prepare social posts and a press note.
- In-app review prompt set to appear after a positive moment, not on first launch.
- Decide on a soft launch (one country or a limited audience) or full launch.
Common App Store and Google Play rejection reasons
Most rejections are avoidable. The usual culprits:
| Reason | How to avoid it |
|---|---|
| Crashes or broken features during review | Test the exact build you submit on real devices |
| Missing demo account for reviewers | Provide working login details in the review notes |
| Incomplete or inaccurate privacy information | Match privacy labels and data safety forms to what the app really collects |
| No in-app account deletion | Add it if users can create accounts |
| Digital goods sold outside store rules | Follow each store's payment rules for your region |
| Placeholder content or "coming soon" screens | Remove anything unfinished |
| Misleading metadata or screenshots | Show the real app and accurate claims |
| Minimal functionality (a website in a wrapper) | Offer genuine app features, not just a web view |
| Permission requests without clear purpose | Explain why each permission is needed |
If you are rejected, read the message carefully, fix the specific issue and reply through the review system. Rejections are routine and usually quick to resolve.
The first 30 days after launch
| Week | Focus |
|---|---|
| 1 | Watch crash reports and reviews daily; fix critical bugs fast |
| 2 | Check onboarding drop-off and activation; improve the weakest step |
| 3 | Test store listing changes (screenshots, subtitle) |
| 4 | Review retention (day 1, day 7) and plan the first improvement release |
Reply to reviews, especially negative ones, politely and with a fix where possible. Early responsiveness shapes your rating.
Common launch mistakes
- Launching without crash reporting.
- Testing only on the developers' own phones.
- Forgetting account deletion or privacy labels, leading to rejection.
- Setting a public launch date before approval.
- Asking for reviews on first launch.
- No plan for support questions.
- Accounts owned by a freelancer rather than the business.
After launch: plan for maintenance
New iOS and Android versions arrive every year, and stores keep updating requirements. Budget for ongoing work. See how much app maintenance costs.
The short version
Before launch, test the core journey on many real devices, set up crash reporting and analytics, complete privacy labels, permission explanations and account deletion, polish the store listing, submit early with manual release and prepare support. In the first month, watch crashes, reviews, onboarding and retention, and ship fixes quickly.
Launching an app? Our mobile app development team takes apps from idea to store and beyond. Still planning? Read how to plan a mobile app.




