Shipping an app is not finished when the code works on your phone. Apple and Google each have review processes, asset requirements, and policy rules that catch unprepared teams every week. This checklist covers what you need before hitting Submit.
Before you submit — product readiness
- App tested on multiple device sizes (small phone, large phone, tablet if supported)
- Crash-free sessions on TestFlight (iOS) and internal testing track (Android)
- Login flows work including password reset and edge cases
- Privacy policy URL live and linked inside the app
- Support contact email visible in app and store listing
- All placeholder text and lorem ipsum removed
Apple App Store requirements
Developer account
Enrol in the Apple Developer Program ($99/year). Organisation accounts need D-U-N-S verification — allow extra days.
Store listing assets
- App name (30 characters), subtitle, description, keywords
- App icon 1024×1024 without transparency or rounded corners
- Screenshots for required device sizes — 6.7" and 6.5" iPhone at minimum
- Privacy nutrition labels — declare data collection accurately
- Age rating questionnaire completed honestly
Common Apple rejection reasons
- Broken links or demo login credentials missing for reviewers
- Minimum functionality — apps that are mostly a website wrapper
- Guideline 4.3 spam — duplicate template apps
- In-app purchase rules violated — digital goods must use Apple IAP
- Privacy policy missing or data use not disclosed
Google Play requirements
Developer account
Google Play Console one-time $25 registration. New personal accounts face additional identity verification and may have longer review times for first apps.
Store listing assets
- Short and full description, feature graphic 1024×500
- App icon 512×512, phone screenshots (minimum 2)
- Content rating questionnaire (IARC)
- Data safety form — mirrors Apple's privacy disclosure
Common Google rejection reasons
- Permissions not justified — location, SMS, background access
- Misleading store listing vs actual app behaviour
- Broken functionality on review devices
- Missing privacy policy when collecting user data
Privacy and legal (both stores)
If your app collects email, location, analytics, or payment data, you need a privacy policy accessible from the app and the listing. GDPR and regional laws may require consent flows for EU users. Account deletion — Apple requires in-app account deletion for apps that support account creation.
Release strategy
Ship to TestFlight and Play internal testing first. Fix crashes from real devices, not simulators alone. Use phased release on Google Play and manual release on iOS until you are confident. Plan for review time: Apple often 24–48 hours; Google varies from hours to several days for new developers.
Need help getting to the store? I include submission support in full Flutter project engagements — [email protected].