You can migrate an Android app to API 36 (Android 16) without dropping older Android versions: keep the app’s existing minSdkVersion unless you deliberately need to raise it, and treat Android 16 compatibility work and the API 36 targetSdkVersion change as separate stages. First test the current release on Android 16 and fix issues that affect apps there; then opt into API 36 behavior and test those changes independently.
Understand which SDK setting controls older-device support
minSdkVersion sets the lowest Android version on which the app is intended to install. targetSdkVersion tells Android which newer platform behaviors the app is prepared to handle. Raising the target to API 36 does not, by itself, raise the minimum OS version. Google Play’s guidance says apps targeting a recent API can still run on older Android versions; the actual supported range depends on the app’s minimum SDK, build configuration, and dependencies. See Google Play’s target API level requirements.
As an Amazon Associate I earn from qualifying purchases.
Keep the existing minimum SDK when the goal is only to migrate to API 36. Change it only as a separate product decision, after checking which users and devices would lose installation or update access. A successful build is not proof that every older supported OS still works: verify the app across the range it declares and the devices its users rely on.
Choose between a compatibility update and the API 36 target update
Android distinguishes changes that affect every app running on Android 16 from changes that turn on when an app targets API 36. Keeping those tracks separate makes regressions easier to identify and can let you ship Android 16 fixes before taking on target-gated changes. Android Developers’ “Migrate apps to Android 16,” last updated September 16, 2026, says you can usually publish an update for compatibility without changing the target SDK.
#1 Best Overall
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
| Track | Target SDK | What it addresses | Build changes | Release planning |
|---|---|---|---|---|
| Compatibility-only update | Keep the current targetSdkVersion. |
Issues that affect apps running on Android 16 regardless of target, including relevant platform and native-dependency compatibility. | Change compileSdkVersion or other build settings only if the app’s build or platform API use requires it. |
Useful for addressing Android 16 problems before opting into API 36 behavior. |
| API 36 target update | Set targetSdkVersion to 36. |
Compatibility work plus Android 16 behaviors gated on targeting API 36. | Set compileSdkVersion to 36 as needed to build against the APIs; check plugin, framework, and dependency requirements. |
Plan the additional behavior review and regression testing. Google Play’s current policy has target-level deadlines. |
These are migration tracks, not guarantees that every app can make no build changes in the first phase. Whether a compile SDK change is necessary depends on how the app is built and which platform APIs it uses.
Migrate in stages
- Record the baseline. Note the app’s
minSdkVersion,targetSdkVersion,compileSdkVersion, build tools, framework, native components, third-party SDKs, and declared device support. Save the current production build and test results as a comparison point. - Test the production-target build on Android 16. Install the current app on an Android 16 device or emulator and exercise its important flows: launch and sign-in, navigation, data entry, notifications, background work, permissions, and any app-specific functions. Review Android 16 changes that apply to all apps, without first raising the target SDK.
- Investigate platform and dependency failures. Review logcat for warnings about restricted non-SDK interfaces. Android recommends using
StrictMode.detectNonSdkApiUsage()to identify this usage. Exercise native code and third-party SDKs on Android 16; update an incompatible dependency or work with its maintainer rather than assuming the app code is the only cause. - Ship the compatibility fixes separately when practical. Keep the existing target SDK, make only changes needed to resolve Android 16 compatibility issues, and retain the current minimum SDK. Re-run the older-device checks before release. This phase may not require a compile SDK change, depending on the app.
- Prepare the API 36 target change. Update
targetSdkVersionto 36 and setcompileSdkVersionto 36 if needed for the build. Review the target-gated behavior checklist below against the app’s features and libraries. - Isolate behavior changes before release. Android 16 compatibility framework changes can be toggled individually for a debuggable build using Developer options or adb. Use the toggles to expose and diagnose a target-gated change before switching the app’s target, or to isolate a regression during development. They are test aids, not a substitute for testing the final target-36 build.
- Run the final matrix. Test the API 36 build on Android 16, the oldest Android version the app supports, and representative versions between them. Add Android 15 coverage for edge-to-edge behavior. If the app supports tablets, foldables, or other large-screen devices, test resizing and rotation there as well as on phones.
Review API 36 changes that can alter app behavior
Not every item applies to every app. Map each change to the screens, APIs, and dependencies that use it; test affected flows rather than treating an API-level upgrade as a mechanical version edit.
Rank #2
- Carrier: This phone is locked to Tracfone, which means this device can only be used on the Tracfone wireless network. Tracfone plan required, activating is easy, just 3 steps.
- DISPLAY: Immersive viewing on a 6.7-inch super-bright 120Hz display with powerful stereo speakers and Bass Boost for cinematic entertainment.
- CAMERA SYSTEM: Advanced 50MP Quad Pixel camera captures sharp, detailed photos and videos in any lighting condition
- PERFORMANCE: Lightning-fast 5G connectivity paired with a powerful processor and RAM Boost for smooth multitasking.
- BATTERY LIFE: Long-lasting 5000mAh battery with TurboPower charging technology delivers hours of power in minutes.
Edge-to-edge layout
Android 15 enforces edge-to-edge for apps targeting API 35. On Android 16, an app targeting API 36 can no longer use the windowOptOutEdgeToEdgeEnforcement opt-out. Check whether content is obscured by status or navigation bars, whether system-bar insets are handled correctly, and whether gesture areas overlap buttons or other controls. Include dialogs and both Compose and Views interfaces if the app uses them.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Predictive back and custom navigation
For an app targeting API 36 on Android 16 or newer, predictive system animations are enabled by default. onBackPressed is not called and KEYCODE_BACK is no longer dispatched in this case. Move custom back interception to supported back-navigation APIs and verify the expected behavior for nested navigation, unsaved changes, and dialogs. Android documents android:enableOnBackInvokedCallback="false" as a temporary manifest opt-out; treat it as a migration fallback, not the completed navigation change.
Rank #3
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
Large-screen resizing, orientation, and aspect ratio
On displays with a smallest width of at least 600dp, most apps targeting API 36 cannot rely on orientation, resizability, or aspect-ratio constraints being honored. Test split-screen, window resizing, rotation, and layouts at changing window sizes. Look for stretched or clipped content, then check that state survives activity recreation. Documented exceptions include games, a user opting into the app’s default behavior in aspect-ratio settings, and screens smaller than sw600dp. Android provides a temporary manifest opt-out, but says it will not apply when targeting API 37.
Scheduled work using scheduleAtFixedRate
When targeting API 36, a returning app process runs at most one missed fixed-rate execution immediately rather than immediately running every missed execution. Check any logic that assumes every interval will be replayed after the process is unavailable, especially work that updates state or performs repeated actions. Make the work safe when intervals have been missed instead of depending on a burst of catch-up executions.
Rank #4
- PRIVACY DISPLAY: Automatically hide your screen from those beside you. The built-in privacy display can be preset¹ to turn on when receiving notifications, typing passwords, or using specific apps
- TYPE IT IN. TRANSFORM IT FAST: Enhance any shot in seconds on your smartphone by using Photo Assist² with Galaxy AI.³ Add objects, restore details, or apply new styles by simply typing or tapping
- NIGHTS, CAPTURED CLEARLY: From gigs to city lights, record and capture moments after dark with clarity using Nightography so your photos and videos stay crisp and clear on your Samsung Galaxy
- MAKE IT. EDIT IT. SHARE IT: Turn everyday moments into something personal with creative tools built right into your mobile phone, whether it’s a special contact photo, custom wallpaper, an invitation or more⁴
- HELP THAT KEEPS UP: Stay in the moment while Now Nudge with Galaxy AI helps you respond faster and stay organized with smart suggestions⁵ that appear exactly when you need them on your phone
Health and sensor permissions
If the app uses affected sensor or health APIs, review API 36’s granular android.permission.health permissions in place of the relevant BODY_SENSORS permissions. The documented changes cover named heart-rate APIs and the health foreground-service case. Determine which permissions the app actually needs and update its permission flow accordingly; apps that do not use the affected functionality should not apply this migration indiscriminately.
Text height for specific scripts
API 36 ignores the deprecated elegantTextHeight attribute. If the app supports Arabic, Lao, Myanmar, Tamil, Gujarati, Kannada, Malayalam, Odia, Telugu, or Thai, inspect text wrapping, clipping, and vertical alignment on the screens that render those scripts.
Best Value
- Carrier: This phone is locked to Tracfone, which means this device can only be used on the Tracfone wireless network. Activating is easy, just 3 steps.
- ACTIVATION Promotion: Includes 1500 min, 1500 texts & 1500 MB Data + add more as you need it
- CAMERA SYSTEM: 50MP Quad Pixel camera. Capture sharper, more vibrant photos day or night with 4x the light sensitivity.
- PERFORMANCE: Blazing-fast Qualcomm performance. Get the speed you need for great entertainment with a Snapdragon 680 processor and 4GB of RAM.
- 64GB built-in storage. Get plenty of room for photos, movies, songs, and apps. Made for US
Check Android 16 issues that are not limited to target API 36
Passing the target-gated checks is not enough. Android 16 also changes ART internals, which can expose apps or libraries that depend on internal runtime structures. Test the app’s major flows with its actual runtime and dependencies, and investigate crashes or unexpected behavior in both app code and bundled SDKs.
Also assess native components on 16 KB memory-page devices. Android 16 offers compatibility mode for some apps built for 4 KB pages on those devices, but that is not a reason to assume every binary is ready. Check the actual native binaries and follow current Android guidance for building for 16 KB page sizes where relevant.
Build a test matrix around the app’s declared support
| Test target | What it verifies |
|---|---|
Oldest Android version allowed by minSdkVersion |
Installation, launch, core flows, and any older-version behavior the app promises. The precise version depends on the app’s configured minimum. |
| Representative intermediate Android versions | Regressions across the app’s supported range, including version-specific permission, navigation, and layout behavior used by the app. |
| Android 15 | Edge-to-edge behavior relevant to apps targeting API 35, especially layouts already using insets or system bars. |
| Android 16 | Both changes affecting all apps on Android 16 and target-gated behavior in the final API 36 build. |
| Phone and supported large-screen form factors | Small-screen flows plus resizing, rotation, split-screen, and state restoration on large displays where the app claims support. |
Run the same critical user journeys against the compatibility-only build and the final target-36 build. Include dependency-heavy features, background work, permission requests, and navigation paths, not only a clean launch. Choose physical devices or emulators according to the app’s real support policy; the right matrix is determined by its minimum SDK, user base, and supported form factors.
Plan releases against Google Play’s target API rules
Google Play’s policy page states that, starting August 31, 2026, new apps and app updates generally must target Android 16 (API 36) or higher. It lists lower thresholds for specific categories: Wear OS and Android Automotive OS apps must target API 35 or higher, while Android TV and Android XR apps must target API 34 or higher. The page also says an extension may be requested to November 1, 2026.
Existing apps are subject to a separate availability rule: the page says targeting API 35 or higher is required for an app to remain available to new users on devices running a newer Android OS. Check the current Play Console policy for the app’s category and release timing; these requirements are time-sensitive, and the update deadline is not a reason to skip older-device regression testing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
