F-Droid's catalog lags weeks behind developers. Obtainium closes the gap — it watches GitHub releases and installs APKs directly, turning sideloading from a chore into a pipeline.

F-Droid's catalog lags weeks behind developers. Obtainium closes the gap — it watches GitHub releases and installs APKs directly, turning sideloading from a chore into a pipeline.

Here's the open-source Android dilemma: F-Droid is trustworthy but slow (its build queue delays releases by days or weeks), while sideloading APKs from GitHub is fast but manual — you become the update mechanism, checking repos like it's 2009. Obtainium is the missing piece: an updater that tracks app releases at their source and installs them directly, no store involved.

What Obtainium actually does

You give it a source — a GitHub releases page, a GitLab project, F-Droid repo, or even a direct APK URL — and it monitors for new versions. When one appears, it downloads and installs the APK, using Android's standard install flow. It's essentially a package manager where every "repository" is the developer's own release channel.

This matters because the freshest, most trustworthy build of an open-source app is usually the one the developer publishes themselves. F-Droid rebuilds from source (great for verification, slow for delivery). Obtainium skips the middleman: same APK the developer signed, installed minutes after release.

Setting it up (ten minutes)

  1. Install Obtainium from its GitHub releases or F-Droid.
  2. Tap Add App, paste a releases URL — e.g. https://github.com/TeamNewPipe/NewPipe/releases. Obtainium auto-detects the source type.
  3. For GitHub sources, add a personal access token (Settings → Apps) if you track many apps — GitHub rate-limits anonymous API calls and you'll hit the ceiling fast with a dozen apps.
  4. Configure the APK filter with a regex matching your architecture (arm64) so it doesn't offer you x86 builds. The default filters are sane; tighten them per app if needed.
  5. Enable background updates and decide per app: silent auto-install (convenient, slightly less eyes-on) or notify-then-install (my preference for anything with network permissions).

The workflow that actually works

Run F-Droid for discovery and Obtainium for delivery. Browse F-Droid to find apps, then add the fast-moving ones to Obtainium pointed at their GitHub releases. You get F-Droid's curation with day-one updates — the best of both.

A practical starter set: NewPipe, AntennaPod, Aegis, KeePassDX, and Syncthing all publish GitHub releases that Obtainium tracks flawlessly. That's five apps updated within hours of release, zero Play Store involvement.

Know the tradeoffs

Obtainium installs developer-signed APKs, not F-Droid's reproducible builds — you're trusting the developer's release process instead of F-Droid's verification. For well-known projects with signed releases and a track record, that's a fine trade. For obscure apps, stick to F-Droid.

It also can't update apps that only distribute through Play, and apps with split APKs (app bundles) need extra configuration. Check each app's release page for a universal APK before adding it.

The bottom line

Sideloading's bad reputation comes from it being manual. Obtainium automates the tedious part — watching, downloading, installing — while keeping the good part: software straight from the people who wrote it. Pair it with F-Droid and you've got a complete open-source app pipeline that answers to nobody.

Sources: Obtainium GitHub · F-Droid · NewPipe releases