F‑Droid warns Google verification threatens alternatives

Android app installation is about to get a lot more centralized — even outside the Play Store. Google is rolling out a system that ties app installs on certified Android devices to verified developer identities, and F‑Droid says that turns Google into the checkpoint for software it doesn’t even distribute. That is the real fight here. Not whether malware is bad — everybody agrees on that — but whether Android still counts as open if Google gets to approve the identity layer for almost every app. ### What did Google actually change? Google first announced in August 2025 that certified Android devices would require apps to be registered by verified developers, even when those apps come from third-party stores or direct downloads. In March 2026, Google started rolling verification out to developers through Play Console and a new Android Developer Console, with user-facing enforcement set to begin in September 2026 in Brazil, Indonesia, Singapore, and Thailand, then expand globally in 2027. ### Why is F‑Droid so alarmed? F‑Droid’s argument is pretty simple — its whole model is that developers can publish free and open-source Android apps outside Google’s commercial store, and users can install them without asking Google first. In its February open letter, F‑Droid said the new rules would require developers everywhere to register a rival store or a plain website. ### Is Google banning sideloading? Not exactly. Google’s line is that sideloading stays, but unregistered apps will face extra hurdles. For most users, Google says nothing changes unless they try to install an app from an unverified developer. At that point, Android will require either ADB or a new “advanced flow” meant for power users. ### So what is the “advanced flow”? It is basically a deliberate obstacle course. Google says users who want to install apps from unverified developers will need to enable developer mode, confirm they are not being coached by a scammer, restart the phone, wait one day, then come back and reauthenticate with your phone. ### Why does Google think this is necessary? Google says the threat is repeat malware authors and financial scammers hiding behind anonymity. In August 2025 it said it saw over 50 times more malware from internet-sideloaded sources than on Play, and by March 2026 it said recent analysis showed over 90 times more malware from sideloaded sources than on Google Play. That is the core case for identity checks at the OS level. ### Why do critics still think this changes Android’s character? Because the issue is not just security warnings — it is dependency. F‑Droid says future rival stores will be structurally weaker if every developer still has to go through Google to reach users on certified devices. Even if Google never reviews app content, controlling the registration problem, not just a safety feature. ### Does Google offer any carve-outs? A few. Google says developers can still distribute where they want, and it is creating limited-distribution accounts for students and hobbyists. But those are still Google-run paths, which is exactly what F‑Droid objects to. The disagreement is not over whether an exception exists. It is over who gets to grant it. ### Bottom line? Google has not killed alternative Android stores. But it is moving the trust checkpoint for app installation closer to the operating system itself — and closer to Google. If you think Android’s openness means users can install software without Google sitting in the middle, F‑Droid’s warning makes sense. If you think scam prevention matters more than friction for niche distribution, Google’s case does too.