Every year the same item appears in mobile backlogs: raise the target SDK. It is estimated as a one-line change, because in the build file it is one. It is also the first release in which the platform treats the app differently.
The Date Is Fixed
Google Play's target API requirements are explicit: "Starting August 31, 2026: New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play," with lower bars for Wear OS, Android Automotive OS, Android TV and Android XR apps. Teams "will be able to request an extension to November 1, 2026." The long-run penalty is reach: existing apps below the previous bar stop being available "to new users on devices running Android OS higher than your app's target API level." The newest phones, the ones future customers are buying, stop seeing the listing.
Where the Risk Actually Sits
The behavior changes are the real work, and one of them fails silently. For apps targeting API 36 on Android 16 devices, the system back animations "are enabled by default. Additionally, onBackPressed is not called and KeyEvent.KEYCODE_BACK is not dispatched anymore" (Google). Every "discard your draft?" confirmation built the old way stops firing. The customer swipes back and the work is gone, and no test fails because the code that would have run is never called.
Two more changes land with the same bump:
- Edge-to-edge is no longer optional. The opt-out attribute "is deprecated and disabled." Buttons and text that sat safely inside the system bars now sit under them unless each screen handles it.
- Orientation locks stop working on large screens. Restrictions "no longer apply on displays with smallest width >= 600dp," with a temporary opt-out that ends at API 37.
Some Android 16 changes reach apps whatever their target, including a job runtime quota that "impacts tasks scheduled using WorkManager, JobScheduler, and DownloadManager" (Google).
How to Run It
Treat the target bump as a project with a risk register, not a ticket. Bump on a branch first and list what breaks; fix back handling before anything else because it is the one that loses data; audit every screen for edge-to-edge; decide the large-screen position explicitly; then ship behind a staged rollout. Request the November extension early if needed, and plan to ship on August 31 anyway. An extension is insurance, not a schedule.
-Rocky
#Android16 #GooglePlay #PlatformRisk #EngineeringDreams #StrategiaX
Originally published on ANDROID-ARCHITECT, the Android engineering blog of Strategia-X.