Google Play starts blocking unverified apps on 30 September — what Android developer verification means for distribution

From 30 September 2026, certified Android devices in Brazil, Indonesia, Singapore and Thailand will only install and update apps from verified developers, with global rollout confirmed for 2027 — a real change to how 'sideload an app' and 'Android app distribution' need to be planned for, not just an Apple-style App Store rule anymore.

Google has confirmed 30 September 2026 as the enforcement date for Android developer verification: from that date, certified Android devices in Brazil, Indonesia, Singapore and Thailand will only install or update apps registered to a verified developer identity, across Google Play and six participating third-party stores including Galaxy Store and OPPO App Market. Global expansion to all certified devices is planned for 2027. Google says over 99% of existing Play developers have already completed verification, and new APIs are landing this month to support bulk registration and CI/CD pipeline integration for teams shipping regularly.

This closes a gap that’s existed since Android launched: unlike iOS, Android has always allowed installing apps from outside any official store, no identity check required. That openness is real and still exists — unverified apps can still be sideloaded via ADB or an “advanced flow” with built-in friction designed to resist coercion scams — but it’s no longer the frictionless default. Android is moving toward the same “known, accountable publisher” model Apple has run for years, just arriving there from a different starting point and on a slower, market-by-market timeline.

So what

If you’re building or maintaining an Android app — whether that’s a consumer product, an internal enterprise tool distributed outside Google Play, or a white-label app for a client — developer verification status now belongs on the pre-launch checklist alongside app signing and Play Console setup, particularly if any distribution touches Brazil, Indonesia, Singapore or Thailand before global rollout in 2027. For enterprise and internal-distribution apps specifically, this is worth flagging early: teams that have relied on informal sideloading for internal builds will need a verified publisher identity sooner than the global timeline suggests, in any market where the deadline is already live. If you’re planning an Android build and want the distribution strategy sorted before development starts, see our iOS & Android work or get in touch to talk it through.

← All research

More research.

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

GitHub now reports how often developers act on Copilot code review comments

On 5 November 2026 GitHub added code review metrics, including an addressed rate, to the Copilot usage metrics API. For AI software development buyers, it is the first first-party number for how much AI review feedback is acted on.

Read ›

Dependabot can now keep AI agent skills and prompts up to date

GitHub's Dependabot gained Agent Package Manager (APM) support on 3 November 2026, treating AI agent skills, prompts and instructions as dependencies that need updating like any other software.

Read ›

GitHub Copilot is now inside Xcode's own coding assistant: what iOS app owners should ask

GitHub put Copilot into Xcode's built-in coding assistant on 4 November 2026, in public preview with Xcode 27.3 beta. AI-assisted iOS app development is now a built-in choice of agent, not a plug-in.

Read ›

GitHub's Copilot usage API now separates bring-your-own-key and custom models: AI spend visibility for software buyers

GitHub's Copilot usage metrics API now reports bring-your-own-key (BYOK) and enterprise custom model usage separately, as of 3 November 2026. Teams using AI coding tools can see more of where usage goes.

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