# Droid-ify: an F-Droid client for Android that puts repositories first

> Droid-ify is a Kotlin Android client for browsing and installing apps from F-Droid repositories, with background updates and three installation backends. It is for people who already run their own repo or want a lighter store front end, not for anyone expecting Play Store coverage.

**Droid-ify/client** — Clutterfree F-Droid client, [mirror] https://codeberg.org/droidify/client

- Repository: https://github.com/Droid-ify/client
- Website: https://droidify.app/
- Stars: 7,525 · Forks: 225
- Language: Kotlin
- License: GPL-3.0
- Published: 2026-09-22 · Updated: 2026-09-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/droid-ify-client

## What Droid-ify replaces, and who it is actually for

F-Droid's own client works, but its repository management is the part people complain about. Adding a third-party index usually means pasting a URL into a settings screen, waiting for a sync, and hoping the index parses. Droid-ify's README lists "Add custom repositories with one tap" as a headline feature, which tells you where the project thinks the friction is.

The audience is narrower than "Android users who want free apps". It is people who already know what an F-Droid repository is: self-hosters running their own index, users of IzzyOnDroid, and anyone who wants a store front end that syncs in the background and then works offline. The README states that offline browsing works after the initial sync. That is a real constraint as much as a feature: the first sync is the expensive part, and everything after it reads from local data.

It is not an app discovery tool for a general audience. If you do not already have repositories you care about, the catalogue you get is the same catalogue F-Droid ships, presented differently.

## How the client is put together: Kotlin, Gradle and a mirror split

The primary language is Kotlin, and the repository topics include kotlin-flow, which points at the reactive layer the UI reads from. The top-level layout is a standard single-module Android Gradle project: app/, gradle/, build.gradle.kts, settings.gradle.kts, gradlew, plus metadata/ for F-Droid's own build metadata and release.sh for cutting releases. Nothing exotic, and that matters for anyone who wants to build it themselves.

The unusual part is not the code, it is the hosting. The README states that source exists on both GitHub and Codeberg, that GitHub is now just a mirror of the Codeberg repo, and that releases will only be created on GitHub until the migration finishes. The same README admits there is "no actual way to say" when that migration is finished. So pull requests go to Codeberg while issues and release artefacts live on GitHub. For a contributor that is two accounts and two mental models; for a user it changes nothing except where the download comes from.

The last push to this repository was on 2026-09-12, and v0.7.8 was tagged the same day. Releases have been landing roughly every one to three weeks through August and September 2026.

## Installing Droid-ify and adding a repository

The README gives four distribution channels: IzzyOnDroid, F-Droid, GitHub releases, and Codeberg releases. For most people the F-Droid listing is the shortest path, since it keeps the client itself updated through the same mechanism it uses for everything else.

If you would rather build it, the README's manual build is three commands. Run them from a shell with a JDK and the Android SDK available:

```sh
git clone https://github.com/Droid-ify/client droidify
cd droidify
./gradlew assembleRelease
```

The output lands under the app module's build directory. The README does not document signing configuration for a self-built release, so expect to handle that yourself before the APK is installable on a device.

Before installing anything, compare the signing certificate against the fingerprint the README publishes:

```
ED:88:59:C5:5A:F3:11:16:26:58:B9:4A:F9:82:B9:F0:91:DC:D2:76:28:D4:DE:34:86:D1:21:7E:BF:3C:99:35
```

The README adds a note that the signature for versions from F-Droid might be different. That is the standard F-Droid signing arrangement, and it means the fingerprint above is not a universal check across all four channels. Verify against the source you actually downloaded from.

Once the app is running, the first sync populates the local catalogue. After that, browsing works offline and updates are handled in the background.

## Installation methods and the root or Shizuku dependency

Droid-ify's README lists three installation methods: Session, Root, and Shizuku. Session is the normal Android package installer flow, which means a confirmation tap per app. Root and Shizuku exist to remove that tap, and to let background updates actually complete without you present.

