Visit f-droid.org today and the first thing you see isn't the app catalog. It's a red banner: "F-Droid is under threat. Google is changing how you install apps on your device. We need your help."

That banner is not fundraising theater. On September 30, 2026, Google switched on Android Developer Verification in four countries — Brazil, Indonesia, Singapore, and Thailand — and Indonesia is one of them. If you run stock Android on a certified device here, the rules for installing apps outside the Play Store have already changed under your feet.

What actually changed

Under the new policy, every app installed on a certified Android device must be registered by an identity-verified developer — including apps you sideload yourself from an APK. After the deadline, attempting to install an unverified app hits a system-level block with no override in the normal install flow.

Google's stated reason is straightforward: deterring scam and malware installs, which disproportionately arrive via sideloaded APKs. The mechanism is a developer program where you verify your identity and register your package names with Google, whether you distribute through Play, another store, or a direct download.

Enforcement is rolling out in stages. The four launch countries went live on September 30, 2026. Google has moved the broader expansion — covering all apps on certified devices globally — to 2027. There is a "limited distribution" tier for hobbyists and students (email-based, capped at 20 devices), and Google promised an "advanced flow" for experienced users who want to sideload unverified apps with extra safeguards.

Why F-Droid is uniquely exposed

Most alternative stores distribute your APK signed by you, the developer. F-Droid doesn't work that way. For the bulk of its catalog, F-Droid builds apps from source and signs them with its own key — community estimates put that at roughly 85% of listed apps.

Developer verification ties a package name to a specific developer's signing key. F-Droid's key is not the developer's key. So for the vast majority of its catalog, there is currently no coordination mechanism between thousands of independent maintainers and F-Droid to register under the new system — because that mechanism does not exist yet.

F-Droid's board has called this an existential threat, not a paperwork inconvenience. Reproducible builds are the clean technical answer — F-Droid could then ship the developer-signed APK directly — but reproducible-build coverage across the catalog is only partial today. And many F-Droid developers operate anonymously or in jurisdictions where handing identity documents to Google creates real personal risk.

What breaks in practice

Here is the concrete damage, based on how enforcement is behaving in the launch countries:

  • New installs of unverified APKs are blocked by default on certified devices — apps from GitHub releases, F-Droid, and community-patched packages are all affected.
  • Updates can fail too. Apps installed before the rollout keep running, but updating them may require going through a bypass.
  • The signing-key mismatch is the tripwire. Any APK whose signing key doesn't match the registered developer is treated as unverified.

What keeps working: everything from the Play Store, apps installed before enforcement (they keep running), and installs done over ADB, which Google explicitly carved out of the requirement.

The field guide: what still works

If you're in Indonesia on stock Android and you sideload, you have four practical paths, roughly in order of convenience:

1. The Advanced Flow. Google's promised path for experienced users. In practice it is deliberately high-friction: enable Developer Options, authenticate, restart the phone, and wait 24 hours before the system permits sideloading — for seven days or indefinitely. Details were still vague right up to the enforcement date, and F-Droid has said no workable version appeared before the deadline. Treat this as the official-but-annoying route.

2. ADB installs. adb install is explicitly exempt from the verification requirement. If you're comfortable with a terminal — and if you read this blog, you probably are — this is currently the most reliable way to sideload on a certified device. It was always the power user's route; now it's the necessary one.

3. Custom ROMs. GrapheneOS, LineageOS, and other custom ROMs run on uncertified builds, so the verification mandate doesn't hit them the same way. This is the nuclear option with the most setup cost, but it's also the only path that removes Google from the decision entirely.

4. For developers: reproducible builds and registration. If you ship on F-Droid, check your reproducible-build status and push toward it — it's the only path where your own key stays on the artifact. If you're in an affected region, register your package name in Google's system even if you never touch the Play Store, and don't change your applicationId or signing setup mid-transition.

The bigger picture

The opposition has been loud. The Keep Android Open campaign — launched in October 2025 — published an open letter to Alphabet leadership in February 2026 that now carries signatures from more than 70 organizations across 23 countries, including the EFF, the Tor Project, Free Software Foundation Europe, Proton, and Nextcloud. Their argument: the verification requirement gives Google unilateral control over which software may run on certified Android devices regardless of how it's distributed.

Strip away the campaign language and the core tension is genuinely hard. Sideloaded APKs are a major malware vector, and Google's accountability-layer framing isn't absurd on its face. But Android's openness to sideloading was never a minor feature — it was the platform's fundamental differentiator from iOS, and the foundation under F-Droid, custom ROMs, and a decade of independent Android software. A policy that makes installing unapproved software deliberately inconvenient, gated behind identity registration with a single American company, changes what Android is, not just how it's administered.

There's a bitter irony in the timing, too. The same week enforcement began, F-Droid shipped version 2.0 — a full rewrite with a modern interface, audited and rebuilt after more than a year of work. The code was never the part under threat.

What to do now

If you're in Indonesia on a stock Pixel, Samsung, Xiaomi, or anything else with Google certification: your sideloading workflow has an expiry date on its current convenience. Learn the ADB route now, before the app you need to reinstall is the one that's blocked. If you maintain an app distributed outside Play, register your package name and look hard at reproducible builds. And if you think one company shouldn't hold the keys to what runs on two billion devices, keepandroidopen.org is where the pushback is being organized.

Android was the open one. That was the deal. Google just renegotiated it — starting here.