Google Play Pre-Launch Checklist for Android Developers

Publishing an app on Google Play is not as simple as uploading an APK and clicking publish. There are technical requirements, policy requirements, and store listing requirements — and failing any one of them will result in a rejection or a delay. This checklist covers everything you need to verify before you apply for production access.

1. Complete the Closed Testing Requirement

This is the most commonly missed requirement for new apps. You need at least 12 testers to remain active in your closed testing track for 14 consecutive days. Do not apply for production access until this is complete — Google will reject your application immediately if the requirement is not met.

2. Verify Your Target API Level

Google Play requires new apps to target a recent Android API level. As of 2025, new apps must target Android 14 (API level 34) or higher. Apps that target older API levels will be rejected. Check yourbuild.gradle file and ensure targetSdkVersion is set to 34 or above.

3. Complete Your Store Listing

Your store listing must include a title (up to 30 characters), a short description (up to 80 characters), a full description (up to 4,000 characters), at least 2 screenshots for each supported screen size, a 512×512 px app icon, and a 1024×500 px feature graphic. Missing any of these will prevent you from publishing.

4. Set Up Your Content Rating

All apps must complete the IARC content rating questionnaire in Google Play Console. Navigate toPolicy → App content → Content rating and complete the questionnaire honestly. Misrepresenting your app's content can result in removal from the store.

5. Declare Your App's Data Safety

Google requires all apps to complete the Data Safety section, disclosing what data your app collects, how it is used, and whether it is shared with third parties. This must match your actual app behaviour and your privacy policy. Navigate to Policy → App content → Data safety.

6. Publish a Privacy Policy

If your app collects any personal data — including analytics, crash reports, or login information — you must link to a privacy policy in your store listing. The privacy policy must be hosted on a live URL (not a Google Doc or Notion page) and must accurately describe your data practices.

7. Test on Multiple Devices and API Levels

Before publishing, test your app on at least three different device configurations: a low-end device running your minimum supported API level, a mid-range device running a recent API level, and a tablet if your app supports larger screens. Use Android Studio's device emulator for coverage and a physical device for final validation.

8. Check Your App Signing Configuration

Google Play uses Play App Signing by default for new apps. If you are using Play App Signing, make sure you have downloaded and securely stored your upload key certificate. If you lose your upload key, you will need to contact Google support to reset it — a process that can take weeks.

9. Verify Your Billing Integration (If Applicable)

If your app uses in-app purchases or subscriptions, test every purchase flow in the sandbox environment before going live. Verify that purchases are acknowledged correctly — Google will refund any purchase that is not acknowledged within 3 days, which can cause revenue loss and user confusion.

10. Review Google Play's Developer Policies

Read through Google Play's current developer policies, paying particular attention to the sections on deceptive behaviour, impersonation, and restricted content. Policy violations are the most common reason for app rejection, and many violations are unintentional. Common issues include misleading screenshots, keyword stuffing in the app description, and using trademarked terms without permission.

11. Set Up Crash Reporting

Integrate Firebase Crashlytics or a similar crash reporting tool before launch. Google Play Console shows crash and ANR (Application Not Responding) rates, and apps with high crash rates may be demoted in search rankings. Having crash reporting in place from day one means you can respond to issues quickly after launch.

12. Prepare Your Launch Announcement

Have your launch announcement ready before you apply for production access. Google's review process typically takes 3–7 days for new apps, but can take longer. Prepare your social media posts, Product Hunt submission, and any press outreach in advance so you can publish them the moment your app goes live.