A comprehensive, interactive pre-submission audit for Android developers. Verify store listing assets, App Bundle technical criteria, closed testing cohorts, Data Safety declarations, and rollout readiness before clicking submit.
This interactive readiness checklist evaluates your store listing assets, App Bundle technical configurations, Target SDK requirements, and Data Safety disclosures against published Google Play Developer Program policies. Completing all items here does not guarantee automated approval. Google evaluates app submissions using proprietary static scanners and human reviewers who review app runtime behavior, in-app purchases, and account credentials.
App title cannot exceed 30 characters. Avoid keyword stuffing, emojis, price claims ('Free', 'Best', 'Top'), or all-caps capitalization.
Short description (max 80 chars) highlighting primary utility. Full description (max 4,000 chars) accurately describing app features without keyword repetition.
Provide a 512x512 32-bit PNG with an alpha channel, up to 1MB. Must adhere to Google Play icon specifications with rounded squircle masking.
Banner displayed in search results and editorial placements. Keep key branding centered to prevent cutoff on varying mobile screen ratios.
Upload at least 4 screenshots (between 320px and 3840px, up to 8MB each). Showcase real in-app UI. Include tablet (7" & 10") screenshots if supporting tablets.
All new app submissions and updates must target API level 34 or higher in build.gradle (targetSdkVersion 34).
All new applications must be uploaded as an .aab rather than a standalone .apk. Enables dynamic asset delivery and smaller download footprints.
If your app contains C/C++ native code, arm64-v8a or x86_64 64-bit architectures must be provided alongside 32-bit variants.
Enroll in Google Play App Signing. Store your upload signing keystore securely in an encrypted vault or password manager.
Distribute an internal test build to your development team to verify build installation, crash reporting (Crashlytics), and deep-link flows.
For personal accounts created after Nov 13, 2023: maintain at least 20 active opted-in testers continuously for 14 full days without interruption.
Check Play Console > Pre-launch report. Verify 0 fatal exceptions, 0 strict mode violations, and no major UI overlap on tested physical device matrix.
Link a publicly accessible, permanent HTTPS privacy policy on a verified domain describing data collection, retention, and third-party SDK sharing.
Audit all third-party SDKs (AdMob, Firebase, Analytics, Facebook, Adjust). Ensure every data point collected or shared is declared in the Data Safety form.
If your app allows user account creation, you must provide a publicly accessible web URL where users can request account and associated data deletion.
Answer the International Age Rating Coalition questionnaire honestly regarding violence, crude humor, language, fear, gambling, and user interaction.
Accurately disclose whether your app includes paid digital goods, subscriptions, or randomized loot mechanics with clear odds disclosures.
Specify whether your app targets Children (< 13), Mixed Audience, or Adults (18+). If children are targeted, strict Designed for Families rules apply.
If targeting both children and adults, ask users for their age using a neutral date-of-birth or age selector that does not nudge them toward an adult age.
If any part of your app requires a login, OTP, or membership, provide active demo credentials in Play Console > App Content > App access without SMS 2FA.
If your app handles medical data, personal loans, VPN services, or government info, complete the required declaration forms with licensing proof.
Remove unnecessary permissions (`READ_MEDIA_IMAGES`, `ACCESS_BACKGROUND_LOCATION`, `READ_CONTACTS`). Only declare permissions core to the app experience.
Draft clear, descriptive release notes explaining new features or bug fixes. Avoid generic placeholders like 'Bug fixes and performance improvements'.
Release production builds using staged rollouts over 3–7 days to catch unexpected crashes or user regressions before 100% of your user base updates.
Ensure Sentry, Crashlytics, or Android Vitals alerts are configured to notify engineering if crash rates exceed the bad behavior threshold (1.09%).
Publishing an Android app to Google Play is no longer a simple file upload. Today, Play Console enforces intricate technical compliance rules, automated malware scanning, strict metadata character limits, and legal user privacy declarations.
A single oversight—such as omitting a test username in the App Access tab, or failing to declare an advertising identifier collected by AdMob—can result in rejection strikes, review delays of several weeks, or even account suspension. Working through this checklist systematically safeguards your release timeline.
Google automatically blocks any submission targeting older Android API versions. Ensure your build compiles with targetSdkVersion = 34 (Android 14) or newer.
If your app has login, subscription, or paywalled screens and you fail to provide working credentials under App Content > App access, reviewers will immediately reject for broken functionality.
Your Privacy Policy URL must be a live HTTPS page that loads without geo-blocking or login requirements. Broken links trigger automated policy takedowns.
Sensitive permissions like ACCESS_BACKGROUND_LOCATION, CAMERA, or READ_MEDIA_IMAGES must have prominent in-app disclosure dialogs before being requested.
Consult Google’s official developer documentation for the latest policy updates:
Initial submissions for new applications or newly created developer accounts typically take between 3 to 7 business days for full policy and automated security evaluation. In some cases involving sensitive permissions or high-risk categories (finance, health), reviews may extend up to 14 days.
The most frequent rejection triggers are: 1) Inaccurate Data Safety form declarations (omitting third-party SDK analytics or device IDs); 2) Missing or broken app access test credentials (preventing Google reviewers from testing login-gated features); and 3) Broken functionality or immediate crashes on physical review test devices.
Organization developer accounts can technically release directly to production, although internal and closed testing is strongly advised. Personal developer accounts registered after November 13, 2023 cannot publish directly to production until they complete a mandatory 14-day closed test with at least 20 opted-in testers.
A Staged Rollout releases your update to a percentage of users (e.g. 10%, then 20%, then 50%, then 100%) rather than all users at once. This prevents a critical undetected bug or crash regression from impacting your entire install base simultaneously, protecting your store rating.
If your app's manifest permits tablet screen sizes or if you check tablet distribution in Play Console, Google requires high-quality 7-inch and 10-inch screenshots to feature your app on tablet search results. If you only target phones, 4 phone screenshots satisfy the minimum store listing requirement.
This checklist is an independent developer self-audit utility. It cannot independently connect to your Play Console or guarantee that your build will be accepted by Google Play reviewers.
Always review your live submission warnings inside the Play Console Release Dashboard before initiating a production rollout.
Our Android publishing specialists perform comprehensive pre-submission audits, verify Target SDK compliance, test App Access credentials, and guide your App Bundle through Google review without delays.
Navigating closed testing cohorts, production questionnaires, or policy appeals? Our team provides structured assistance with verified tester networks and Play Console readiness audits.
