F-Droid 2.0 Modernizes as Google Tightens Android Rules

F-Droid announced version 2.0 on September 24, giving its open-source Android app store its largest overhaul in a decade just as Google prepares new rules for software distributed outside Google Play.

The release bundles the visible repairs users will notice first: Material Design, three main sections called Discover, Search and My Apps, narrower categories, and search across descriptions and translated content. Underneath, key parts of the client have moved to Kotlin, with the interface built using Jetpack Compose. F-Droid says the migration should help it deliver improvements faster in future years.

That combination makes 2.0 a useful case study in what an alternative app store actually needs to remain an alternative. A repository can contain excellent software and still lose users if discovery is poor, installation resembles paperwork, or its codebase becomes difficult to maintain. Meanwhile, the operating-system owner can improve one part of third-party distribution while placing a new checkpoint somewhere else.

F-Droid now occupies both halves of that sentence.

A Decade of Interface Debt Arrives at Once

The previous client carried five navigation destinations, broad categories and search that leaned heavily on app names. The installation flow also required users to tap Download, wait, and then confirm Install. How-To Geek's account of the redesign describes 2.0 as a ground-up rebuild that reduces navigation to three destinations and adds description-based search and filters.

Those changes repair an old discoverability problem. People looking for an open-source substitute for a familiar proprietary app may know the function they need without knowing the project's name. Searching descriptions for a password manager or map application serves that user better than expecting them to arrive with the package name already copied to their clipboard, a ritual beloved mainly by package managers and nobody's relatives.

The stale interface had consequences outside the official client. MakeUseOf reports that some users adopted alternatives such as Droid-ify, which presented F-Droid's catalog through a more polished interface. It also says version 2.0 followed more than a year of work and 14 test releases.

Droid-ify offers a useful comparison because it separates the repository from the storefront. Community-built clients can compensate when an official interface falls behind, preserving choice at the presentation layer. Their limit is equally clear: another client cannot change Android's system installation rules. A better shop window helps only while the operating system permits customers through the door.

The Kotlin and Jetpack Compose rewrite also concerns project labor. Using Android's current development stack may enlarge the pool of contributors who can understand the client and reduce the cost of future interface work. That is an inference rather than a demonstrated result. The available reporting supplies no contributor counts, maintenance-time measurements or funding information, so 2.0 cannot yet prove that modernization will produce a healthier maintainer pipeline. It gives that pipeline a more current codebase to work with.

Regulation Improved the Plumbing

F-Droid credits the European Union's Digital Markets Act with enabling a unified installation service and a pre-approval API. Users can approve an installation when requesting it instead of waiting for the download to finish before approving another step. Version 2.0 also supports simultaneous downloads and automatic update installation.

F-Droid told The Register that this brings installation on official Android devices closer to the experience offered by the built-in store. That comparison has a precise boundary. Google Play begins with platform integration and an established relationship between Google and registered developers. F-Droid needed regulatory pressure to obtain system plumbing that reduces the usability gap.

The result illustrates what interoperability rules can change. They do not make two stores equal, but they can prevent routine operating-system functions from becoming an exclusive convenience of the platform owner's store. Every removed confirmation screen lowers the patience tax imposed on people choosing another distributor.

Yet Google is also preparing a developer-verification regime for Android software distributed beyond Play. Google announced the expansion in August 2025, and The Register reports that the rules are due to reach users worldwide in 2027. Under the described options, broad distribution requires a one-time $25 payment, government-issued identification and acceptance of Google's terms. A free limited-distribution route avoids the ID requirement but caps distribution at 20 authorized devices. Google has also said unverified developers will remain installable through an advanced installation flow.

The strongest security case for verification is straightforward: tying widely distributed software to an identified developer may create accountability and make abuse harder to repeat anonymously. The governance problem sits in who administers that identity layer. Developers choosing a repository outside Google Play would still need Google's permission structure for broad reach, including developers whose reasons for avoiding identification may involve privacy, personal safety or political risk rather than malware.

F-Droid operates without user accounts so it does not need to identify or track its users. Its board member Marc Prud'hommeaux warned in September 2025 that the proposed registration system would end F-Droid and similar free-software distribution “as we know them today.” That forecast should be read with its date attached. Google later preserved an advanced route for unverified installations, so the project faces an evolving constraint rather than a confirmed shutdown. The remaining questions concern how burdensome that route becomes and whether ordinary users will traverse it.

This creates the release's central tension. EU intervention has helped F-Droid approach the built-in store's installation experience, while Google's verification policy could make access to that improved experience harder for unregistered developers. One policy reduces friction at install time; the other moves friction upstream into developer identity and distribution eligibility. A modern interface cannot settle that governance dispute.

Polish Carries Its Own Trade-Offs

Version 2.0 also changes features used by a smaller, privacy-sensitive part of the community. Android Police reports that pull-to-refresh update checks have been replaced by automatic checks, although manual checking remains in the overflow menu. The dedicated Use Tor option migrates to generic proxy settings, with Tor VPN recommended instead.

The panic feature has narrower coverage too. Users can disguise F-Droid's name and icon, but the app remains visible in system settings and forensic analysis. The previous ability to remove apps through a panic trigger is absent for now; the report says the team proceeded without it because the feature had a small user base.

These choices show the maintenance arithmetic behind a redesign. Supporting rarely used security features consumes development and testing capacity, especially during a rewrite. Shipping without them can move the main client forward sooner, while exposing users who depended on those features to a weaker threat model. The reporting does not establish how many people relied on them or when full functionality might return, so broad claims about F-Droid abandoning privacy would outrun the facts.

Release availability has also been described inconsistently. MakeUseOf said 2.0 was available from F-Droid's versions page during a staged rollout, while Android Police described the downloadable build as an alpha still missing features. Users who depend on Tor or panic behavior should therefore check the build status and included functions before replacing their current client.

F-Droid 2.0 gives the project a cleaner storefront, better search and a codebase aligned with contemporary Android development. The DMA gives it a smoother route from storefront to installed app. Google still controls the road beneath both, and the consequential test will arrive when developer verification meets the distributed, pseudonymous and occasionally unruly software culture that F-Droid was built to serve.