News · written 2 November 2026. A summary for readers, not legal or business advice — check the sources at the end before relying on any detail.

For most of Android's history, anyone could build an app, share the installer file and let people install it. That is changing. Google's Android developer verification requires apps on certified Android devices to be registered to a developer whose identity has been checked — including apps that never go near the Play Store. If you share Android apps yourself, including through JM Tech Power, here is the short version.

What started on 30 September 2026

From 30 September 2026, Google says its protections began for people in Brazil, Indonesia, Singapore and Thailand who install apps from participating stores on certified devices running Android 7 or later. In those places, an app has to be registered to a verified developer to be installed and updated that way. The first participating stores are Google Play, HONOR App Market, OPPO App Market, Samsung Galaxy Store, Palm Store (Transsion), vivo V-Appstore and Xiaomi GetApps.

Google says it will expand the requirement globally in 2027, after taking in feedback from partners, users and developers.

Sideloading is not banned

Google has repeated that installing apps from outside a store is staying. Apps from developers who have not registered can still be installed with Android Debug Bridge (adb), or through an advanced flow for experienced users that launched in August 2026. Google says that flow includes extra security checkpoints, aimed at scams where someone is talked into installing a malicious app.

What it means for small developers

• On Google Play already? Google says Play registers about 99% of apps automatically; the rest, and apps you ship outside Play, are registered from Play Console.
• Only distributing outside Play? There is a separate Android Developer Console for developers who never use Play.
• Students, teachers and hobbyists can use a limited distribution account: share an app with up to 20 devices without a government-issued ID or a registration fee. That suits class projects and apps for family and friends.
• Google points developers to its own guides for account options and any fees, which can differ by account type.

Why it matters

Google frames verification as a defence against malware spread through sideloaded apps: if a known developer is behind every installable app, bad actors are easier to stop. Critics, including people who build and distribute free and open-source Android apps, worry that one company now decides who may publish on a platform that used to be open by default. Both sides will be watching how the advanced flow works in practice before the 2027 rollout.

If you publish Android builds, a practical step is to check now which account type fits you, so your users are not surprised when the rules reach their country.

Sources

• Android Developers — Android developer verification (timeline, account paths, limited distribution accounts).
• Android Developers Blog — Android developer verification: Building a safer ecosystem together, 18 June 2026 (enforcement date, countries, participating stores, adb and advanced flow).
• Android Developers Blog — A new layer of security for certified Android devices, August 2025 (the original announcement).

More news and guides at https://jmtechpower.com/articles.