
Installing an Android application outside Google Play could soon require an additional security process, even when the app comes directly from its developer’s website.
Google has confirmed that its Android developer verification system will begin expanding globally in January 2027. The programme, which started with selected countries in September 2026, will require developers to register their identities and applications before those apps can be installed through normal installation methods on affected Android devices.
What makes this announcement significant is its reach. Google is not limiting the requirement to applications published on the Play Store. Independent app stores, APK repositories and developers distributing software directly to users will also be affected.
What Google’s new Android verification system actually does
The idea behind developer verification is relatively simple. Google wants to establish who is responsible for an Android application before allowing it to be installed through normal methods on certified Android devices.
Under the system, developers must verify their identities and register their applications using information that connects the developer to the software.
This includes two important technical identifiers:
- Package name: The unique identifier assigned to an Android application, such as
com.example.myapp. - Signing certificate: A cryptographic certificate used to establish the application’s signing identity.
Connecting these details to a verified developer account gives Android a way to check whether an application belongs to a registered developer.
Google has clarified that this is not an additional review of every application’s source code or functionality. The programme focuses on developer identity and application ownership, rather than determining whether an app is useful, well-designed or free from every possible security problem.
Why Google is expanding verification beyond the Play Store
Google’s stated reason for introducing this system is to make it harder for malicious developers to distribute harmful applications using disposable or anonymous identities.
Consider a situation where a fraudulent application is identified and removed. Its creator could potentially create another developer account, change the app’s name and publish a replacement APK. Users might download the new application without realizing that it comes from the same source.
Google believes linking applications to verified identities will make this type of repeated abuse more difficult.
The company has previously cited its security research, reporting substantially higher levels of malware from internet-sideloaded sources than from Google Play. Google reported a 50-times difference in its August 2025 announcement and a 90-times difference in March 2026.
These figures are based on Google’s own analysis, but they explain the security problem the company is trying to address.
There is another side to this argument, though. Android became popular partly because users could obtain software from sources other than the official Play Store. Extending identity registration to those distribution channels introduces a new layer of control over an ecosystem that has traditionally offered developers more flexibility.
Which app stores will be affected?
Google has identified seven participating application distributors for the initial rollout:
- Google Play
- Samsung Galaxy Store
- HONOR App Market
- OPPO App Market
- Xiaomi GetApps
- Transsion Palm Store
- vivo V-Appstore
The inclusion of these platforms is important because Android users do not all obtain applications from the same marketplace. Someone using a Samsung phone might regularly use Galaxy Store, while another person could download applications through Xiaomi’s GetApps or Transsion’s Palm Store.
Google wants developer verification to extend across these distribution channels rather than remain a Play Store requirement.
The expansion is scheduled to begin in January 2027, with protections extending to additional countries and installation sources over several months. Google’s distributor guidance also identifies March 1, 2027, as a target for other app stores to have the required protections in effect.
What happens when someone installs an unregistered APK?
This is probably the part of the announcement that will concern regular Android users most.
Google is not completely removing the ability to sideload applications. Instead, it is introducing additional steps for installing applications that have not been registered by a verified developer.
On affected devices, users will need to go through a process Google calls Advanced Flow.
The process involves enabling developer options, allowing installations from unverified developers, completing additional security checks and restarting the device. Users must then wait for a 24-hour security period before returning to enable the setting.
After completing the process, users can authorize unverified applications for seven days or indefinitely.
That extra waiting period is intentional. Google wants to make it harder for scammers to pressure people into immediately installing applications that could compromise their devices.
Developers also retain an important exception: Android Debug Bridge (ADB) installations are not subject to the Advanced Flow waiting period. This means developers can continue installing and testing their own APKs through their normal development workflow.
Google’s published requirements focus on restricting normal installation and updates of unregistered applications. They do not establish that Android will automatically delete every unregistered app already installed on a device.
Android developers will need to register their applications
Google has provided two registration options depending on where developers publish their applications.
Android Developer Console
This option is intended for developers who distribute applications outside Google Play. Independent developers, software companies and publishers sharing APKs directly with users can use it to verify their identities and register their applications.
Google Play Console
Developers already publishing through Google Play can manage verification and application registration through their existing Play Console accounts.
Google has also reported that approximately 99% of Play applications have already been registered automatically. Existing publishers should still check their account status for outstanding requirements.
The general registration process involves:
- Creating or accessing a developer account.
- Choosing an individual or organization account.
- Completing the required identity verification.
- Registering the application’s package name.
- Providing the SHA-256 fingerprint of its signing certificate.
- Completing any additional ownership checks requested by Google.
Developers should pay particular attention to their signing keys. An application package name and its signing certificate are connected, and losing the private key can create complications when proving ownership.
Google has also introduced registration APIs to help developers and alternative app stores automate parts of the process, particularly when managing multiple applications.
There is a free option for smaller developers
Not every developer needs unrestricted public distribution. Google has introduced a limited distribution account for students, hobbyists and people sharing applications with small groups.
This account is free and supports unlimited application registrations, but developers can authorize installations on only 50 devices.
It provides an alternative for someone building a small application for a classroom, a group of testers or a personal project.
Developers seeking unrestricted distribution can use the full-distribution account, which carries a $25 registration fee through Android Developer Console.
The distinction is important. The free option is not a replacement for full commercial distribution. Developers intending to publish applications to the general public should consider the full-distribution requirements.
What this means for Nigerian Android developers
Nigeria is not among the four countries where Google initially activated developer verification protections on September 30, 2026. Those countries are Brazil, Indonesia, Singapore and Thailand.
However, Nigeria is included in Google’s planned global expansion. The company has not published a separate activation date for Nigeria as of November 21, 2026.
There is already a Nigerian-specific list of acceptable identity documents for developers completing verification.
Individuals can use documents such as an international passport, National ID card, driver’s licence or voter’s card. Proof of address may include an eligible utility bill, bank statement or insurance statement issued within the preceding 90 days.
Organizations must provide appropriate registration documents, such as a certificate of incorporation, alongside identification for an authorized representative. Google’s full-distribution requirements also include a D-U-N-S number and a verified organization website.
For Nigerian software companies and independent developers, preparing these details ahead of the regional rollout could prevent unnecessary delays when registering applications.
Open-source developers are not entirely comfortable with the changes
Not everyone in the Android community supports Google’s approach.
F-Droid, an independent repository for free and open-source Android applications, has raised concerns about requiring developers to register with Google even when they distribute software outside Google Play.
In February 2026, F-Droid published an open letter opposing the policy. The letter received support from 37 organizations and technology companies, including the Electronic Frontier Foundation and Free Software Foundation.
Their concerns include privacy, developer freedom and the possibility that independent application distribution could become more dependent on Google’s registration infrastructure.
There is a practical concern here. An open-source developer might publish a small utility without intending to make money or collect user information. Under the full-distribution model, that developer would still need to complete Google’s identity verification process before distributing the application normally on covered devices.
Google has responded with limited distribution accounts, Advanced Flow and registration APIs. These additions provide alternatives for certain use cases, but they do not remove identity verification from unrestricted distribution.
Android’s open distribution model is entering a new phase
Google’s global developer verification expansion introduces a new requirement for distributing software across the certified Android ecosystem.
For Google, the objective is to make malicious developers easier to identify and hold accountable. For independent developers, the process introduces identity, registration and signing-certificate requirements that extend beyond Google’s own marketplace.
Sideloading will remain available, and developers still have ways to test and distribute applications under Google’s different account arrangements. However, installing unregistered applications through normal methods will become less convenient.
The next important development will be the country-by-country rollout beginning in January 2027. Nigeria’s activation date, the response from alternative application stores and the experience of users installing independent APKs will provide a clearer picture of how the policy works in practice.
For now, Android developers should review their package names, secure their signing keys and check their registration status before the global rollout reaches their markets.
Sources:
- Google’s November 19 announcement on expanding Android developer verification globally
- Android developer verification programme overview
- Frequently asked questions about developer verification
- How limited distribution accounts work
- Application registration guidance for open-source developers
- F-Droid’s open letter opposing Android developer verification
Discover more from Aree Blog
Subscribe now to keep reading and get access to the full archive.


