F-Droid is a free, open-source app store for Android that compiles apps from their published source code. Ars Technica reports the client app has now been rebuilt from scratch, with a new interface and a less awkward install process.
What is F-Droid, and what does it actually do?
F-Droid is a catalogue of Android applications that are distributed under free and open-source licences. Rather than accepting finished packages from developers, the project takes the published source code, builds the app on its own infrastructure, and signs the resulting package with its own key. That build is then offered through a client app you install on your phone.
The practical effect is that every listing in the main catalogue corresponds to source code someone can inspect. It also means F-Droid is a curator as well as a shop: apps have to meet its licensing rules to be included, and packages that rely on proprietary components are either excluded or flagged. The catalogue is smaller than a mainstream store, and skews towards utilities, privacy tools and enthusiast software.
How is it different from the Google Play Store?
The clearest difference is where the binary comes from. On Google Play, developers upload the package they built themselves. On F-Droid, the project builds it, so the version you receive is tied to a specific public commit rather than to whatever a developer chose to submit.
The second difference is distribution. Google Play is pre-installed on most Android phones sold with Google services, and its install machinery is privileged at the system level. F-Droid is an ordinary app that you install yourself, which means it operates under the same restrictions as any other third-party installer.
Third, the commercial model differs: F-Droid has no paid apps, no in-app purchase plumbing and no advertising network attached to the catalogue.
What has changed in the rebuilt client?
According to Ars Technica, the F-Droid client has been rewritten from the ground up, giving it a new interface and a smoother experience when installing apps. The publication frames this as the most substantial change to the app in roughly ten years, which matches the long-standing complaint that the old client’s design and browsing experience had aged badly.
Beyond that, the detail is thin, and it is worth being honest about the gap. Exactly which screens were redesigned, what the install flow now looks like step by step, which Android versions the rebuilt client supports, and whether older devices are affected are not things that can be confirmed from the material available here. If you rely on F-Droid daily, check the project’s own release notes before updating.
How do I install F-Droid on an Android phone?
The client is not distributed through Google Play. You download an APK file from the project’s own website using your phone’s browser, then open it to begin installation. Android will ask whether that browser is permitted to install applications; you grant the permission, complete the install, and can then revoke it again if you prefer.
Once the client is open, it downloads an index of the catalogue, which can take a moment on a first run. After that you can search, browse by category, and install individual apps from within the client.
On devices from manufacturers that add their own security layers, there may be an additional prompt or a toggle buried in the settings app. The wording varies by brand and Android version.
Why does Android warn me during installation?
Because installing software from outside a pre-approved store is exactly the path that malicious APKs also use, and Android cannot tell the difference between a carefully curated open-source store and a dubious download. The warning is generic.
Modern Android grants the install permission per application rather than as a single global switch, so the browser you used to fetch the APK is the thing being trusted, not the phone as a whole. Once F-Droid is installed, it becomes the app requesting that permission for subsequent installs.
The sensible precaution is to make sure you obtained the APK from the project’s official domain over HTTPS, and to be wary of mirrors, file-sharing sites or messaging apps forwarding you an APK.
Why does each app install need its own confirmation?
Historically, an unprivileged installer on Android cannot push a package silently. Every install and every update produces a system dialogue that you have to approve, which makes updating a dozen apps a tedious sequence of taps. This is a platform restriction, not a design choice by the project.
The long-standing workaround is the F-Droid Privileged Extension, a component installed at system level that lets the client install and update apps without prompting. It generally requires either a custom Android distribution that ships it, or a device where you can write to the system partition, so it is not an option for most stock phones.
Ars Technica reports that installing apps is smoother in the rebuilt client. The precise mechanism behind that is not something confirmed in the available material.
Can I move an app I already have from Google Play?
Not by updating in place. Android refuses to replace an installed app with a package signed by a different key, and an F-Droid build is normally signed by F-Droid rather than by the developer. The two copies are, as far as the system is concerned, different software with the same name.
To switch, you uninstall the existing copy and install the F-Droid version, which means losing local data unless the app offers its own export or backup function. Check for one before you uninstall.
A partial exception exists: some developers publish builds that F-Droid verifies reproducibly and then distributes with the developer’s original signature. Where that applies, the signatures match and the switch is less disruptive. It is not the norm across the catalogue.
What do the “anti-feature” labels mean?
F-Droid attaches warning labels, called anti-features, to listings that contain things some users would rather avoid even though the app itself is open source. Typical categories cover advertising, tracking or analytics, dependencies on non-free services, promotion of non-free software, and known security or privacy concerns.
These labels are informational rather than prohibitive. Apps carrying them remain installable, and the client has settings controlling whether flagged apps appear in browsing and search results by default.
Treat them as a prompt to look closer rather than a verdict. A label indicating reliance on a proprietary network service, for example, may be entirely expected for a client app that talks to a commercial platform, and tells you little you did not already know.
Should I add third-party repositories?
The client supports additional repositories beyond the default catalogue, added by URL or QR code. Some are run by organisations that publish their own software; others aggregate open-source apps that are not in the main repository, often with faster updates because the packages are not rebuilt from source.
The trade-off is that each repository you add is a party you trust to sign packages installed on your phone. The main F-Droid catalogue’s inclusion policies and build process do not apply to them, and neither do its anti-feature labels unless that repository maintains its own.
For most people the default repository is enough. If you add others, add specific ones you have a reason to trust rather than collecting them.
What are the trade-offs before relying on it?
The catalogue will not contain most mainstream commercial apps, because those are not open source. F-Droid is a supplement to, not a replacement for, whatever store your phone shipped with, unless you have deliberately chosen a device and software set built around it.
Updates can lag behind a developer’s own releases, because packages have to be rebuilt and signed after upstream publishes. Some apps are also available in the client in variants that differ slightly from the versions distributed elsewhere.
Against that, you get software with published source, explicit warnings about undesirable behaviour, no account requirement, and a store that does not itself need a commercial relationship with the developer to list an app.
Sources and further reading
- Ars Technica — technology news report describing the rebuilt F-Droid client, its new interface and improved install experience.
- The F-Droid project’s own documentation and user manual — the authoritative reference for repositories, anti-features and the Privileged Extension.
- Android developer documentation on application signing and package installation permissions — explains why signatures must match and why installers prompt.
- Release notes published by the F-Droid project — the place to check version-specific changes and device compatibility before updating.
Surfaced from the rss:arstechnica signal “open-source app store redesign”. AI-assisted draft, editorially reviewed.
