A rocky journey to targetSDK 36 @AndroidDevelopers
A rocky journey to targetSDK 36  @AndroidDevelopers
Uploaded November 2026 | Updated November 2026, 3 hours ago
We knew it was coming, but it still began with an ominous Play Console warning: update to targetSdk 36 before the deadline. The upgrade sounded straightforward... until it wasn’t. In this session, I’ll share the challenges we encountered, assumptions that proved wrong, and what we learned along the way. It’s an honest, practical look at a major migration, including our mistakes and the lessons that could save other teams time and trouble.

This recording is from the community track at Android Dev Summit Extended in London. Thanks to all our guest speakers!

Speakers: Ale Stamato

Chapters:
0:00 - Introduction
3:45 - Defining the migration strategy
5:30 - Adaptive layout enforcement on large screens
7:33 - Edge-to-edge enforcement and opt-out
10:48 - Predictive back navigation
13:20 - Background work and job scheduling
14:24 - Testing tips and automated flows
15:44 - Migration results


Watch all the sessions from Android Dev Summit 2026 → https://goo.gle/ADS26-All-Sessions

Subscribe to Android Developers → https://goo.gle/AndroidDevs


#AndroidDevSummit2026


Event: Android Dev Summit 2026

Products Mentioned: Google Play Console, Google Play
A rocky journey to targetSDK 36Android at Google I/O ConnectTrace me if you can: Automated instrumentation and field profilingInside Gemini Nano and Gemma 4 powering on-device intelligenceEngineering memory-performant Android appsWhat is new in app performance reporting on PlayBuild apps for Wear OS 7 and the Pixel Watch 5What’s new in Google PlayHow to make code review easier with AITest on real hardware through Android CLIJetPacker App demoHow to understand Play’s expanded billing options and lower fees
Android Developers |

A rocky journey to targetSDK 36

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER