App Store and Google Play Submission Checklist for Android and iOS Apps.
A practical checklist of the accounts, documents, assets and testing you need ready before submitting your iOS or Android app for review.
Finishing the app is not the same as launching it. Many first releases are delayed by things that have nothing to do with code: a missing privacy policy, screenshots that don't match store requirements, or a review team that can't log in to test the app. This app launch checklist covers what to prepare before you submit to the Apple App Store and Google Play. Store rules change, so always confirm current requirements in Apple's and Google's official developer documentation.
1. Set up developer accounts under your own company
You'll need an Apple Developer Program membership and a Google Play Console account. Register them under your own business, not your development partner's, so that you own the listings, the reviews and the ability to move to another team later. Allow extra time: business verification can take longer than expected.
2. Prepare a privacy policy and your data disclosures
Both stores ask what data your app collects and why, including data collected by third-party SDKs such as analytics or ads. You'll need a public privacy policy URL and need to complete Apple's App Privacy details and Google Play's Data safety form accurately. Mismatches between what you declare and what the app actually does are a common reason for rejection.
3. Check sign-in, account and payment rules
If users can create an account, review the current store requirements around account creation and account deletion. If you sell digital goods or subscriptions, check the in-app purchase rules and how subscriptions must be described to users. These are the areas where stores are strictest, and fixing them after a rejection costs time.
4. Build your store listing assets
- App name, subtitle or short description, and full description
- Keywords (Apple) and category selection
- App icon and screenshots in each required device size
- An optional preview video
- Support URL and a working support email address
Use only assets you have the rights to. Don't include other companies' logos, trademarks, music, stock images or fonts unless your licence covers commercial app use. Original or properly licensed material avoids takedowns later.
5. Test on real devices and through the official test channels
Use TestFlight for iOS and the internal or closed testing tracks on Google Play so testers install the app the same way real users will. Test on a range of devices and operating-system versions, on poor connections, and with fresh installs as well as updates.
6. Prepare for the review team
- Provide a demo account if the app requires sign-in, and make sure it works
- Make sure your backend and any third-party services are live during review
- Explain any permissions the app asks for (location, camera, notifications) and make sure each has a clear reason
- Remove placeholder text, test data and “coming soon” screens
7. Plan the release, not just the submission
Review times vary, so avoid promising a fixed public launch date until the app is approved. Consider a staged or phased rollout, set up crash reporting and basic analytics before launch, and decide who monitors reviews and support email in the first weeks.
8. Have a plan for the first update
Real users will find issues your testers did not. Keep the build pipeline and signing credentials accessible to you, not only to your developers, and plan the first update soon after launch.
Android app submission checklist (Google Play)
Everything Google Play asks for before your first Android release:
- Play Console developer account, with identity verification complete
- New personal accounts: a closed test with the required number of testers for the required period, before you can apply for production access (check the current numbers in Play Console)
- Release built as a signed Android App Bundle (.aab), using Play App Signing
- Target API level that meets Google Play's current requirement
- Store listing: app name (up to 30 characters), short description (up to 80), full description, 512×512 icon, 1024×500 feature graphic and phone screenshots
- App content section: privacy policy, Data safety form, content rating questionnaire, target audience, ads declaration and app access instructions for reviewers
- Internal or closed testing track used to install and check the release before production
iOS app submission checklist (App Store)
And the equivalent list for Apple:
- Apple Developer Program membership and an App Store Connect record with the right bundle ID
- Build archived in Xcode, uploaded to App Store Connect and tested through TestFlight
- App Privacy details completed, and privacy manifests for your app and any third-party SDKs that need them
- If people can create an account, they can also delete it from inside the app
- Listing: app name and subtitle (up to 30 characters each), keywords (up to 100 characters), description, screenshots for each required device size, support URL and privacy policy URL
- Age rating questionnaire and export compliance (encryption) answers
- Review notes, plus a working demo account if the app needs sign-in
A short pre-submission summary
- Developer accounts under your company, with verification complete
- Privacy policy live and data disclosures filled in accurately
- Sign-in, account deletion and payment flows checked against store rules
- Listing text and screenshots finished, using only assets you have rights to
- Tested on real devices through TestFlight and Google Play testing tracks
- Demo account and reviewer notes ready
- Crash reporting and a support process in place
Common questions
A Google Play Console account with identity verification done, a signed Android App Bundle (.aab) that meets the current target API level, a complete store listing (icon, feature graphic, screenshots and descriptions), a privacy policy, and the Data safety, content rating, target audience and app access sections filled in. New personal accounts also need to finish a closed test before they can publish to production.
An Apple Developer Program membership, an App Store Connect record, a build uploaded from Xcode and tested in TestFlight, screenshots for the required device sizes, App Privacy details and privacy manifests, an age rating, a privacy policy and support URL, and review notes with a working demo account if the app needs sign-in.
Everything in the summary above: accounts under your company, privacy disclosures, store rules for sign-in and payments, finished listing assets, testing on real devices, reviewer notes, and crash reporting and support in place for launch day.
It varies. Many apps are reviewed within a few days, but first submissions and rejections take longer, so leave a buffer before any announced launch date.
Common causes are a demo account that doesn't work, privacy declarations that don't match what the app does, crashes or unfinished screens, misleading listing text or screenshots, and payment flows that don't follow store rules.
We help founders take mobile products from idea to store release. See our mobile app development services, browse the apps we have shipped, or get in touch about your launch.
Have a Project to Discuss?
We're happy to talk through your idea, even before you're ready to scope it fully.