What Conversations’ Move to F-Droid Really Changes

On a phone, an app store looks like a shelf. For the person maintaining a small open-source Android app, it is also a checkout, an update gate, a review desk, and an identity provider. That is why Conversations’ move toward free, F-Droid-first distribution matters beyond its price tag. It changes who delivers the app, who controls the release clock, and how the project stays alive.

Conversations is an XMPP messenger. XMPP, short for Extensible Messaging and Presence Protocol, is an open standard for chat; “federated” means people on different servers can communicate, much like email. The network avoids putting every conversation under one company. Now the distribution model is following that same instinct.

As of September 2026, Google Play presents Conversations as a free open-source Android client, while F-Droid lists version 2.20.3+free for Android 6.0 and newer. The deeper change is that F-Droid has become the primary route, with a reproducibly built release signed by the developer’s own key.

Free is not the same as effortless

Conversations has been open source from the start. Open source means the source code—the human-readable instructions that make up the program—is available for others to inspect, modify, and share. The project uses the GPLv3, a license that preserves those freedoms under specific sharing conditions.

That did not prevent the maintainer from selling a convenient release. For years, the code could be studied and the app could be obtained through F-Droid, while the polished, signed Google Play version charged for the convenience of installation and automatic updates. It is a coherent model: the recipe is public, while someone pays for a tested meal delivered to the table.

The money mattered. The maintainer describes Play revenue as a dependable part of his income and says Google’s cut alone amounted to more than €1,000 per year at his sales volume. Over time, grants, paid development, consulting, and related work became more important. The free F-Droid release became possible because the funding model changed—not because maintaining a secure messenger stopped costing time.

The file on your phone has an identity

An Android app is delivered as an APK, short for Android Package. It is the installable file containing the program and its resources. Android does not trust an APK because its filename looks familiar. It checks a digital signature: a mathematical proof made with a secret signing key.

That key matters whenever an app is updated. Android expects the new release to carry the same signing identity as the installed release. If the certificate changes, the system may treat the file as a different app or refuse an in-place update. This is why changing distribution channels can be more complicated than downloading a second copy.

Google Play App Signing adds another layer. Google can manage the key that signs APKs delivered through Play, while the developer keeps a separate upload key. A developer who wants the same app to update across several stores has to plan that key ownership carefully.

You can inspect the certificate on an APK with the Android Software Development Kit (SDK), a collection of tools for building and checking Android apps:

apksigner verify --print-certs Conversations.apk

The command reports certificate details and a fingerprint. That tells you who signed the file. It does not, by itself, prove that the file was built from the published source code. For that, we need another idea.

Reproducible builds turn trust into a check

A reproducible build is a build process that produces the same result when people repeat it with the same source and controlled tools. Think of it as a baking recipe that specifies not only the ingredients, but also the oven temperature, timing, and measuring method closely enough that another kitchen can produce the same loaf.

F-Droid’s build system can compile an app from source, compare the result with the developer’s release, and publish the developer-signed APK when the two match. That is the important detail in Conversations’ new arrangement. F-Droid is not merely acting as a download mirror; it can check that the binary corresponds to the source archive before distributing it.

This is not magic. Build tools, timestamps, native libraries, and third-party dependency versions can introduce tiny differences. Reproducibility takes deliberate work. But it removes one large “trust this server” step and replaces it with an auditable comparison.

Why XMPP makes the move feel natural

XMPP is federated in the same way email is federated. You can choose an account provider, run a server yourself, or move between providers without changing the basic messaging protocol. Conversations is the phone client, not the entire network.

The app supports end-to-end encryption through OMEMO, an XMPP extension that protects message contents from servers and other intermediaries, along with file sharing, group chats, and encrypted calls when the necessary server features are available. The protocol, server, Android client, and app store are distinct layers.

That separation is useful here. A federated messenger distributed through one dominant storefront was always a compromise of convenience. Conversations’ F-Droid-first approach brings the packaging layer closer to the project’s existing design philosophy.

Independence has a user cost

F-Droid is an app repository: a catalog and delivery service for free and open-source Android software. Installing the F-Droid client adds a step compared with tapping an install button in Google Play, and users must learn a different update path. Direct APK downloads are even less convenient; F-Droid warns that they do not provide update notifications and are a less secure way to install.

So how do you install an Android app without Google Play? You install a trusted alternative repository, use it to install the app, and keep receiving updates through that same channel. The update path matters because security depends on receiving patched releases, not merely installing the first version.

Moving from an existing Play installation can also involve signing keys. If the installed copy and the F-Droid copy are signed by different keys, Android may require an uninstall and reinstall. That can remove private app data, so exporting account details or backups before switching is sensible. A free download can still carry a migration cost.

The maintainer’s announcement described waiting 14 days for an app update review. A feature can wait in a queue. A security fix should not. No store can eliminate every bug or malicious release, but a project that controls its build and distribution path has fewer external gates between “patch ready” and “patch available.”

The bigger lesson is about dependency

This story is not really about refusing to charge for an app. It is about separating four things that app stores tend to bundle together: payment, discovery, delivery, and trust.

Conversations now has a funding mix that includes grants and professional work. F-Droid handles a primary distribution path. Reproducible builds make the relationship between source and release easier to inspect. A developer-controlled signing key preserves the app’s identity. XMPP keeps the messaging network independent from the client.

That arrangement will not fit every project. App stores still offer reach, familiar installation, automatic updates, and payment infrastructure. But Conversations shows that “free” can be the visible result of a deeper technical decision: move the gate, keep control of the keys, and make the build process part of the trust story.

The most interesting part is not that the app costs nothing. It is that the route from source code to a message on your phone is becoming more visible—and less dependent on a single storefront.