Updated April 2026
Complete Checklist for Android App Submission to Google Play Store
Everything you need to successfully publish your Android application on the Google Play Store — from APK/AAB requirements and store listing to policies, testing, and post-launch steps. Use this interactive checklist to track your progress.
3.9B+Android devices worldwide
$25One-time dev registration
3–7 daysAverage review time
60+Checklist items below
Submitting an Android app to the Google Play Store is not just about uploading an APK. There are dozens of requirements across technical specs, store listing quality, content policies, and compliance — and missing even one can result in your app being rejected or removed after launch.
This comprehensive checklist — maintained by the team at MobileMerit.com — covers every step you need to complete before you hit “Publish.” You can click each checkbox below to track your own progress.
📋 Phase 1: Developer Account Setup
Before you can submit anything, you need a Google Play Developer account. This is a one-time setup that takes 24–48 hours to verify.
Account Prerequisites
5 itemsPay the $25 one-time developer registration feeRequired for all Google Play developer accounts
Critical
Verify your identity with GoogleGovernment-issued ID required for new accounts since 2023
Critical
Set up D-U-N-S number (for organisations)Required if registering as a company or organisation
High
Accept Google Play Developer Distribution AgreementRead and accept all terms before proceeding
Critical
Complete Play Console account detailsDeveloper name, email, website, phone number
High
⚙️ Phase 2: Technical Requirements (APK / AAB)
Google Play now requires Android App Bundles (.aab) for new apps. Your build must meet strict technical thresholds.
AAB is now mandatory for new apps
Since August 2021, all new apps on Google Play must be published as Android App Bundles (.aab) instead of APK files. Existing apps can still update via APK but AAB is strongly recommended.
Build & Package Requirements
10 itemsBuild and export as Android App Bundle (.aab)Use Android Studio → Build → Generate Signed Bundle/APK
Critical
Sign the APK/AAB with a production keystoreDebug keystores are NOT accepted on Play Store
Critical
Target Android 14 (API level 34) or higherGoogle Play requires new apps to target the latest API
Critical
Set minSdkVersion appropriately (≥ 21 recommended)Determines the minimum Android OS your app supports
High
Verify versionCode and versionName are correctversionCode must increment with every update
Critical
Ensure APK/AAB is under 200MB (compressed)Use Android App Bundle + Play Asset Delivery for larger apps
High
Enable ProGuard / R8 for release buildsMinifies and obfuscates code; reduces APK size
Medium
Remove all debug logs and test credentials from buildNo API keys, passwords, or tokens in production code
Critical
Request only necessary permissionsUnused permissions trigger policy violations and user distrust
High
Enrol in Google Play App SigningGoogle manages your app signing key — required for new apps
Critical
Quick Reference: Technical Specs at a Glance
| Requirement | Specification | Status |
|---|---|---|
| Package format | .aab (Android App Bundle) | Mandatory |
| Target SDK | API 34 (Android 14) or higher | Mandatory |
| Min SDK | API 21 (Android 5.0) recommended | Recommended |
| Max compressed size | 200 MB (base APK) | Mandatory |
| Build type | Release (signed) | Mandatory |
| 64-bit support | Required for all native code | Mandatory |
| App signing | Google Play App Signing enrolled | Mandatory |
| Adaptive icons | Recommended for Android 8.0+ | Recommended |
🖼️ Phase 3: Store Listing Assets
Your store listing is the first thing users see. Poor assets lead to low conversions — and incomplete assets will block submission entirely.
Graphics & Media Assets
8 itemsApp icon: 512×512 px, PNG, max 1024 KBMust not contain borders; no copyrighted elements
Critical
Feature graphic: 1024×500 px, JPG or PNG, max 1024 KBDisplayed at the top of your store listing on most devices
High
Minimum 2 screenshots per device typePhone: 16:9 or 9:16; Tablet: optional but recommended
Critical
Screenshots show actual in-app contentMockups and promotional text are not permitted as primary screenshots
High
Promo video (optional but recommended)YouTube URL only; 30 seconds to 2 minutes; avoid intro splash screens
Medium
All assets reviewed for trademark / copyright issuesNo brand logos (Google, Apple, etc.) in your artwork
Critical
No device frames in screenshots (per Google guidelines)Google discourages using device frames that may be misleading
Medium
Adaptive icon configured in res/mipmap-anydpi-v26Ensures your icon looks correct on all Android launchers
High
App Title, Description & Metadata
7 itemsApp title: max 30 characters, keyword-richYour primary SEO signal in Play Store search
Critical
Short description: max 80 charactersDisplayed in search results; include primary keyword
Critical
Full description: max 4000 characters, no keyword stuffingExplain features clearly; natural language only
Critical
Select the most appropriate categoryPrimary category directly affects discoverability
High
Add relevant tags (up to 5 allowed)Helps Google match your app to relevant user searches
Medium
Localize store listing for key marketsTranslated listings rank higher in non-English searches
Medium
Add “What’s new” release notes (for updates)Required for updates; helps with user communication
High
🔒 Phase 4: Privacy, Policies & Data Safety
Google’s policy requirements have grown significantly. The Data Safety section and privacy policy are now mandatory for all apps.
Policy violations are the #1 reason apps get rejected
Always re-read the Google Play Developer Policy Centre before submitting. Policies are updated frequently, often without advance notice.
Privacy & Data Safety
8 itemsCreate and host a publicly accessible Privacy PolicyMandatory for all apps; must cover all data collected
Critical
Complete the Data Safety form in Play ConsoleDisclose all data types collected, shared, and their purposes
Critical
Declare use of sensitive permissions accuratelyCamera, microphone, contacts, location, SMS/Call Log, etc.
Critical
Implement runtime permission requests (Android 6.0+)Request permissions only when needed, with rationale
High
Confirm app does not collect data from children without parental consentCOPPA / GDPR-K compliance if app targets under-13s
Critical
Add account deletion option if app has user accountsMandatory since December 2023 — must also delete server-side data
Critical
Ensure HTTPS / TLS for all network communicationNetwork security config must block plain HTTP in production
High
Review and comply with Families Policy (if applicable)Apps designed for children face stricter content and data rules
High
Content Rating & Compliance
5 itemsComplete the Content Rating questionnaire (IARC)Required for all apps; affects visibility in certain regions
Critical
Accurately describe all app content in the questionnaireMisleading ratings result in removal and account suspension
Critical
Declare app contains ads (if applicable)Required toggle in Play Console → App Content settings
High
Comply with financial services policy (if fintech app)Fintech apps face additional verification requirements
High
Review country/region availability for restricted contentSome content types are blocked in specific countries
Medium
🧪 Phase 5: Testing & Quality Assurance
Google now requires 20 testers and 14 days of closed testing before you can apply to go live (for new personal accounts).
New accounts must complete closed testing first
Since November 2023, new personal developer accounts must complete at least 14 days of closed testing with 20 opt-in testers before being eligible for production publishing. Organisation accounts are exempt.
Pre-Launch Testing
8 itemsRun Android Lint checks with zero critical errorsIn Android Studio: Analyze → Inspect Code
High
Test on multiple Android OS versions (8.0 to 14)Use Android Emulator or a real device farm
High
Test on multiple screen sizes (phone, tablet, foldable)Responsive UI prevents bad reviews from tablet users
Medium
Run Pre-Launch Report in Play ConsoleAutomated testing on Firebase Test Lab devices
High
Test all in-app purchases in test / sandbox modeUse Google Play Billing Library test environment
Critical
Complete closed testing with 20+ testers for 14+ days (new accounts)Mandatory prerequisite for personal accounts to access production
Critical
Conduct open beta testing if possibleCatching crashes before 1-star reviews is priceless
Medium
Verify deep links and App Links work correctlyUse adb shell and Digital Asset Links validator
Medium
💰 Phase 6: Monetisation Setup
In-App Purchases & Subscriptions
5 itemsUse Google Play Billing Library 6.x or higherOlder versions are deprecated and will be rejected
Critical
Set up products (in-app items/subscriptions) in Play ConsoleProducts must be “Active” before the app can go live
High
Provide a working test account for reviewers (if login required)Supply credentials in “Notes for reviewers” section
Critical
Set up your Google Play payment profile / bank detailsRequired to receive payouts from paid apps or purchases
High
Declare subscription pricing clearly in the store listingHidden pricing leads to chargebacks and policy violations
High
🚀 Phase 7: Final Submission Steps
Pre-Publish Final Checklist
7 itemsUpload your AAB to the production release trackPlay Console → Production → Create new release
Critical
Review the “Publish app” errors and warnings panelResolve all errors; warnings are optional but worth reviewing
Critical
Set rollout percentage for staged rollout (optional)Start at 10–20% to catch production crashes before full launch
Medium
Configure distribution countries and regionsInclude or exclude specific territories in the release settings
High
Add notes for reviewers (if special setup needed)Login credentials, feature flags, test flows — anything that helps the reviewer
High
Set up Android Vitals alerts and crash monitoringFirebase Crashlytics + Play Console vitals before launch
Medium
Click “Send for review” and await Google’s decisionTypically 3–7 days; new apps may take up to 2 weeks
Critical
❌ Top 10 Reasons Apps Get Rejected
Avoid these common pitfalls that slow down or block your submission.
| # | Rejection Reason | How to Fix | Severity |
|---|---|---|---|
| 1 | Incomplete Data Safety section | Fill in all data collection disclosures accurately | High |
| 2 | Missing or broken privacy policy link | Host on a public URL; ensure it’s not behind a login | High |
| 3 | Spam or misleading description | Remove repetitive keywords; be accurate about features | Medium |
| 4 | App crashes on launch | Run Pre-Launch Report; fix ANRs and crashes first | High |
| 5 | Targeting outdated API level | Update targetSdkVersion to API 34+ | High |
| 6 | Using deprecated Advertising ID without disclosure | Declare AD_ID permission and ad use in Data Safety | Medium |
| 7 | Intellectual property violations in screenshots/icon | Remove all third-party brand assets | High |
| 8 | Login-required app with no test credentials provided | Add test credentials in “Notes for reviewers” | Medium |
| 9 | Deceptive in-app purchase UI patterns | Clearly label all paid features and subscription terms | High |
| 10 | New account: not completed 14-day closed testing | Run a closed test with 20 testers for 14 days first | High |
📚 Official Resources & Useful Links
These are the most important official Google resources you should bookmark when submitting your app.
Google Play ConsoleSubmit and manage your apps
Play Policy CentreOfficial content policies (read before every release)
Target API Level RequirementsGoogle’s current SDK targeting requirements
Play Billing Library DocsImplement in-app purchases correctly
Data Safety Section HelpHow to fill in data safety accurately
Firebase CrashlyticsCatch crashes before users do
Android App Bundle GuideOfficial AAB documentation
MobileMerit.comExpert Android development & ASO services
❓ Frequently Asked Questions
The most common questions we receive about submitting Android apps to the Google Play Store.
How long does Google Play Store review take in 2026? +
For new apps, the review typically takes 3–7 business days. First-time submissions or apps with sensitive content (e.g., health, finance, VPN) may take up to 2 weeks. For updates to existing apps, the review is usually faster — often 24–72 hours. You’ll receive an email notification once the review is complete.
Do I need a privacy policy even if my app doesn’t collect user data? +
Yes. Google Play requires a privacy policy for all apps, regardless of whether you collect personal data. The policy must be hosted at a publicly accessible URL (not behind a login) and linked in both your store listing and within the app itself. Even if your app collects no data, your privacy policy should state that explicitly.
What’s the difference between APK and AAB? Which should I use? +
An APK (Android Package Kit) is the traditional installation format, containing all resources for all device configurations. An AAB (Android App Bundle) is a publishing format that lets Google generate optimised APKs for each device — resulting in smaller download sizes (typically 15–35% smaller). Since August 2021, all new apps on Google Play must be submitted as AAB. Existing app updates can still use APK but AAB is strongly recommended.
What happens if my app is rejected by Google Play? +
If rejected, you’ll receive an email explaining the specific policy violation or technical issue. You can fix the problem and resubmit — there’s no penalty for a first rejection. If you believe the rejection was made in error, you can appeal through the Play Console Policy Centre. Repeated violations, however, can lead to account suspension. Always read the rejection notice carefully and address every point raised.
Is the $25 Google Play developer fee a one-time payment? +
Yes. The $25 USD registration fee is a one-time payment per developer account. Once paid, you can publish unlimited apps on Google Play with no recurring account fee. Note that Google takes a 15% service fee on the first $1 million USD in earnings per year (30% thereafter) from paid apps and in-app purchases.
Why do new Google Play developer accounts need to do closed testing first? +
Google introduced this requirement in November 2023 to reduce spam and low-quality apps. New personal developer accounts must complete at least 14 days of closed testing with a minimum of 20 opt-in testers before they can publish to production. Organisation accounts (registered as a company with DUNS number) are exempt from this requirement. This policy does not apply to existing accounts that already have apps in production.
What is the Data Safety section and why is it required? +
The Data Safety section is a standardised form in Google Play Console where you disclose what data your app collects, how it’s used, whether it’s shared with third parties, and whether users can request deletion. It was made mandatory in 2022. Your declarations must be accurate and consistent with your actual app behaviour and privacy policy — discrepancies are treated as a policy violation. You can find guidance on filling it in on the official Play Help page.
Can I publish a free app and later make it paid? +
No. This is one of Google’s stricter rules: you cannot change a free app to a paid app. However, you can change a paid app to free at any time. If you want to monetise a currently-free app, the recommended approach is to add in-app purchases or subscriptions for premium features, or publish a separate paid version.