Android release readiness checklist for Google Play in 2026

A release is ready when the exact artifact you intend to submit has been checked against the requirements that matter for that app. A successful compile is only one step.

1. Confirm the app identity

• Package/application ID matches the existing app if this is an update.
• The release is built from the intended source project and variant.

2. Confirm versioning

• versionName is correct for the release.
• versionCode is new and appropriate for the existing Play release history.

3. Check target and compile SDK

For standard phone/tablet submissions from August 31, 2026, new apps and updates need target API 36 or higher. Android’s Android 16 SDK guidance uses compileSdk 36 and targetSdk 36 for a normal Android 16 migration.

Check the current APK/AAB release metadata →

4. Review Android 16 behaviour changes

Test the changes relevant to your app. Depending on the project, this can include edge-to-edge UI, predictive back behaviour and large-screen behaviour.

5. Check native 16 KB compatibility

If native .so libraries are present, verify their alignment, packaging and runtime compatibility. The 16 KB requirement is separate from target API compliance.

6. Validate the final AAB/APK structure

• The artifact opens as a valid Android package/bundle.
• Expected manifest and resources are present.
• No unintended package or legacy files slipped into the release.

7. Verify signing/upload process

Use the correct release/upload signing process for the app. Do not treat a debug-signed local build as proof that the Play release artifact is correct.

8. Install and launch-test

For installable APK/device-derived testing, confirm the app installs, launches and shows the expected identity and resources. For an AAB, use the normal bundle/Play testing flow rather than trying to open the raw bundle as an app.

9. Regression-test important flows

• navigation and main screens;
• permissions;
• save/data flows if used;
• ads or billing if used;
• network behaviour;
• every feature touched by the migration.

10. Re-check the exact final artifact

Do not validate one build and upload another. Freeze the intended release artifact, record its checksum when possible and verify the package/version/API facts again immediately before submission.

11. Review Play-specific declarations

Technical readiness does not replace Google Play policy and disclosure requirements. Confirm the declarations relevant to the app’s permissions, data handling, ads, billing and content.

12. Keep a rollback baseline

Preserve the previous known-working source and artifact until the new release has passed the required checks. A migration should improve the project without destroying the last verified baseline.

Last verified: 17 August 2026

Official references

• Google Play target API requirements
• Set up the Android 16 SDK
• Android 16 behaviour changes
• 16 KB page-size support