Tomorrow is the Play deadline — but your app is not getting removed

31 August 2026 is Google Play's target API level deadline. What actually happens, what doesn't, and the thing API 36 really breaks in a portrait-locked game.

Bu yazının Türkçesi: Türkçe sürüm.

I am writing this on 30 August 2026. Tomorrow is Google Play's target API level deadline. The sentence going around developer groups is: "if you're not on API 36 by 31 August your app comes off the store."

That is wrong. Let me lay out what actually happens, and what genuinely breaks, because both differ from the popular version.

What actually happens on the deadline

Per Google's own documentation, 31 August 2026 means two separate things and they keep getting conflated:

For new apps and updates. After that date, every new build you upload to Play Console must target at least Android 16 (API level 36). Wear OS and Android Automotive need API 35, Android TV and XR need API 34.

For existing apps. For apps already published that you are not updating, the bar is lower: API 35. Apps below that bar are not removed from the store. What happens instead is that they become invisible to new users on devices running an Android version newer than the app's target API level.

Which means:

• Users who already installed the app notice nothing. It keeps working.
• New users on older Android versions can still install it.
• New users on newer Android versions don't see it in the listing.
• And you cannot upload an update.

That last one is what actually hurts. Your app is not removed, it is frozen. You cannot ship a bug fix. In practice the product is dead, it just dies more slowly.

There is also an escape hatch: if you cannot make it, you can request an extension through the Policy status page in Play Console, valid until 1 November 2026. The extension form only appears for non-compliant apps. So check the console before you panic.

What API 36 actually breaks

Changing the number on the targetSdk line takes five seconds. The work is dealing with the behaviour changes that switch on when you do. The Android 16 behaviour changes page has a long list; three matter most if you write games or small apps.

1. Edge-to-edge is now mandatory. The windowOptOutEdgeToEdgeEnforcement attribute is deprecated and disabled on Android 16 devices. You cannot opt out of drawing under the system bars any more; you have to handle insets yourself. An interface that doesn't isn't merely ugly — it's worse than that: a button that ends up under the status bar cannot be tapped, and you will not notice in the emulator.

2. Predictive back is on by default. onBackPressed() is no longer called and KEYCODE_BACK is not dispatched. If you intercept the back button you must migrate to OnBackInvokedCallback. There is a temporary escape — android:enableOnBackInvokedCallback="false" in the manifest — but as the name says, temporary.

3. Orientation locks are ignored on large screens. This is the big one for me. On displays 600dp wide and above, all of the following are ignored:

• android:screenOrientation
• android:resizableActivity="false"
• android:minAspectRatio and android:maxAspectRatio
• calls to setRequestedOrientation()

Zıpla is a portrait-locked game. Running on a tablet it has always stayed portrait. Under API 36, a tablet user who turns the device sideways gets the game sideways too — and my game canvas was not ready for that. You cannot fix this by changing one line in the manifest, because the fix is in the interface itself.

There is a temporary escape here as well:

<application>
  <property
    android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY"
    android:value="true" />
</application>

But Google states plainly that this opt-out expires at API 37. So you buy a year, you don't solve anything. If you have a portrait-locked mobile game, put "landscape layout" on next year's list right now.

Two more things on the same calendar

The target API deadline does not arrive alone. Here is the next year for an independent developer:

Apple's side was quieter this year: since 28 April 2026, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS 26 SDK or later, using Xcode 26 or later. That date has passed; if you missed it you already know, because the upload gets rejected.

Developer verification: don't panic, know the calendar

This is the topic that generated the most noise this year. Briefly: Google wants apps installed on certified Android devices to come from verified developers — not just via Play, but including sideloading and third-party stores.

Set aside the "Android is closing" headlines and look at the calendar:

• October 2025: early access began by invitation.
• March 2026: verification opened to all developers.
• September 2026: the requirement takes effect in four countries only — Brazil, Indonesia, Singapore, Thailand.
• 2027 and beyond: global rollout.

So if you hand an APK to a user in Turkey, nothing changes this month. If you publish through Play you have already been through a verification process and nothing changes for you at all.

What will change is this: handing an APK to a friend and publishing on Play used to be two entirely separate worlds. They are merging. Anyone distributing a beta over Telegram, sharing an internal test APK, or offering a download from their own site will enter this process over the next two years. Google describes it as "like an ID check at the airport", and says the app's content is not reviewed. That may well be true; it is still one more piece of friction.

The order I worked in

Seeing this calendar, I lined my own list up like this:

1. Check the console first. The Policy status page tells you directly whether you are compliant and whether you are eligible for an extension. Don't guess.
2. Raise targetSdk, then play on a real device. The emulator forgives edge-to-edge problems; a real phone does not, especially one with a notch.
3. Try the tablet scenario today. See what happens when the orientation lock is ignored. Even if you are going to apply the temporary opt-out, apply it knowing what you are opting out of.
4. Migrate the back button if you handle it. In games, back usually means "pause". Without the new API that behaviour quietly disappears.

And a general note: none of these dates were a surprise. All three were announced months ahead. In a one-person studio the problem is never not knowing the dates — it is never finding the time to look at the calendar. I partly wrote this post as a reminder to myself.

← All posts