Google Sets September 30 Deadline For Android Developer Verification In Four Countries

Google Sets September 30 Deadline For Android Developer Verification In Four Countries

Google has announced that September 30, 2026, will mark the start of mandatory Android developer verification enforcement in Brazil, Indonesia, Singapore, and Thailand, introducing a significant change to how applications are installed on certified Android devices. The policy will apply not only to applications distributed through Google Play but also to those offered through app stores operated by major smartphone manufacturers including Samsung, Xiaomi, OPPO, vivo, Honor, and Transsion. Under the new framework, certified Android devices will block the standard installation of applications whose developers have not completed Google’s identity verification process. Certified devices are those that ship with Google services and Play Protect functionality, representing more than 95 percent of Android devices outside China, according to estimates cited by F Droid. While most consumers are expected to experience little disruption because verified applications will continue to install normally, the change introduces new requirements for developers, particularly those distributing software through independent and open source channels.

The verification system relies on a new device level service called Android Developer Verifier, which Google began deploying to Android 8 and newer devices in June 2026. The service checks whether an application is associated with a verified developer before allowing installation. After the September deadline, users in the four launch countries will be unable to install applications from unregistered developers through standard methods. Alternative installation paths will remain available, including Android Debug Bridge and an advanced sideloading process introduced earlier in the year. However, this process has been intentionally designed to add friction by requiring users to enable developer mode, restart their devices, wait 24 hours, and complete additional authentication steps before proceeding with the installation of unverified applications. Google plans to expand this advanced verification flow globally in August. Registration for developers opened in March 2026 and already covers nearly all installations occurring through Google Play as well as a substantial portion of installations originating from external sources. To complete registration, developers must provide legal identity details, including name, address, and contact information. Some applicants may also be required to submit government issued identification and prove ownership of their applications through APK files signed with private cryptographic keys.

Google is also introducing supporting tools designed to simplify compliance for developers and application marketplaces. New APIs scheduled for release in July will enable bulk registration, package name verification, and OAuth based delegation, allowing third party stores to assist developers in completing portions of the verification process. The company will additionally launch a limited distribution program that enters early access in July before becoming globally available in August. This option is aimed at students, hobbyists, and small scale developers, allowing applications to be shared with up to 20 devices without requiring government identification or payment. By contrast, standard developer registration will continue to require a one time fee of $25. Google states that these measures are intended to reduce malware distribution and combat social engineering schemes that persuade users to install malicious applications directly from external sources. The company has indicated that the four initial countries were selected because they have experienced elevated levels of app related scams and abuse originating from repeat offenders.

The initiative has generated considerable debate within the open source software community. F Droid, one of the most widely used repositories for free and open source Android applications, argues that the verification requirement threatens its operating model because many contributors distribute software under pseudonyms and may be unwilling to provide legal identities to Google. The broader Keep Android Open campaign, supported by more than 70 organizations across 23 countries, has also opposed the policy and called on Google to remove mandatory identity verification requirements for applications distributed outside Google Play. While Google’s introduction of advanced installation options and limited distribution accounts addresses concerns that sideloading could be eliminated entirely, critics maintain that the underlying issue remains unresolved. They argue that a single company would effectively control the smooth installation pathway for the overwhelming majority of Android devices outside China. Questions also remain regarding the appeals process for developers who may be incorrectly flagged, the retention and handling of identity information collected through the verification system, and whether repositories such as F Droid will be offered alternative compliance pathways that accommodate their unique development and distribution models.

Source

Follow the SPIN IDG WhatsApp Channel for updates across the Smart Pakistan Insights Network covering all of Pakistan’s technology ecosystem. 

Post Comment