◉RORK LABJP
●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30
Articles/Business
⟐ Business/2026-08-20Intermediate

August 31 Means Something Different Depending on Whether You Plan to Ship an Update

Two separate conditions land on Google Play's August 31 date: API 36 to submit an update, and API 35 to stay discoverable to new users. Here is how I sorted six apps, and who actually gets the extension form.

Google Play44targetSdkVersion5Expo237release operationsindie developer53

✦ Premium Article

I opened the Policy status page for all six of my apps in one sitting earlier this month. Some had warnings. Others had nothing at all. My first reaction was confusion about which state was the correct one.

Reading more carefully, I found that two conditions of different kinds happen to share the same date. Treating them as a single deadline leads either to work that was never needed, or to running out of runway on the one app that mattered.

Two conditions land on the same date

Breaking apart what the Play Console Help page actually says:

ConditionApplies toTarget API neededWhat happens if you miss it
SubmissionNew apps and app updates36 (Android 16) or higherYou cannot submit at all
AvailabilityApps already published35 (Android 15) or higherNew users on devices running an OS newer than your target can no longer discover the app

So an app already shipping at API 35 does not vanish from the store on August 31. What closes is the path to shipping anything new. The moment you try to publish the next version, 36 becomes the requirement.

That was the part I had backwards. I had been working from "get to 36 by August 31 or the app disappears," when in fact the only apps whose distribution was genuinely at risk were the ones still below 35. Once the location of the risk changes, so does the priority order.

Worth noting: the numbers differ by form factor. Wear OS and Android Automotive OS need 35 or higher, while Android TV and Android XR need 34 or higher. If you ship a watch target, do not reuse the phone number.

The extension form only reaches apps that got a warning

This is the detail that trips up the most people in practice.

The Play Console Help page states that only apps that are not compliant with the policy receive policy warnings and notifications, and that the extension form is reachable from the details page of that warning on the Policy status page. There is no permanent "request extension" button sitting at the account level.

Three practical consequences follow:

  1. If no warning appears, no form appears. From Google's side that is correct behavior: a compliant app does not need one. But if you are waiting for a form that will never show up, you are waiting on nothing
  2. The extension protects distribution, not submission. Being granted an extension does not let you publish an update built against a target below 36. The window until November 1 exists so your app keeps reaching all users, nothing more
  3. The timing of the form is Google's call. The Help page says it will become available in Play Console later this year, which is not a promise that you can open it today

The third point deserves the most caution. If your plan depends on the extension, your next move is gated on someone else's schedule. Plan for the possibility that August 31 arrives with no form in sight.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦You will be able to tell what your app actually loses on August 31, based on whether you plan to ship another update
✦You will spot the situations where waiting on the extension form leaves you with no moves left, and avoid getting cornered days before the deadline
✦You will be able to work backward from your staged rollout timeline to your own submission cutoff, and decide the order in which multiple apps go out
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Rork Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

⟐ Business2026-10-24
Google Play's Extension Ends November 1 — Count Backwards from Your Submit Day
The target API 36 extension on Google Play ends November 1. Instead of counting to the deadline itself, count back from the last day you can submit — with a small script that does the date math.
⟐ Business2026-08-31
After the Google Play deadline: which dormant Android apps to raise, and which to leave at 35
Apps you have stopped updating are governed by a different bar than apps you still ship. Here is how to inventory effective targetSdk across your builds and decide which apps to raise, hold, or retire.
⟐ Business2026-10-28
If You Want to Rename an App After Release, Sort What the Store Keeps From What You Redo. Before Choosing a Name, Look at a Trademark Search
Being able to save a name in App Store Connect is not the same as being allowed to use it. Here is what Apple and Google Play documentation actually says about renaming after release, a small script that finds the old name left inside your project, and the order I check things before settling on a name.