Actualité
Google sets September Android developer-verification deadline for four countries
Google is preparing the first user-facing phase of Android developer verification, with app registration requirements starting September 30 in Brazil, Indonesia, Singapore and Thailand.
Google is moving Android developer verification toward its first user-facing enforcement phase. In an updated post published on the Android Developers Blog, the company said app registration requirements will begin on September 30, 2026, for users in Brazil, Indonesia, Singapore and Thailand.
The change is designed to make it harder for malicious actors to distribute harmful Android apps while retaining alternative installation paths for experienced users. Google says the initial rollout will cover installations from seven participating stores: Google Play, HONOR App Market, OPPO App Market, Samsung Galaxy Store, Transsion Palm Store, vivo V-Appstore and Xiaomi GetApps.
What changes on September 30
Under the announced rules, apps distributed through the participating stores in the four launch countries must be associated with a verified developer. Google says developers should register any remaining apps before the deadline. Play developers can check their status in Play Console, while developers distributing apps outside Google Play can use the Android Developer Console.
Google says more than 99% of apps on Google Play have already been registered automatically. That figure should reduce the immediate impact for most Play users, but developers with less common distribution arrangements still need to check their accounts. The company specifically advises developers to review their Play Console status and register apps that were not automatically linked to a verified identity.
The initial scope is deliberately narrower than a global Android change. It applies to the four named countries and the seven participating stores, rather than to every Android device or every app source worldwide. Google says the protections will expand globally for apps installed on certified Android devices from 2027 onward.
Sideloading is not being removed
The announcement does not describe a blanket end to sideloading. Google says unregistered apps can still be installed through Android Debug Bridge, commonly known as ADB, or through a new advanced installation flow intended for power users.
That advanced flow is scheduled to launch globally in August. It will add security checkpoints designed to resist coercion scams while preserving a route for users who knowingly install software from an unverified developer. The distinction matters: the new system raises the friction around unverified apps, but the announced policy still provides explicit ways to install them.
For ordinary users, the most visible effect should be limited to apps obtained from outside the established store ecosystem, and even then the first enforcement phase will be regional. Users in other countries are not part of the September launch described by Google, although the company has signalled that broader coverage is planned.
New tools for developers
Google is also adding tools intended to make registration easier for developers with large catalogues or automated release pipelines. The Android Developer ID Status API can check whether a package name has been registered, while the Android Developer Console API is intended to let developers register and manage package names from their development environments.
The APIs support bulk workflows and OAuth delegation, allowing third-party platforms such as app stores to perform registration operations on a developer’s behalf. That could reduce manual work for teams distributing the same application across multiple storefronts, although the final operational details will depend on how each store integrates the APIs.
Google has also introduced limited distribution accounts for students, hobbyists and learners. The company says these accounts can be used to share apps with up to 20 devices without requiring a government-issued ID or a fee. The feature is aimed at small-scale testing and learning rather than broad commercial distribution.
Why the rollout matters
Android’s open distribution model has always made it possible to install software from sources beyond Google Play. That flexibility supports independent developers, alternative stores and enterprise deployments, but it also makes it easier for attackers to circulate apps under false or disposable identities.
Developer verification targets that identity problem. It does not certify that every app is safe, and it does not replace malware scanning, permission review or sensible user behaviour. Instead, it gives app stores and Android’s installation framework a stronger way to associate software with an accountable developer.
Google says the verification system was introduced to strengthen ecosystem security and that millions of apps have already been registered. The company is now asking developers to prepare for the September deadline, particularly those distributing in Brazil, Indonesia, Singapore or Thailand through one of the participating stores.
For users, the practical advice is straightforward: apps from recognised stores should continue to work normally, while installations from unfamiliar sources may require additional verification steps. Developers in the first four markets should review their registration status now, and teams that rely on automated publishing should evaluate the new APIs before the deadline arrives.
More technical details are available in Google’s Android developer verification documentation. The next significant checkpoint is September 30, followed by the planned global expansion in 2027.