Google plans to restrict sideloading of Android apps

On 25 August 2025, Google announced that starting in 2026, the company will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026 with global enforcement targeted for 2027. This marks a significant change to Android's long-standing support for sideloading apps and has sparked debate among developers, consumers, and digital rights advocates.

Background

The open-source Android operating system has historically allowed sideloading, the installation of apps from outside the Google Play Store. Users would need to enable "unknown sources" in their device settings to make this possible. This level of openness distinguished Android OS from Apple's restrictive iOS that does not allow sideloading. Alternative android app stores, such as F-Droid, Amazon's Appstore, and web downloads from sites like APKMirror, thrived under this model.

Over time, Google introduced restrictions to the open-source operating system citing security concerns. In 2023, Google began requiring Play Store developers to verify their identities in order to reduce "impersonation and malware." Android versions 13 and 15 further limited what sideloaded apps could do, blocking access to sensitive permissions for apps not installed through Google's channels. These steps appear to have laid the groundwork for Google's new, broader enforcement.

Timeline

On 25 August 2025, Google announced that apps can only be installed on certified Android devices if their developers have verified their personal identity with Google. Developers must register through a new Android Developer Console, pay a one-time $25 fee (except for hobbyists or students, who will have a separate free path), and provide identifying details such as legal name, address, and government-issued ID. Apps must also be registered with their signing keys to prove ownership.

The rollout will proceed in stages:

• October 2025: Early access program for select developers.
• March 2026: Verification opens for all developers worldwide.
• September 2026: Enforcement begins in Brazil, Indonesia, Singapore, and Thailand.
• 2027: Targeted global rollout, eventually covering nearly all certified Android devices.

The new system applies to certified Android devices which are phones and tablets that ship with Google Mobile Services (e.g., Pixel, Samsung, Xiaomi). Devices running uncertified AOSP builds or custom ROMs (e.g., GrapheneOS, LineageOS) are not subject to this restriction. However, uncertified devices often face their own sideloading and app compatibility due to SafetyNet/Play Integrity checks.

Google's response

Google framed this new policy as a necessary security measure to reduce malware, fraud, and impersonation. The company stated that malware is "50× more common outside the Play Store" and that anonymity allows bad actors to evade accountability. Suzanne Frey, VP of Product for Android, likened the change to an ID check at the airport: verifying who the developer is without inspecting app content.

Google emphasized that it will not review or police apps distributed outside the Play Store for content, only verify developer identities. Google's move gained support from some industry and institutions, including the Developers Alliance, Brazil's banking federation FEBRABAN, and Indonesia's Ministry of Communication and Informatics, all of which praised the move as protecting users from fraud.

Consumer response

The announcement sparked backlash in online communities. On Reddit, users accused Google of gradually eroding Android's openness. Many argued that Android is becoming indistinguishable from iOS, with some stating that they may switch to operating systems from Apple or Linux since Android's openness was its key advantage.

Independent developers raised concerns that hobby projects or sensitive apps (e.g., protest tools, ad-blockers) would be stifled since not all creators are willing to submit government IDs to Google. Open-source communities, including GrapheneOS developers, argued this would discourage FOSS development and give Google exclusive control over Android's ecosystem.

Conversely, some security experts and industry groups welcomed the move, calling it a reasonable compromise that still allows third-party distribution while deterring anonymous malware authors. Critics countered that determined attackers could still exploit stolen IDs, and that this introduces a "choke point," giving Google leverage over all app installs.

Regulators had not formally responded within the first 24 hours, but commentators noted that the change resembles Apple's Developer ID system on macOS and that it may be Google's way of tightening control while remaining compliant with the EU's Digital Markets Act.