Testing Tracks, Target API 36 and Releasing on Google Play

Android Development 11 min min read Updated: Nov 16, 2026 Intermediate
Testing Tracks, Target API 36 and Releasing on Google Play
Intermediate Topic 5 of 5

Testing Tracks

TrackWhoUse
Internal testingUp to 100 testers you listQuick checks, available within minutes
Closed testingInvited groups or email listsBeta feedback
Open testingAnyone can join from the storePublic beta
ProductionEveryoneFull release
New personal developer accounts: Google has had extra testing requirements for newly created personal accounts before they can go to production, such as running a closed test with a minimum number of testers for a number of days. These rules can change, so read the current Play Console Help before you plan your launch.

Target API Level

Google Play requires apps to target a recent Android API level. From August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher (Wear OS and Automotive have lower requirements). Existing apps that target below Android 15 (API 35) become hidden from new users on newer devices.

kotlin android { compileSdk = 36 defaultConfig { minSdk = 24 targetSdk = 36 // check developer.android.com/google/play/requirements/target-sdk each year } }

When you raise targetSdk, read the behavior changes page for that Android version and test your app. Typical changes affect permissions, background work, edge-to-edge display and 16 KB memory page size support for native code.

Pre-Release Checklist

  • Test the release build on at least two real devices and different Android versions
  • Check the Pre-launch report in Play Console (automatic tests on real devices)
  • Complete the Data safety form honestly, including SDKs
  • Provide a demo account if the app needs login (App access section)
  • Remove debug logs, test URLs and hard-coded secrets
  • Prepare screenshots, icon (512 x 512) and short and full descriptions

Common Policy Problems

ProblemHow to avoid it
Missing or wrong privacy policyUse a real policy that matches the app's behavior
Requesting unnecessary permissionsRequest only what a feature really needs
Misleading store listingScreenshots and text must match the real app
Crashes and ANRsTest on real devices, watch Android vitals
Using restricted permissions (SMS, call log, background location)Avoid them, or complete the declaration form with a strong reason

Staged Rollout

In the production release choose a percentage, for example 10 percent. Watch crashes and ratings, then increase to 100 percent. You can halt a rollout if you find a serious bug.

After Release

  • Monitor Android vitals: crash rate, ANR rate and startup time
  • Read and answer user reviews
  • Ship updates with a higher versionCode and release notes
  • Update targetSdk once a year
Start small: A polished, simple app is better than a huge unfinished one. Release, learn from users and improve.

Conclusion

Use internal and closed tracks to test, meet the target API level, follow the policy checklist and release in stages.

Quick Summary: Test through tracks, target API 36 for new apps and updates, complete data safety and roll out gradually.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators