Android developer verification bites tomorrow: what founders shipping Android apps should check before 30 September

Android developer verification enforcement starts on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand, with every certified Android device worldwide to follow in 2027 — a distribution requirement app owners need to confirm their agency has handled.

Search interest in “Android developer verification”, “sideloading changes” and “Android 17 unverified apps” has climbed through September, and the reason is a single date: tomorrow, 30 September 2026. From then, certified Android phones in Brazil, Indonesia, Singapore and Thailand will block normal installs of apps whose developer has not registered an identity with Google. That applies to Google Play and to the stores run by Samsung, Xiaomi, OPPO, vivo, Honor and Transsion.

Google has said the rollout expands to certified Android devices globally in 2027. The four launch markets are the trial run.

What has not changed

Sideloading is not banned. Power users can still install unregistered apps through an advanced flow that adds an authentication step and a one-off 24-hour wait. Google also created a limited-distribution account for hobbyists and students that skips the ID requirement. None of that helps a company shipping a commercial product to customers.

Why this is a commissioning issue, not a developer issue

The verification identity sits with whoever owns the developer account. If your app was published under your agency’s account rather than your own, the legal identity Google verifies is theirs, not yours. That is a problem if you ever change supplier, and it is now also a distribution dependency with a live deadline.

Three questions to put to whoever builds your Android app:

  1. Whose developer account is the app published under, and is it registered and verified?
  2. Do you distribute outside Google Play, for example enterprise builds, beta testers or regional stores? Those routes are affected most.
  3. Does your release pipeline use the new registration APIs, or will each release need manual handling?

So what

If you sell to users in the four launch markets, verify now. If you do not, treat 2027 as your deadline and use the time to move the developer account into your company’s name. A clean handover of accounts, signing keys and store listings is part of what a good build partner provides as standard. If you are unsure where your Android app stands, our iOS and Android team can audit your distribution setup, or you can start a project with us.

← All research

More research.

GitHub Copilot adds Supabase, Webflow, Wix and five more connectors in public preview

GitHub Copilot now connects to eight more services, including Supabase, Webflow, Wix and Mixpanel, through verified MCP connectors in public preview. They join more than 25 existing ones.

Read ›

Gemini 4 Neon is generally available in GitHub Copilot, aimed at lower-cost agentic coding

Gemini 4 Neon is now generally available in GitHub Copilot for agentic coding. Google says its quality is close to Gemini 4 Carbon at a lower token cost per task.

Read ›

Claude Code 2.1.328 brings auto mode to Bedrock, Vertex and Foundry, and narrows /code-review to bugs

Claude Code 2.1.328 extends auto mode to Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud and Microsoft Foundry. /code-review now reports only bugs and CLAUDE.md violations.

Read ›

GitHub Copilot Evals: repeatable tests for AI agents, now in public preview

GitHub Copilot Evals lets teams write repeatable tests for AI coding skills, custom agents and MCP tools. It checks both the result and the path the agent took, and is in public preview.

Read ›

GitHub Copilot can now drive your browser: browser use enters public preview

GitHub Copilot browser use lets an AI coding agent control Chrome to debug web apps and run browser tests. It is in public preview across the CLI, the Copilot app, VS Code and JetBrains.

Read ›

Claude Code 2.1.327 refuses some symbolic links and lists broken setup in /status

Claude Code 2.1.327 tightens file and package permissions again and adds a /status list of broken agent, skill and hook settings. A short read for teams using AI coding tools on a live product.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work