Mobile App DevelopmentDeveloperTechnical migration guide

Android Target API 36 Migration: Roadmap Before August 31, 2026

A technical migration checklist for native Android, React Native and Expo projects before the Google Play target API 36 requirement.

Published: July 23, 2026Updated: July 23, 2026InoviqLab

Audience: Developer
Content type: Technical migration guide
Source verification date: 2026-07-22
Verified version or policy: Google Play target API 36 policy and Android 16 behavior changes

AndroidAPI 36Google PlayReact NativeExpoMobile App

Short answer

Google Play Store policies mandate that Android app updates target recent Android API levels to maintain security, battery optimization, and user privacy standards.

Migrating your Android or cross-platform mobile application (React Native, Flutter, Expo) to **Target API level 36** requires updating build configurations, handling runtime permission changes, and verifying background task execution limits.

Android API Migration Steps:

Update Android SDK Build Configuration (`build.gradle`)

+ Audit Runtime Permissions & Background Service Policies + Test App Execution on Android 16 (API 36) Emulators + Submit Updated APK / AAB Bundle to Google Play Console =

Store Policy Compliance

Key Build Configuration (`android/app/build.gradle`):

android {
    compileSdkVersion 36
    defaultConfig {
        targetSdkVersion 36
        minSdkVersion 24
    }
}

Android Migration Checklist

[ ] Update `targetSdkVersion` and `compileSdkVersion` to 36 in `build.gradle`
[ ] Test runtime permissions for notification, photo picker, and location access
[ ] Verify foreground service and background worker behavior on Android 16

Sources

Android Developers — Target API Level Requirements for Google Play Apps
Android Developers — Android 16 Behavior Changes and API 36 Features

LinkedIn X