Android App Launch Checklist: Artifacts, Access, Policy and Rollback
An Android launch checklist should make a release recoverable, not merely uploadable. The essential question is whether the team can identify the shipped.
Google Play & compliance
Play Store Readiness Checker
A complete pre-launch checklist before publishing to Google Play — store listing, policy, signing, testing, and release readiness, so nothing slips through.
Play Store Readiness Checker is part of APKLint, an online toolkit for inspecting Android APK files. A complete pre-launch checklist before publishing to Google Play — store listing, policy, signing, testing, and release readiness, so nothing slips through. Work through the checklist on this page — there is nothing to upload; it is a guided review.
- Final package settingsapplicationId, versionCode, and versionName are correct for launch.
- Release signingSigned with your upload key; Play App Signing enrolled.
- Not debuggableandroid:debuggable is false and logging is reduced in release.
- Target API OKMeets Google Play's current target-API requirement for your release track and form factor — verify the current threshold in Play Console.
- Shrink & obfuscateR8 minify and resource shrinking are on for release.
- Store listing completeTitle, short/full description, screenshots, and feature graphic are ready.
- App icon & brandingAdaptive icon set; no placeholder art.
- Privacy policy & Data SafetyPolicy URL set and Data Safety form completed accurately.
- Content ratingIARC questionnaire submitted; rating received.
- Permissions reviewedOnly necessary permissions; sensitive ones justified.
- Pricing & countriesDistribution countries, pricing, and device exclusions set.
- Pre-launch reportReviewed Play Console pre-launch crashes and warnings.
- Tested on real devicesCore flows verified across screen sizes and OS versions.
- Staged rollout readyStart at a small percentage and watch Vitals before 100%.
Free reference. No upload and no account needed — just open it and work through each point.
About Play Store Readiness Checker
A complete pre-launch checklist before publishing to Google Play — store listing, policy, signing, testing, and release readiness, so nothing slips through.
Play Store Readiness Checker is part of APKLint’s google play & compliance toolkit — Prep your listing, policies, and release for the store. It’s free to use and needs no account.
It’s a free reference — there’s nothing to upload and no account needed.
When to use Play Store Readiness Checker
- Best for
- A complete pre-launch pass before publishing to Google Play, store listing, policy, assets, and readiness together.
- Not the right tool for
- Not a code or binary tool; it is a publish-readiness checklist.
- What you get back
- A broad launch checklist spanning listing, policy, and technical readiness.
- How it differs from related APKLint tools
- It is wider than the Release Checklist, which focuses on the engineering build itself.
- Limitations
- A static checklist, last reviewed 22 September 2026; confirm current Play policy in the Console.
How to use Play Store Readiness Checker
- Open the checklist — Everything you need to review is laid out in plain language.
- Work through each item — Check your app against every point on the list.
- Fix what's flagged — Update your manifest, build, or listing where needed.
- Re-verify before release — Run through it once more before you publish.
Native code: 64-bit and 16 KB page-size support
If your app — or any SDK it bundles — ships native code (.so libraries), Google Play adds two requirements on top of the target-API rule. 64-bit support: every supported native architecture must comply with Google Play's 64-bit requirements — for example, provide an arm64-v8a library when you ship the corresponding ARM native code (you don't need to add ABIs you don't already build for). 16 KB memory page-size support: apps targeting Android 15 (API 35) and higher must support 16 KB page sizes on 64-bit devices, which means rebuilding the affected libraries 16 KB-aligned. Apps written purely in Java/Kotlin qualify by default. From February 1, 2027, updates that don't support 16 KB page sizes can't be released.
Form-factor deadlines are earlier: Android TV has required 64-bit + 16 KB since August 1, 2026, and Wear OS requires them from September 15, 2026 — these apply even though those form factors can still target a lower API level, so don't assume an API 34 TV app is exempt. Check the Play Console compatibility warnings and confirm the current deadlines before your next release.
Why use APKLint
Always free
Every tool is free with no login and no paywall. Reasonable file and input limits keep the free service stable.
No on-page ad banners
A clean, focused interface with no third-party ad banners cluttering your results.
Privacy-first
No upload and no account needed.
How it runs
No analysis engine — this is a browser-only checklist.
No sign-up
Start immediately — no account, login, or email required.
Works anywhere
Runs in any modern browser, on desktop or mobile.
Frequently asked questions
What does Play Store Readiness Checker do?
A complete pre-launch checklist before publishing to Google Play — store listing, policy, signing, testing, and release readiness, so nothing slips through.
Is it free to use?
Yes. Every tool on APKLint is completely free, with no sign-up and no account.
Do I need to upload anything?
No. This is a free reference checklist you work through in your browser — there's nothing to upload and no file is analyzed.
Does it cover the latest Google Play requirements?
This is a static reference guide, last reviewed 22 September 2026. Android and Google Play requirements change over time, so verify time-sensitive policy details in the Play Console before publishing.
Related tools
All product names, logos, and trademarks are property of their respective owners. APKLint is an independent toolset and is not affiliated with, endorsed by, or sponsored by Google, Android, or any other party.