Finishing the build is not the same as being in the store. First-time publishers are often surprised by how much preparation the App Store and Google Play expect: developer accounts in the right name, privacy disclosures, test access for reviewers, listing assets and, for some new Google Play accounts, a testing period before production access.
This app store submission checklist collects what to prepare, with links to Apple’s and Google’s own pages for the rules that matter. Store policies change, so treat the linked official pages as the final word and check them again before you submit.
Start early: developer accounts
Store accounts take time to set up and verify, so create them while the app is still being built. Wherever practical, the accounts should belong to your organisation, not to your developer, so you keep control of the app after handover.
| Item | Apple App Store | Google Play |
|---|---|---|
| Developer account | Apple Developer Program membership | Google Play Console developer account |
| Fee (per official pages) | 99 USD, or local currency where available, per membership year | US$25 one-time registration fee |
| Account types | Individual or organisation | Personal or organisation |
| Extra steps for new accounts | Identity and organisation verification | Identity verification; new personal accounts also face testing requirements (below) |
| Official source | Apple: Choosing a membership | Google: Get started with Play Console |
Apple notes that some nonprofit, educational and government organisations may be eligible for a fee waiver. Google states that the registration fee is not refunded if the identity information provided is judged invalid, so enter details exactly as they appear on your documents.
The Google Play testing requirement for new personal accounts
This catches many first-time publishers. According to Google’s help page on app testing requirements, personal developer accounts created after 13 November 2023 must run a closed test before they can apply for production access. At least 12 testers must be opted in, and they must have been opted in continuously for the preceding 14 days. Google says review of the production access application usually takes seven days or less, but can take longer.
- Check whether your account is a personal account created after 13 November 2023.
- If it is, recruit at least 12 real testers well before your planned launch date.
- Set up a closed testing track and keep testers opted in for the full 14 consecutive days.
- Collect and act on tester feedback; Google may ask for more testing if engagement is too low.
- Build the testing period and review time into your launch plan.
Organisation accounts follow different rules, which is one more reason to set up the account under your business where you can.
Privacy and data disclosures
Both stores ask you to describe how your app handles user data, and reviewers compare what you declare with what the app actually does.
- A privacy policy, published at a stable URL, that matches the app’s real data practices.
- Apple’s App Privacy details completed in App Store Connect.
- Google Play’s Data safety form completed in Play Console.
- A list of every SDK in the app (analytics, crash reporting, ads, payments) and what data each collects.
- Permission requests (camera, location, contacts, notifications) that are needed, explained in plain language and requested at the right moment.
Your privacy disclosures must describe what the app really does, including its third-party SDKs.
— VSN Editorial
Account deletion
If users can create an account in your app, both stores expect them to be able to delete it.
Apple’s guidance on offering account deletion in your app says apps that support account creation must let users start deletion from within the app. Only offering to deactivate the account is not enough, and users should not have to phone or email support unless the app is in a regulated industry that qualifies for an exception.
Google Play’s account deletion requirements ask for an in-app path to delete the account and associated data, plus a web link where users can request deletion without reinstalling the app. You also answer deletion questions in the Data safety form.
- An easy-to-find “Delete account” option, usually in account settings.
- A web page where users can request deletion, referencing the app name as shown in the store.
- A clear message about any data you must keep for legal, security or fraud-prevention reasons.
- Instructions for users with active subscriptions about billing and cancellation.
Review preparation
Reviewers need to be able to use your app. Many rejections come from simple gaps.
- A demo account with sample data if the app requires sign-in, with credentials in the review notes.
- Notes explaining any feature that is not obvious, such as hardware requirements or region-specific content.
- No placeholder content, broken links or unfinished screens.
- Working support contact details.
- Payments for digital goods and subscriptions checked against each store’s current billing rules for your app type and regions.
Read Apple’s App Review Guidelines and the Google Play Developer Policy Center for the full rules. Both are long, but the sections relevant to your app type are worth reading in full.
Store listing assets
- App name and subtitle or short description within each store’s limits.
- Full description written for people, not keyword lists.
- Screenshots for the required device sizes, showing real screens.
- App icon in the required formats.
- Category, age rating questionnaire and content declarations.
- Release notes for the first version.
When to do what
Store preparation is easiest when it runs alongside development rather than after it. A simple sequence:
- At the start of the build: create developer accounts in your organisation’s name and start verification.
- While features are being built: list every SDK and data flow, draft the privacy policy and decide on account deletion.
- Once the core journey works: start internal and closed testing, and recruit testers if your Google Play account needs the 14-day closed test.
- Before submission: finish listing assets, complete the App Privacy and Data safety forms, and prepare the reviewer demo account.
- After submission: monitor review messages and keep the team available to respond quickly.
Final technical checks
- Release builds signed and versioned correctly, using the toolchain versions each store currently requires.
- Crash reporting and analytics configured, and disclosed in privacy forms.
- Tested on the agreed devices, OS versions and network conditions.
- Backend, APIs and admin tools running in production, not test mode.
- Push notification, deep link and payment configurations switched to production settings.
If you are still planning the app, factor store requirements into the budget early; our guide to app development cost factors covers release and ongoing costs. For a reality check on launch expectations, see mobile app development myths.
Key takeaways
- Create developer accounts early, in your organisation’s name.
- New personal Google Play accounts need a 14-day closed test with at least 12 testers before production access.
- Privacy policy, App Privacy details and the Data safety form must match the app’s real behaviour, including SDKs.
- Apps with account creation must offer account deletion; deactivation alone is not enough for Apple.
- Give reviewers a working demo account and clear notes; approval is always the store’s decision.
App store submission checklist: common questions
How long does App Store or Google Play review take?
Review times vary. For new personal Google Play accounts, the production access application after closed testing usually takes seven days or less according to Google, and the app review itself follows. Build buffer time into your launch plan.
Can my developer publish the app under their own account?
They can, but it makes you dependent on them. Publishing under your organisation’s account keeps ownership, reviews and download history with your business.
Do I need a privacy policy if my app does not collect personal data?
Both stores expect a privacy policy link. Many apps also collect data indirectly through SDKs such as analytics or crash reporting, so review those before declaring that nothing is collected.
What happens if my app is rejected?
The store explains the reason. Fix the issue or reply with clarification in the review system, then resubmit. Approval decisions remain with Apple and Google.
VSN prepares release builds, store metadata and submission steps when you provide eligible developer accounts, disclosures and content, while approval stays with Apple and Google. See our mobile app development service or ask about your release.
Filed under Software



