Full story
Verification timeline set
Google says Android developer verification is on track for an initial launch later this year and will continue into 2027, with the protections beginning on September 30 in Brazil, Indonesia, Singapore, and Thailand.
“Starting September 30, users in Brazil, Indonesia, Singapore, and Thailand will see the developer verification protections”
In its update, Google said that since the registration process launched in March, it has verified “millions of apps,” including “nearly all installs on Google Play and a large majority of installs from outside of Google Play.”
Google will “begin by verifying app installations from the following stores” including Google Play, Honor (HONOR App Market), OPlus (OPPO App Market), Samsung (Galaxy Store), Transsion (Palm Store), vivo (V-Appstore), and Xiaomi (GetApps).
Behind the scenes, Google will automatically roll out a new system service called Android Developer Verifier (com.google.android.verifier) to Android 8+ devices, and it will “validates that an app is registered to a verified developer.”
Google also laid out that it will start granting early access to limited distribution accounts on the Android Developer Console in July, with a global launch in August, and it will launch the Android Developer ID Status API to streamline app registration.
Stores, sideloading, and accounts
Google’s plan ties enforcement to specific storefronts, with Ars Technica describing Google’s confirmation of which app stores are participating and its claim that verification will require identities of developers outside the Play Store just like it does for devs publishing on its platform.
Ars Technica reports that Google’s new developer console, released in March, invited external developers to pay $25 and verify their identities early, and it says developers who don’t register will find their apps cannot be sideloaded on Google-certified Android devices once verification has rolled out.
For users and developers looking for alternatives, 9to5Google says Google will roll out an “advanced flow” for sideloading applications from unverified developers this August, while also noting that users can alternatively use the Android Debug Bridge (adb) to install apps.
9to5Google adds that in “2027 and beyond,” Google will launch the Android verification requirement globally “after incorporating the feedback from our partners, users, and developer community.”
Frandroid frames the “advanced flow” timeline as a concern, accusing Google of promising a bypass that “will not be implemented before next September,” while Android will require that all apps be registered by validated developers at that same date.
Critics warn of lock-in
As Google prepares to extend verification worldwide from 2027, critics in the open-source ecosystem argue the policy threatens alternative app distribution models, with Frandroid saying F-Droid representatives accuse Google of lying about its intentions.
“F-Droid formally advises developers not to enroll in Google’s certification program”
Frandroid reports that F-Droid formally advises developers not to enroll in Google’s certification program, which it says will open next March, and it describes the situation as “a grave breach of trust” by Google toward the open-source community.
Korben’s coverage similarly argues that Google’s identity verification threatens F-Droid’s model, stating that F-Droid signs the apps itself and that this “directly conflicts with Google's new single-signature rule.”
Korben also claims that 37 organizations including the EFF, FSF, and Vivaldi signed an open letter against the project, and it says a Change.org petition gathered 64,000 signatures from developers.
In response to the security rationale, Google’s approach is described as phased—Android Developer Verifier starting in April 2026 and enforcement beginning in September 2026 in Brazil, Indonesia, Singapore, and Thailand—while ITdaily says users attempting to install unregistered apps will need additional steps such as ADB or an advanced flow.
