Google Android restrict app sideloading

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.^[1][2] 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.^[3][4]

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.^[5]

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."^[1] 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.^[6] These steps appear to have laid the groundwork for Google's new, broader enforcement.

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.^[1] 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.^[2][3] Apps must also be registered with their signing keys to prove ownership.^[3]

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.^[1]
• 2027: Targeted global rollout, eventually covering nearly all certified Android devices.^[1][2]

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.^[3] However, uncertified devices often face their own sideloading and app compatibility issues, due to SafetyNet/Play Integrity checks.^[3]

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.^[1][3] 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.^[1]

Google emphasized that it will not review or police apps distributed outside the Play Store for content, only verify developer identities.^[1][2] 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.^[1][2]

As backlash mounted, Google took steps to clarify the changes. In late September 2025, an Android Developers Blog Q&A by Android security director Matthew Forsythe reiterated that sideloading is "fundamental to Android" and "absolutely not" going away, stressing the policy's focus on verifying developer identities rather than limiting user choice.^[7] Google assured developers that common workflows remain unaffected; for example, installing test apps via ADB will not require verification.^[7] The company also introduced a free "limited distribution" developer account as well as a new Android Developer Console for students, teachers, and hobbyists, allowing them to publish apps without paying a fee or providing government ID.^[7][8] However, these accounts come with significant app distribution restrictions, namely a strict cap on the number of devices that can install their apps. To enforce this restriction, any user of a hobbyist app must retrieve a unique device identifier, and the developer must whitelist that device in the Android Developer Console before the app can be installed.^[8] This two-way device registration limits "free tier" apps to a small, known group of people, whereas anyone aiming to reach a broad audience will need to upgrade to a fully verified paid account.^[8]

Google also detailed how the verification enforcement will work. A new system service called the Android Developer Verifier will check each app at installation to confirm its package name and signing certificate are registered with Google.^[8] Common apps from verified developers can be installed offline thanks to a cached on-device list, but an active internet connection will be required to verify less common apps that aren't in the cache.^[8] To accommodate third-party app stores, Google is developing a "pre-auth token", a cryptographically signed blob that an alternative app store can pass to the system to pre-verify apps without repeated network calls.^[8] Enforcement of these rules will debut in Android 16 QPR2 (the second quarterly update of Android 16, expected in late 2026), and Google will also update Play Protect on older Android versions to implement similar checks via Google Play Services.^[8] Notably, Google is carving out exceptions for enterprise scenarios: apps deployed through enterprise mobile management on managed work devices will install without developer verification (the assumption being that an organization's IT admin is taking responsibility for those apps' safety).^[8] However, truly offline use cases may prove tricky. Google has noted that entities with devices kept entirely off the internet will need to "determine for themselves" how to handle verification requests (i.e. such devices must periodically connect online to update the trusted app list).^[8]

The announcement sparked backlash in online communities. On Reddit, users accused Google of gradually eroding Android's openness.^[9] 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.^[9][10]

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 (or can safely) submit government IDs to Google.^[11][12] Open-source communities, including GrapheneOS developers, argued this would discourage FOSS development and give Google exclusive control over Android's ecosystem.^[12][13]

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.^[1][3] Critics countered that determined attackers could still exploit stolen IDs, and that this introduces a "choke point," giving Google leverage over all app installs.^[4]

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.^[6][12]

By late September 2025, open-source app developers escalated their opposition. The volunteer-run F-Droid app repository warned that Google's plan, if implemented, "will end the F-Droid project and other free/open-source app distribution sources as we know them today."^[14] F-Droid cannot comply with a centralized registration regime; its team builds apps from source code and signs them with its own cryptographic keys so it cannot simply have each apps' original author register and hand over a signing identity without fundamentally changing F-Droid's model.^[15]

Google offered a limited concession for situations where the same app exists in multiple stores: in rare cases, it will allow duplicate package names if one version has a significantly smaller user base (meaning the developer of the less-installed version might be asked to change their app's identifier).^[8] In practice this would do little to help F-Droid. Many apps on F-Droid share a package name with a more popular Google Play version, so Google's policy would effectively treat the Play developer as the rightful owner and force the F-Droid variant to disappear or rebrand, an outcome that violates F-Droid's core philosophy.^[8]

The F-Droid team argued that Google is using security as a pretext to consolidate power over software distribution, especially since even the Play Store has repeatedly hosted malware despite all its checks.^[14][15] In an official statement, F-Droid appealed to regulators and competition authorities around the world, citing the EU's Digital Markets Act, to scrutinize Google's proposal and protect the ability of alternative app stores and open-source developers to operate freely.^[15]

Privacy and free-speech advocates also raised concerns. Requiring every app developer to verify their real-world identity would eliminate anonymity for creators of apps used in sensitive contexts, for example by political dissidents or whistleblowers.^[16] Google acknowledged that legitimate reasons for developer anonymity exist and stated it won't publicly disclose developer information, but the company did not promise to withhold that information from governments should they seek it.^[8] Google's stance is that the status quo (allowing anonymous app distribution) poses risks it can no longer accept.^[8]

Some former Android team members have also lamented the platform's direction. Jean-Baptiste Quéru, a founding Android engineer who led the Android Open Source Project, remarked that when he worked on Android, goals included keeping the app ecosystem "as open as the web" and letting users run their own builds, but "12 years later, this seems to have all died".^[17]

A website titled https://keepandroidopen.org/ was created to push back against Google's decision. It was endorsed by F-Droid in a blog post as a way for users to take action.