What do you need to do before publishing a mobile app?
Before you publish, set up your Apple and Google developer accounts, test the final build on real devices, prepare the store listing with screenshots and a description, publish a privacy policy and complete each store's privacy and data forms, provide review access and demo credentials, and plan a staged rollout with monitoring. Check each store's current requirements, because they change.
1. Accounts and identity
- Enroll in the Apple Developer Program and set up App Store Connect.
- Create a Google Play Console account and complete its identity verification.
- Use organization accounts where possible, so the app is not tied to one person.
- Check Google Play's current testing requirements for new developer accounts before you plan your launch date.
2. Build and test
- Test the release build, not just the debug build, on real devices and different screen sizes.
- Use TestFlight for iOS and internal or closed testing tracks on Google Play.
- Check offline behavior, slow networks, permissions and interruptions such as calls.
- Fix crashes and performance problems before submitting.
3. Store listing
- App name, subtitle or short description, full description and keywords that describe what the app really does.
- A clear icon and screenshots that show the real app.
- A category, a contact email and a support page.
- A promotional video or preview, if you have one.
4. Privacy, policy and compliance
- Publish a privacy policy at a public URL.
- Complete Apple's App Privacy details and Google Play's Data safety form accurately.
- If people can create an account in the app, provide a way to delete the account from within the app.
- Explain why you request each permission, and request only what you need.
- Complete the content rating questionnaires.
5. Review readiness
- Give reviewers demo credentials and any steps needed to reach key features.
- Make sure every feature described in the listing works in the submitted build.
- Follow the store guidelines on payments, user-generated content and design.
- Allow time for review and for a possible rejection and resubmission.
Key takeaway: Most rejections come from broken flows, missing demo access, unclear permissions or a mismatch between the listing and the app. Test the review experience yourself.
6. Release and monitoring
- Use phased release on iOS and staged rollout on Google Play, so problems affect fewer people.
- Monitor crash reports, ratings and reviews from day one.
- Reply to reviews and fix reported problems quickly.
- Plan regular updates for fixes, OS changes and improvements.
Need help launching?
Our mobile app development team builds, tests and publishes iOS and Android apps. If you are still choosing a framework, read Flutter vs React Native, and for budgeting see mobile app development cost.
Frequently asked questions
How long does app review take?
It varies, from hours to several days, and can be longer for a first submission or after a rejection. Leave a buffer before any launch date.
Do I need a privacy policy?
Yes. Both stores expect a privacy policy at a public URL, and you must describe your data practices accurately in their forms.
Why do apps get rejected?
Common reasons are crashes, broken features, missing demo access, unclear permissions, misleading listings and guideline violations.
Should I release to everyone at once?
Usually not. A phased or staged rollout lets you catch problems with a small group first.
