On November 19, Google announced that it will roll out Android developer verification worldwide in phases starting in January 2027. The program was first introduced at certain stores in four countries, including Brazil. The global rollout will begin with seven stores, including Google Play and the Galaxy Store. Google plans to extend it to other stores by March of the same year.
The program verifies a developer's identity and links the package name that identifies an app, along with the signing certificate of its installation file (APK), to that developer. Because distributors sometimes re-sign the same app with their own keys, even a developer who has completed identity verification needs to make sure the signature on the version that actually reaches users is also verified.
Seven stores in January, other stores by March
Google will start the global rollout at seven participating stores in January 2027 and plans to extend it to other stores by March of that year. The list of participating stores for January appears on the official blog, and the timing for other stores is described in the guide for distributors.
| Timing | Distribution channels covered |
|---|---|
| September 30, 2026 | Early enforcement at certain participating stores in Brazil, Indonesia, Singapore and Thailand |
| January 2027 | Global rollout begins with seven stores: Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo |
| By March 2027 | Planned to apply to other stores as well |
The distributor guide lists March 1, 2027 in its preparation table and sample developer notices. That is the target date for stores to set up systems to check the registration status of the apps they distribute, contact developers who have not registered, and match submitted APKs. Google's published materials do not give dates for when the program will begin in each country or region, including Japan, or when it will apply to APKs distributed directly through individual stores or websites.
In the early enforcement in September 2026, verification applied to apps installed from certain participating stores in the four countries. Other stores and sideloading, where an APK is installed directly onto a device, were excluded. Google has outlined a plan to extend coverage over several months to every installation source on certified Android devices. According to Google's FAQ, the program covers certified Android devices running Android 8 (API level 26) or later, and the protection is delivered through Google Play services. Certified Android devices physically located in comprehensively sanctioned countries are exempt from verification checks.
Google put this policy forward in 2025 to make it harder for bad actors to repeat the pattern of distributing another app anonymously after a harmful app is removed. To tie apps to verified developers regardless of where they are distributed, the actual distributed build must be identifiable. So even if an app is published under the same package name, whose key signed the APK determines the registration steps.
What affects registration is the signature of the distributed APK
In Google's guide for distributors, the unit that stores match against is the combination of the package name and the SHA-256 fingerprint of the signing certificate. The package name is the name that identifies the app, and the fingerprint is a value that identifies the signing certificate. According to Google's FAQ, multiple signing keys can be registered for the same package name. In other words, if the same app is distributed on a developer's own site and in an open-source repository, and the repository re-signs it with its own key, a certificate corresponding to each distributed version is required.
The entry point for the process depends on whether you use Google Play. Developers who publish only outside Google Play complete identity verification and app registration in the Android Developer Console. Developers who use Google Play can check their registration status in the Google Play Console, and Google explains on the official blog that unregistered apps distributed outside Play can also be registered in the same console.
According to the registration guide for open-source repositories, a developer distributing a new app with their own signature only needs to register that certificate's fingerprint. If the repository re-signs the app, the developer retrieves the distributed APK from the repository after publication and also adds the repository's certificate fingerprint. If the app has been installed on 50 or more Android devices from that repository before the addition, the developer may be asked to verify ownership.
Even when a re-signed version has already been published, the fingerprint is taken from the APK obtained from the repository. The developer selects the matching key in the console based on the value extracted from it. For apps with fewer than 50 known installs, there is a procedure for entering the fingerprint and adding the key.
To verify ownership, the developer adds a string specified in the console to assets/adi-registration.properties in the source and publishes a new version to the same repository. After obtaining the APK signed by the repository, the developer submits it to the console. Even if the repository manages the key, the developer can proceed with verification using a new version signed through the actual publication channel.
Distributors also have preparations to make. First, matching the package name and signing certificate of each distributed app through the Android Developer ID Status API can narrow down the developers who need to register. After that, Google's distributor guide explains, the same check can be run when accepting new apps or updates and when a signing key changes.
Distributors that integrate the Android Developer Console API and obtain developer authorization via OAuth 2.0 can register on a developer's behalf. They can register package names and signing certificates under the developer's account and can also automate ownership verification for signing keys managed by the store. When asking a repository to act on a developer's behalf, the developer account under which the app is registered must be identity-verified, according to the registration guide.
Initial setup to allow unregistered apps, and updates
Google explains in the FAQ that apps registered by verified developers can be installed the same way as before, whether from alternative stores or downloaded directly from a website. According to Google's announcement, millions of apps have been registered since the verification process was opened widely in March 2026, and they account for more than 99% of Android app installs worldwide. The period covered by those figures and how they were counted have not been disclosed, nor have breakdowns by distribution channel or region.
In a brief report dated November 19, The Verge's Tech section covered developer backlash over the early rollout and the waiting period users face. According to Google's Android Help, the wait applies the first time a user enables, on a supported device, the advanced procedure that allows apps from unverified developers, and it takes 24 hours. After the wait, the setting can be enabled for 7 days or indefinitely, and a warning appears when installing affected apps.
Google's registration guide says open-source repositories can continue to list unregistered apps. Even for unregistered apps already installed, updates on devices and distribution channels covered by the program will be subject to verification. To update, the device setting that allows apps from unverified developers must be enabled, or Android Debug Bridge (ADB), used for development and testing, can be used. Google explains in the FAQ that installs using ADB are not subject to the wait.
For handing apps to a small number of people, there is a limited distribution account that students and hobbyist developers, among others, can use. Google raised the sharing cap, set when it was introduced in August 2026, from 20 devices to 50. According to the limited distribution guide, apps can be shared only with devices that users have explicitly approved, up to a maximum of 50. The 50 known installs mentioned in the registration steps for existing re-signed apps refers to the number of installs of that app that Google is aware of.
Limited distribution accounts are free and reportedly do not require a government-issued ID. Use requires two-step verification on the Google account, a payments profile that holds the legal name and address, and a contact email.
For those who keep distributing publicly available apps, differences in preparedness will come down to whether they can confirm that the APK reaching users is registered when accepting new versions or changing signing keys. If developers and distributors catch registration gaps through pre-release checks and complete the necessary registrations, users will not face additional steps for developer verification when installing that APK.
Sources
- Android Developers' Blog: Expanding Android developer verification in 2027
- Android Developers: Resources for app distributors
- Android Developers: Register your app on open-source repositories
- Android Help: Allow app installs from unverified developers
- Android Developers: よくある質問
- Android Developers: Register for limited distribution on Android devices
- The Verge: Android’s new sideloading requirements take effect globally in January 2027.
推奨Slug
android-developer-verification-global-rollout
画像・図解案 (with Generative AI Prompts)
アイキャッチ
- Prompt:
Wide editorial photograph for a technology news article, a modern Android-style smartphone on a matte graphite desk next to two translucent cards carrying distinct abstract circuit patterns, suggesting app files delivered through different stores and paired with separate signing certificates. Realistic glass and brushed metal, raking daylight with restrained green highlights, clean composition with the main scene centered for flexible cropping. No text, logos, identifiable app icons or interface screenshots, 16:9. - Filename:
android-developer-verification-rollout.webp
- Prompt:
挿絵
- Prompt:
Editorial concept illustration for a developer audience, two matching rounded app-file tiles shown side by side, one bearing a blue embossed circular seal and the other bearing a copper triangular seal, illustrating different signing certificates on packages for the same app. Use clear object silhouettes, restrained modern colors, and an uncluttered neutral ground. No real company logos, words, letters, numbers or UI elements, 3:2. - Filename:
android-apk-signing-certificates.webp
- Prompt:
インフォグラフィック
- Prompt:
Create an unlabeled vector-style editorial timeline template with three spaced stations, with distinct icons suggesting a regional launch, a group of storefronts, and a larger group of storefronts. Leave ample blank space around each station for a human editor to add dates and store names. Thin connectors, high contrast, ivory background, restrained dark green and charcoal. No generated words, logos or numerals, 16:9. - Filename:
android-verification-store-timeline.webp
- Prompt:
タイトル案
- Google Playなど7ストアで1月に始まるAndroidの開発者確認、他ストアにも3月までに適用予定
- Androidアプリを普段どおり入れ続けるには、配布先が再署名した版の証明書も登録する必要がある
- Androidの開発者確認が2027年1月から世界へ、APKを再署名する配布元はどう備える