This is the sharpest limitation in the project, and it is inherited from Android rather than caused by Droid-ify. The README claims "automatic app updates in the background", but on a stock, unrooted device with no Shizuku running, the Session installer still requires user confirmation. Shizuku is a separate app you have to install and start, typically after each reboot unless you have root. If your reason for choosing Droid-ify is unattended updates, budget for that setup, and check that your device and Android version support it. The README does not document per-device compatibility for these backends.

The second limitation is coverage. This is an F-Droid client. Anything not published to an F-Droid-compatible repository is not in it, and proprietary apps are out of scope by construction. If your workflow depends on apps that only exist on the Play Store, Droid-ify is the wrong tool and no amount of repository configuration fixes that.

## How it differs from the official F-Droid client

The official F-Droid client is the obvious alternative and it is the reference implementation for the repository format, so it will always be the first to support format changes. The difference in approach is where each puts its effort. F-Droid's client is conservative about installation and about what it will do without explicit user action; Droid-ify treats installation as a pluggable backend and offers Root and Shizuku paths alongside the Session installer.

Repository handling is the other split. Droid-ify's README presents one-tap custom repository addition as a feature, implying the official client makes you work harder for the same result. That is a UI and workflow difference, not a format difference; both read the same indexes.

Aurora Store is a different comparison and a common source of confusion. Aurora is a front end for Google Play, so it gives you Play catalogue access without Play Services. Droid-ify gives you F-Droid catalogue access. They solve opposite problems and there is no reason to pick between them on features; you pick based on which catalogue you need.

## Licence, upgrade cost and what GPL-3.0 means here

Droid-ify is GPL-3.0. The README carries the full notice, copyright LooKeR, version 3 or later, with the usual warranty disclaimer. For a user this changes nothing about installing or running it. For anyone forking it into their own client and shipping that client, the copyleft terms apply to the distributed work, and the source has to be made available under the same licence. That is a description of the licence text, not legal advice; if you are shipping a derivative, read the licence or talk to someone qualified.

The practical upgrade cost is low. Releases have been frequent, the build is a single Gradle invocation, and there is no server component to migrate. The one thing to watch is the repository split: if you track the project, issues are on GitHub while pull requests are on Codeberg, and the README says releases will keep coming from GitHub until the migration is declared finished. A contributor workflow built around one forge will need the other.

## Conclusion

Adopt Droid-ify if you already use F-Droid repositories and want custom repo handling plus background updates, and if you are willing to check the signing certificate before installing. Do not adopt it if you need Play Store apps, automatic updates on an unrooted device without Shizuku, or a client whose source of truth is a single forge, since the README states that the GitHub repository is now only a mirror of Codeberg while releases are still published on GitHub. Verify first: the APK signature fingerprint, and whether your device has root or Shizuku available for unattended updates.

## FAQ

### How do I install Droid-ify on Android?

The README lists four channels: IzzyOnDroid, F-Droid, GitHub releases and Codeberg releases. Installing from F-Droid is the simplest because the client then updates through the same repository mechanism it uses for other apps.

### Does Droid-ify update apps automatically in the background?

The README lists automatic background updates as a feature, and separately lists three installation methods: Session, Root and Shizuku. On a device without root or Shizuku, the Session installer still requires confirmation, so unattended updates depend on which backend you can use.

### Can I add my own F-Droid repository to Droid-ify?

Yes. The README lists adding custom repositories with one tap as a feature, and states that browsing works offline after the initial sync.

### Where do I report a bug or open a pull request for Droid-ify?

The README states that the issue tracker is on GitHub and pull requests go to Codeberg, because GitHub is now only a mirror of the Codeberg repository. Releases are still created on GitHub until the migration finishes.

### How do I build Droid-ify from source?

The README gives a three-command manual build: clone the repository, change into it, and run ./gradlew assembleRelease. The README does not document how to sign the resulting release build.

## Sources

- [Droid-ify/client on GitHub](https://github.com/Droid-ify/client)
- [License: GPL-3.0](https://github.com/Droid-ify/client/blob/main/LICENSE)
- [Project website](https://droidify.app/)
- [README](https://github.com/Droid-ify/client/blob/main/README.md)
- [Releases](https://github.com/Droid-ify/client/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/droid-ify-client