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
Android Release Checklist
Work through a practical pre-release checklist — versioning, signing, target SDK, permissions, listing — so nothing is missed before you ship an update.
Android Release Checklist is part of APKLint, an online toolkit for inspecting Android APK files. Work through a practical pre-release checklist — versioning, signing, target SDK, permissions, listing — so nothing is missed before you ship an update. Work through the checklist on this page — there is nothing to upload; it is a guided review.
- Version bumpedversionCode incremented and versionName updated.
- Changelog writtenRelease notes prepared for each supported language.
- Built from a tagged commitRelease is reproducible from version control.
- Release signing verifiedCorrect upload key; signature schemes v2/v3 present.
- Shrinking & obfuscation onR8 minify + resource shrink enabled for release.
- ProGuard/R8 mapping savedmapping.txt archived so you can de-obfuscate future crashes.
- Target API OKMeets the current Google Play per-form-factor target-API requirements, reviewed 22 September 2026.
- Regression testedCritical flows verified on a device matrix.
- Pre-launch report reviewedNo new crashes/warnings in Play Console.
- Backward compatibilityMigrations and saved data load correctly from the previous version.
- Crash reporting liveCrashlytics/your tool is wired and symbol files uploaded.
- Staged rollout plannedStart small and watch Vitals before full release.
- Rollback planYou can halt the rollout and ship a fix quickly if needed.
Free reference. No upload and no account needed — just open it and work through each point.
About Android Release Checklist
Work through a practical pre-release checklist — versioning, signing, target SDK, permissions, listing — so nothing is missed before you ship an update.
Android Release Checklist 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 Android Release Checklist
- Best for
- A practical pre-release pass, versioning, signing, target SDK, permissions, and more, before you ship.
- Not the right tool for
- Not a binary check; it is a checklist you work through.
- What you get back
- An ordered release checklist covering the build and store-readiness basics.
- How it differs from related APKLint tools
- It is the engineering-release list; the App Launch Checklist is the broader pre-publish (store + policy) list.
- Limitations
- A static checklist, last reviewed 22 September 2026; verify time-sensitive Play details in Play Console.
How to use Android Release Checklist
- 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 Android Release Checklist do?
Work through a practical pre-release checklist — versioning, signing, target SDK, permissions, listing — so nothing is missed before you ship an update.
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.