F-Droid 2.0: What Changed—and Who Should Wait to Update

F-Droid announced version 2.0 on September 24 as a redesign of its Android app catalogue. The changes reach beyond the home screen: the update adds new discovery and search tools, changes how installs are approved, and moves background updates away from the F-Droid Privileged Extension. Whether to update depends on which older features and Android version a person relies on.

F-Droid says users who depend on its panic-trigger app-wiping feature may want to postpone. Android 6 is also outside the new release’s support range. For everyone else, rollout status is a separate question: as checked on October 13, the official F-Droid package listing showed version 2.0.2 (2000052) as a beta added October 12, not proof that every existing client has received a stable update.

Two public threads show the launch drew attention in their communities. An October 12 snapshot of the r/Android discussion showed 1,330 votes and 92 comments; the Hacker News thread showed 1,465 points and 421 comments. These post-level counts do not measure app adoption, represent a user survey, or establish broad agreement about the redesign.

Finding and managing apps

The old navigation gives way to three main areas: Discover, Search, and My Apps. F-Droid says Discover highlights newly added, recently updated, and most-downloaded apps. The My Apps screen brings installed apps, updates, and possible issues together, while Settings and Nearby Swap remain reachable from the top bar. Nearby Swap remains available there, but the announcement says a redesigned Nearby-sharing implementation was still in progress and missed the initial 2.0 release. Anyone installing the client mainly for a revamped nearby-device sharing system should not assume that work shipped with the broader redesign.

Discovery is more detailed: the Games category now separates 17 genres, and search covers app descriptions, categories, and translations as well as names. F-Droid highlights improved Chinese, Japanese, and Korean search, saved queries, and filters for category, device compatibility, and anti-features. Those tools help someone who knows what an app does but not its name—for example, searching by category while excluding apps that use non-free network services.

Installs and updates work differently

F-Droid 2.0 uses Android’s session installer for background updates on recent Android versions, according to the project. The F-Droid Privileged Extension (FPE) is no longer supported: even if it is installed, version 2.0 will not use it. The release describes this as a move toward Android’s built-in installation path, but it does not establish identical behavior across every manufacturer, custom ROM, or device configuration.

On supported devices, F-Droid says a new pre-approval API lets someone confirm an installation before the app has finished downloading. The release also says update checks and installations happen automatically by default, while existing update preferences are respected. Users who want to trigger a manual check can find that action in the overflow menu on My Apps; the old pull-to-refresh gesture is now for scrolling. Data-use settings have also been reorganized. F-Droid says they let users choose what gets downloaded and when, a practical concern for people on limited mobile plans, with strict network-privacy needs, or using devices that slow down during background work. Since update behavior and settings have changed, those readers should revisit the data controls rather than assume every previous choice maps to the same screen.

The package page lists Android 7.0 or newer as a requirement for the 2.0.2 beta. F-Droid says Android 6 support was dropped because a needed fix was added in Android 7. Older F-Droid releases continue to work on older Android versions, but the announcement does not promise that every old release will keep receiving updates.

What the privacy changes do—and do not do

F-Droid says its panic features remain in version 2.0, but the app-hiding disguise is narrower. It changes the app’s icon and name; it does not remove the app from Android’s Apps settings, and F-Droid says forensic inspection can still detect it. The feature is a basic disguise, not a way to make the app invisible.

A different panic feature has not returned: removing and wiping apps in response to a trigger app such as Ripple. F-Droid says some people rely on this for privacy and personal safety and acknowledges that maintaining it requires specialized work. Its release says users who depend on the existing app-wiping behavior may postpone updating while the project evaluates whether to restore it. That is a specific feature gap, not evidence that every privacy feature was removed.

Who should wait?

If app-wiping triggered by Ripple is part of a safety plan, F-Droid’s own advice is to wait rather than assume version 2.0 preserves that behavior. Android 6 users cannot install the new release; they can remain on an older compatible client, with no assurance here about future maintenance. Anyone who depends on FPE should also confirm what their particular Android build supports before changing versions, since F-Droid’s announcement describes session-installer support in general terms rather than testing every device.

For other users, the practical check is to confirm the phone runs Android 7 or newer and see which version the F-Droid client itself offers. The package page warns that downloading an APK directly will not provide update notifications and is less secure than installing through the client. Because the October 13 listing labels 2.0.2 a beta, the listing alone should not be read as a stable-rollout notice. A person who does not rely on the removed wipe behavior can then weigh the discovery and update changes against the beta status shown for their device.