◉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-11Intermediate

Four Countries, Not the World: Checking Which of My Six Apps the September 30 Deadline Actually Touches

Android developer verification goes live on September 30, 2026 in Brazil, Indonesia, Singapore, and Thailand. Here's how to decide from your own install data whether that date is urgent for you, and what actually blocks indie developers.

Android66Google Play44App Distribution3Indie Development31Expo237

✦ Premium Article

My notes said "fully mandatory in September 2026." That was about Android developer verification. September is next month, and two of the apps I run as an indie developer are distributed on Google Play. So I went back and reread the official pages — and what I found there was a list of four country names.

Brazil, Indonesia, Singapore, Thailand.

What begins on September 30, 2026 is enforcement in those four countries, not worldwide. Global expansion is explicitly listed as 2027. Had I spent August believing "everything stops in September," I would have gotten my priorities badly wrong.

That said, whether four countries is small depends entirely on who you are. In categories where the app barely depends on language — wallpapers being the clearest example — traffic from emerging markets runs higher than most people expect. "Only four countries" is not reassuring until you've looked at your own numbers. This is a record of how I checked mine.

Rereading in November: September 30 has already passed

I wrote this in August, so the "today" and "this month" in the body belong to that moment. In November I opened the same official pages again.

The first thing worth saying is that the date reads differently now. The developer page says "Effective September 30, 2026," and that day is behind us. I found no notice of a delay or a change, but the pages don't describe real-world behavior after the switch, so whether the four countries are hurting you is something only your own Play Console numbers can tell you.

Here is what I could add or correct on this reread.

ItemWhat the official help pages and FAQ say
DevicesCertified devices on Android 7 or higher; outside Google Play, phones and tablets in the selected regions
Not enforced yetApps distributed through stores other than the seven listed, and sideloaded apps, are described as outside this phase
Installing unregistered appsThe advanced flow or ADB. The flow runs developer mode, a check, restart and re-authentication, a one-day wait, then biometric or PIN; you can enable it for 7 days or indefinitely
ADBThe one-day wait is described as not applying
Limited distribution device capThe FAQ and the June blog say 20; the registration guide updated October 28, 2026 says 50. The pages disagree
Moving between accountsLimited can migrate to full, not the reverse

The cap discrepancy touches the table and the steps below. I wrote "20 devices" in the body, but the most recently updated guide says 50. I'd treat the number shown on the actual registration screen as the answer, and decide how many test devices to cover only after seeing it.

One more point. A D-U-N-S number is described as necessary only when you register as an organization; individuals don't need one. The wait of up to 28 days hasn't changed. Don't postpone the tasks that come with a waiting period. If you're leaning toward an organization registration, start with the number request.

The rest of the article stays as the record of the judgment I made in August. Please read its date phrasing with that in mind.

The dates that are actually confirmed, and the stores involved

Let me start with what is officially settled. To keep speculation out of it, the dates and country names below come only from what's published in the Android Developer Console help pages.

WhenWhat happens
November 2025Early access registrants began verifying apps they distribute outside Google Play
March 2026The full Android Developer Console experience opened to all developers
September 30, 2026In Brazil, Indonesia, Singapore, and Thailand, only apps registered by verified developers can be newly installed from the participating stores
2027Expansion to all apps distributed to certified Android devices, globally

The participating stores for this first phase are spelled out too. This is the part people skim past.

CompanyStore
GoogleGoogle Play
HonorHONOR App Market
OPlusOPPO App Market
SamsungGalaxy Store
TranssionPalm Store
vivoV-Appstore
XiaomiGetApps

Google Play sits at the top of that list. I had initially filed this whole thing under "sideloading regulation" — something aimed at people who hand out APKs directly, and therefore not really my problem since I ship through Play. It's the opposite. Installs through Play are covered. "I only ship on Play, so this doesn't apply to me" is the single most dangerous misreading here.

Sideloading itself isn't going away either. Apps from unverified developers remain installable through an advanced flow, after the user acknowledges the risk and completes a one-time setup, and ADB continues to work as the normal path for development. But those are escape hatches for someone holding the device. They are not a distribution strategy.

✦

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 decide in about thirty minutes, from your own country install split, whether the September 30 date is urgent for your app or not
✦You will avoid discovering the real bottleneck (a registration number that takes weeks to issue) only after the deadline has passed
✦You will be able to rank several apps by which to register first, using numbers instead of guesswork
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-16
Your First Year With Rork: The Order Your Bills Actually Arrive In
Starting on Rork's free tier doesn't mean Rork is the only thing you'll pay for. I lined up the official pricing for Rork, Apple, Google Play, Expo (EAS) and Supabase to show what gets billed when in year one, what simply stops instead, and how to put those dates on a calendar.
⟐ 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-08-20
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.