The Requirement
Google Play requires apps to target a recent Android API level. For 2026:
- New apps must target API level 36 (Android 16)
- App updates must target API level 36 within one year of Android 16's release
- Apps that do not meet the requirement cannot be published or updated on Google Play
This is part of Google's ongoing effort to ensure apps use the latest security, privacy, and performance features of the Android platform.
API Level Timeline
| Year | Required API Level | Android Version |
|---|---|---|
| 2023 | 33 | Android 13 |
| 2024 | 34 | Android 14 |
| 2025 | 35 | Android 15 |
| 2026 | 36 | Android 16 |
Google typically announces the deadline alongside the new Android release and gives developers several months to comply.
What Changes at API Level 36
Permissions and Privacy
Each new API level introduces stricter permission handling:
- Photo picker changes - New restrictions on broad media access
- Background activity restrictions - Tighter controls on background work
- Notification permissions - Continued evolution of the notification permission model
- Health Connect integration changes
- Credential Manager updates for passkey support
Security
- Updated encryption requirements for local data storage
- Network security config changes
- Package visibility restrictions continue to tighten
- PendingIntent mutability enforcement
Behavior Changes
API level 36 introduces behavior changes that affect all apps targeting it:
- Apps must handle edge-to-edge display
- Foreground service type declarations are strictly enforced
- Exact alarm permissions require explicit user consent
- Predictive back gesture support expectations
Migration Steps
Step 1: Update build.gradle
Change your target SDK version:
In your app-level build.gradle (or build.gradle.kts):
- Set targetSdkVersion (or targetSdk) to 36
- Optionally update compileSdkVersion to 36 as well
- Keep minSdkVersion at whatever your minimum supported version is
Step 2: Update Build Tools
- Update Android Gradle Plugin to the latest version
- Update Gradle wrapper to the required version
- Update Build Tools to the 36.x.x series
- Verify your Kotlin version is compatible
Step 3: Address Behavior Changes
Review the Android 16 behavior changes documentation and fix any incompatibilities:
- Test your app's foreground services
- Verify notification delivery
- Check file access patterns
- Test background work execution
Step 4: Update Dependencies
- Update AndroidX libraries to the latest stable versions
- Check third-party SDK compatibility with API level 36
- Update Google Play Services dependencies
- Run dependency resolution and resolve conflicts
Step 5: Test Thoroughly
- Test on Android 16 emulators and physical devices
- Test backward compatibility on your minimum supported Android version
- Run the pre-launch report in Google Play Console
- Use StrictMode to catch compatibility issues
Common Migration Issues
Foreground Service Types
Starting from API level 34, foreground services must declare a type. At API level 36, enforcement is stricter. Ensure every foreground service in your manifest declares an appropriate type:
- dataSync
- mediaPlayback
- location
- connectedDevice
- health
- remoteMessaging
- shortService
Permission Changes
New API levels often change how permissions work:
- Some previously automatic permissions now require explicit requests
- Runtime permission dialogs may behave differently
- "Do not ask again" behavior may change
Package Visibility
Apps targeting newer API levels can only see a limited set of installed packages by default. If your app needs to interact with other apps, declare the needed packages in your manifest using the queries element.
Staying Ahead
- Subscribe to Android Developer Blog for early announcements
- Join the Android beta program for early testing
- Update dependencies quarterly to avoid large migration jumps
- Use Android Lint to catch deprecated API usage early
- Maintain a CI pipeline that builds against the latest SDK
What If You Miss the Deadline?
If your app currently targets an older API level:
- Existing users keep the app and receive no disruption
- You cannot publish new apps or updates until you comply
- Users on newer Android versions may experience unexpected behavior
- Google may eventually hide non-compliant apps from search results