F-Droid 2.0: A Fresh Start for Open Android

Open F-Droid to find a small utility, and the old experience could feel like rummaging through a well-labeled cupboard that had outgrown its shelves. The catalog had grown to thousands of free and open source software (FOSS) apps, but the tools for browsing them had not always kept pace. On September 24, 2026, F-Droid announced the rollout of version 2.0 after more than a year of work and 14 test releases. It is the project’s biggest client update in a decade, and the interesting part is not the new paint. F-Droid has rebuilt the paths people use to discover, install, and maintain apps.

Why this release matters

F-Droid is both an app repository and an app client. A repository is a catalog that stores information about software and provides the files needed to install it; the client is the Android app that lets you browse that catalog and manage what is on your phone. Unlike a typical commercial storefront, F-Droid focuses on free and open source Android apps and does not need to track your behavior to recommend something to you.

What does F-Droid 2.0 actually change for someone who has never used it before? The answer starts with a much clearer map. The main navigation now centers on Discover, Search, and My Apps. Categories live inside Discover, while settings and Nearby sharing sit in the top bar instead of competing with the primary destinations.

That sounds like a small rearrangement. It is not. Good navigation reduces the amount of hidden knowledge a new user needs before the catalog becomes useful.

Finding apps without guessing their names

The redesigned Discover screen gives the repository a front door. It can highlight recently added and recently updated apps, along with popular downloads that might otherwise remain buried. The goal is not to turn F-Droid into an endless feed, but to make browsing possible when you know what you need without knowing the exact app name.

Categories have also become more specific. Broad labels are now joined by narrower groupings for tools such as virtual private networks, firewalls, password managers, launchers, and navigation apps. Higher-level categories group related topics together, giving beginners an easier starting point before they move into more specialized lists. The Games section is a useful example: F-Droid 2.0 divides it into 17 genres instead of placing every game in one oversized bucket.

Search now looks beyond titles. It can inspect descriptions, categories, and translated content, which means you can search for what an app does rather than trying to remember what its developer called it. Recent searches are saved, and support for Chinese, Japanese, and Korean writing systems has been improved.

Filtering makes the same idea more powerful. Imagine looking for an action game that works on your phone while excluding apps that depend on non-free network services. You can combine those conditions instead of opening each listing one by one. An anti-feature is a metadata label that warns about a characteristic some users may want to avoid, so filters can help turn personal preferences into a practical shortlist. New onboarding screens explain these tools as they appear rather than hiding them in a settings maze.

The install flow finally feels less awkward

For years, installing from a third-party Android app store often involved an awkward pause: download the app first, then wait for Android to ask whether you approve the installation. F-Droid 2.0 uses Android’s newer session installer to bring those steps closer together.

An Android package is the installable file or bundle that contains an app. A session installer treats the operation as one managed transaction, staging the package and then asking Android to complete the installation. F-Droid also uses Android’s pre-approval application programming interface, or API. An API is a defined way for one piece of software to request a service from another.

On supported devices, the sequence now looks more like this:

Choose an app
 ↓
Approve the installation
 ↓
Download the package
 ↓
Android completes the install session

That change matters because the approval can happen before the download finishes. You are not left staring at a progress bar only to discover that another prompt is waiting at the end. Devices that do not support the newer path can still use the conventional Android installation flow, but F-Droid now has one installer design that works whether the operating system included F-Droid or you installed the client yourself.

The same foundation supports background updates on recent Android versions and allows several downloads or updates to be handled together. My Apps becomes the place to see what is installed, what needs attention, and whether Android has reported a problem such as a changed signing key.

Updates become quieter

F-Droid 2.0 checks for updates automatically and installs them by default, while preserving existing preferences for people who want more control. The familiar pull-to-refresh gesture no longer triggers a repository refresh; it is reserved for scrolling. Manual checking remains available through the overflow menu on My Apps.

This is a subtle but meaningful change. Instead of asking users to remember a maintenance gesture, the app can handle routine checks in the background. At the same time, redesigned data-use settings make it easier to decide when downloads are allowed, which matters on expensive mobile connections, limited data plans, or older phones that slow down during background work.

A modern codebase underneath

The visible redesign rests on a technical rewrite. F-Droid 2.0 uses Kotlin, a programming language widely used for modern Android development, together with Jetpack Compose, Android’s Kotlin-based toolkit for building interfaces. Compose makes screens more declarative: developers describe what the interface should look like for a given state, and the toolkit handles much of the updating work.

The project also aligns more closely with Material Design, Android’s design system for layout, color, motion, and interaction patterns. That helps the app feel familiar without turning it into a copy of another store. More importantly, current Android tools lower the barrier for contributors who have learned the platform in the last several years, while reducing the maintenance burden left by an older codebase.

There is a compatibility cost. F-Droid 2.0 requires Android 7.0 or newer because some of its newer installation tools depend on fixes that arrived in Android 7. Devices running Android 6 will need to remain on an older F-Droid release. The F-Droid Privileged Extension, a system-level helper used by some installations in the past, is also not supported by the new client; the session installer now carries more of that responsibility on recent Android versions.

Privacy features, trade-offs, and unfinished work

A major redesign earns trust by explaining what it changes, including the uncomfortable parts. Tor, a privacy network that routes traffic through several relays, is still supported, but its settings have been simplified. Automatic detection has been removed in favor of standard proxy settings, with Tor VPN recommended for users who want a more guided setup.

The app-hiding feature has also been made more honest. Instead of pretending to be a working calculator, the disguise changes the icon and app name only. F-Droid can still appear in Android’s app settings and could be discovered through forensic inspection, so the feature should be treated as low-profile masking rather than complete concealment.

The ability to erase apps in response to a panic-trigger application is not included in the initial 2.0 release. That feature serves a small but important group of users with heightened privacy and personal-safety needs, so anyone who depends on it has a real reason to postpone the upgrade. Nearby, F-Droid’s device-to-device app-sharing feature, is also being rebuilt and is not yet part of the first release.

More than a new coat of paint

F-Droid 2.0 is a redesign, but its deeper purpose is maintenance. User research, accessibility work, testing, translations, security review, community feedback, and a modern Android codebase all shape how quickly the project can respond to the next problem.

After a decade, F-Droid is not merely making its catalog prettier. It is adapting to modern Android installation rules while keeping privacy-respecting discovery at the center. The first screen is easier to navigate, the installer is less interruptive, and the code underneath is less tied to yesterday’s Android. That makes version 2.0 feel less like a final makeover than the foundation for the next chapter of open Android software.