F-Droid 2.0 had pulled 543 points and 161 comments on Hacker News when this story was selected. The number shows how much interest remains in an Android app store outside Google Play. Yet the most consequential line in F-Droid's announcement is aimed at a much smaller group: anyone who relies on a panic trigger to wipe sensitive apps should postpone the update.
That warning sits inside F-Droid's largest app update in 10 years. The project says it spent more than a year rebuilding the client, put it through 14 test releases, and will roll version 2.0 out over the coming weeks. The result changes how people approve installs, find software, receive updates and conceal the store on a phone. It also shows what can fall out when a mature open-source app replaces its decade-old internals.
Approval can happen before the download
Android has long made stores installed by the user feel second-class at the moment that matters. A person could choose an app, wait for its APK to download, then face the system approval prompt. F-Droid 2.0 uses a unified session installer and requests approval earlier, so a supported device can ask for consent just after the person taps Install. F-Droid credits regulatory pressure and antitrust cases with helping open this path to alternative stores.
The underlying Android method is requestUserPreapproval(). Google added it in API level 34, the platform level for Android 14. The PackageInstaller documentation says an installer with REQUEST_INSTALL_PACKAGES permission may seek approval before committing an installation session. A rejected request abandons the session. If pre-approval is unavailable or unresolved, the installer can still use the usual commit flow.
That fallback matters because F-Droid runs in several arrangements. Some Android variants include it, while many people download the store themselves. Version 2.0 uses the same installer architecture across those cases. It no longer supports the F-Droid Privileged Extension, or FPE, even when that extension is present. The project says recent Android versions can run background updates through the session installer without FPE, according to its release explanation.
The practical gain has limits. Pre-approval arrived only with API 34, and Android may still require a person to act. F-Droid 2.0 itself supports Android 7.0 and newer, so the exact install flow depends on the operating system. The project's package page lists the 2.0.0 APK at 11 MiB and supplies its source archive, signature and build log beside the download.
Search now looks beyond an app's name
The old client's navigation has been reduced to Discover, Search and My Apps. Repositories, Settings and Nearby remain accessible from the top bar. Discover now mixes new and recently updated apps with the repository's most-downloaded entries, while My Apps collects installed software, available updates and reported problems. Those changes are described in the 2.0 release announcement, which says the store still does not track people to drive engagement.
Search can inspect descriptions, categories and translated text instead of matching names alone. F-Droid also says it improved matching for Chinese, Japanese and Korean writing systems and now stores recent queries. Someone looking for a firewall can now search for what the app does without already knowing its name. The package changelog confirms that description and translation search shipped in 2.0.0.
Browsing received more structure too. Games have been split into 17 genres, and broader meta-categories group related sections on the Discover screen. Filters can combine category, device compatibility and F-Droid's anti-feature labels. A user can, for example, request compatible action games while excluding software that depends on non-free network services. That example comes from F-Droid's filtering notes, rather than a claim that every listing carries perfect metadata.
Automation brings a sharper privacy tradeoff
Version 2.0 checks for updates in the background and fetches and installs them by default, while preserving existing preferences. Pull-to-refresh now scrolls the list. A manual repository check has moved to the overflow menu in My Apps. F-Droid's data controls still let people restrict when downloads happen, which matters on expensive mobile connections and on devices that slow down during background work.
The client can also process multiple downloads or updates at the same time. Its My Apps view can warn about problems such as a changed signing key, which gives the new installer a place to surface an issue before someone treats an update as routine. Both behaviors appear in the 2.0.0 package changelog, alongside the earlier approval prompt and expanded filters.
The privacy settings have changed along with the update machinery. F-Droid removed its unreliable Tor auto-detection and migrates the old Use Tor choice into generic proxy settings. It now recommends a Tor VPN for the easiest setup, while retaining manual proxy control and support for onion repositories. The project's privacy notes explain the migration and name TorVPN, Orbot and TorServices as parts of the current Android ecosystem.
F-Droid also narrowed its app disguise. The former option could present the client as a calculator. Version 2.0 changes only its icon and name, making the limit more obvious. The app will still appear in Android's Apps settings and remain detectable during a forensic inspection. That is a more honest boundary for someone whose phone may be searched, and F-Droid states that boundary directly.
The harder loss is panic-triggered app wiping. F-Droid's existing client can respond to a separate trigger app such as Ripple by removing selected apps. That function has not returned in 2.0 because the project says it needs specialized maintenance and serves a small user base. F-Droid still calls the function important, asks affected users for feedback and explicitly says they may postpone upgrading while a replacement is evaluated.
A modern codebase raises the minimum Android version
F-Droid rewrote the interface in Kotlin and Jetpack Compose, moving the client toward the tools current Android developers already use. The maintainers expect that shift to make the app easier to test and less forbidding for new contributors. One dependency on fixes made in Android 7 also forced the project to drop Android 6 support, although older F-Droid releases remain available for older devices.
A rewrite of an app installer deserves scrutiny beyond screenshots. F-Droid says the Open Technology Fund's Security Lab and Convocation performed an independent security review, and that the project addressed findings relevant to the new client. The full report has not been published yet because it is awaiting clearance, according to the release post. Until readers can inspect that report, the claim remains the project's account of the review rather than a public audit trail.
F-Droid's package record provides a separate check on what people can install today. It says the project built and signed the 2.0.0 APK and guarantees that the binary corresponds to the linked source archive. The same version entry publishes a PGP signature and compressed build log. Those artifacts do not replace the pending security report, but they let others trace this release back to its source and build output.
The rollout itself is another reason to read the small print. F-Droid announced 2.0 on September 24, while its package page says version 2.0.0 was added on September 23 and currently displays a beta badge. Combined with the promised rollout over several weeks, the package record suggests a staged transition rather than an update reaching every device at once.
Watch the published audit report and the project's decision on panic-triggered wiping before treating this transition as finished. Nearby sharing is also being rebuilt and is absent from the initial release, with development tracked publicly. For anyone facing device searches or depending on emergency removal, the sensible next step is to check the installed version and the missing function before accepting the update. Everyone else can judge 2.0 by a plainer test: whether an independent Android store now takes fewer taps without taking away the controls they use.