Obtainium Updates Apps Straight From Release Pages
Obtainium review: why it says no update when GitHub has a newer release, signature-mismatch and split-APK limits, and its upstream-trust model.
App summary
- App
- Obtainium
- Developer
- ImranR98
- License
- GPL-3.0-only
- Version
- unknown
- Size
- unknown
- Price
- Free
Most Android app installers want to become a store. Obtainium takes the opposite position. It assumes you already know which app you want, that you found its release page yourself, and that you would rather have a small local tool watch that page than trust a catalog to do it for you. That is a narrow job, and the app is honest about it.
Obtainium is an open-source Android app developed by ImranR98 and hosted on GitHub. It is licensed GPL-3.0-only, distributed free of charge, and requires Android 8.0 or later. Its stated purpose is to install and update Android apps directly from upstream release pages, and to track multiple apps so you get notified when new versions are published. No account is involved. The list of apps you track lives on your device.
That design is the whole story, and it is also where the arguments start. Obtainium is best understood as a local, power-user release tracker for Android sideloading rather than a curated store. Its real quality hinges on three things: how cleanly your chosen upstream projects publish releases, how much permission friction you are willing to accept, and whether you are comfortable installing APKs that no store has vetted. Several details about the app itself are not publicly documented — the exact latest version number and release date, the APK download size, and any download or active-user counts are all unknown — so this review sticks to what the project actually claims and flags the rest.
Why Obtainium Says ‘No Update’ When GitHub Has a Newer Release
This is the complaint that shows up most often, and the explanation is structural rather than a bug report. Obtainium’s periodic update checks and notifications depend on each source’s release format and API/rate limits. A project that publishes a proper release with attached assets looks different to a checker than a project that only pushes a tag, and a source that throttles requests can leave a check with nothing to report. When GitHub shows a newer release and Obtainium does not, the most likely reading is that the check did not resolve the new version cleanly, not that the release does not exist.
The mechanics behind that are worth understanding. Obtainium adds apps by URL from supported sources and tracks multiple apps at once. The verified examples in the project’s own description are GitHub, GitLab, and F-Droid; the fact data does not enumerate every integration, so treat any longer list you see elsewhere as unconfirmed. Each of those sources has its own conventions for what a release looks like, and Obtainium has to interpret those conventions rather than read a single standardized feed.
Rate limits are the part people ask about most, and this is where honesty matters. The fact data confirms that API/rate limits affect update reliability, but it does not contain specifics on workarounds, retry behavior, or timing adjustments. Any recipe you find for “fixing” GitHub rate limiting in Obtainium should be treated as unverified unless it comes from the project itself. The same caution applies to version-specific behavior: because the exact latest Obtainium version is unknown, no claim in this article should be pinned to a particular build.
A practical habit follows from all of this. Treat “no update” as a prompt to open the release page yourself, not as proof that nothing shipped. For apps you care about, that manual double-check costs a few seconds and removes the ambiguity entirely. And if an app has no release page at all — no tagged releases, no published artifacts — Obtainium has nothing to watch, which is a different problem than a missed check.
Obtainium Signature Mismatch and Split-APK Installs: Known Limits, Unknown Recovery Steps
Direct APK install and update is a core feature, and it comes with the friction you would expect. Obtainium requires sideloading and granting the install/unknown-source permission on your device. That is not a bug or an oversight; it is the unavoidable cost of installing software outside a store, and it is the first place where non-technical users bounce off.
Split APKs and app bundles are the murkier territory. The fact data describes direct APK install and update but says nothing about how split-APK or app-bundle packages are handled. That means the honest answer to “how do I add an app that publishes split APKs or bundles” is that the documented behavior is unknown. Do not assume support, and do not assume failure either. If a project ships only bundles, that is a question to resolve against the project’s own release artifacts before you add it.
Signature mismatches are the other scenario readers ask about, usually after an app changes its signing key. The fact data does not specify how Obtainium verifies signatures or what it does when a key changes, so any recovery procedure you read elsewhere — uninstall first, clear data, re-add the app — is not something this review can confirm. What can be said plainly is that sideloading and the unknown-source permission already put install mechanics in the user’s hands, so a mismatch becomes a manual problem to solve rather than something the app can quietly paper over.
There is a second layer of risk that has nothing to do with signatures. Update reliability depends on each source’s release format, and Obtainium has no centralized app review or malware scanning comparable to a major app store. So the install path carries user-facing friction and the payload carries unvetted trust at the same time. Neither of those is a reason to avoid the app, but both belong in the decision.
Obtainium’s Upstream-Trust Model: Open Source Does Not Mean Every APK Is Vetted
The most common misconception about Obtainium is that its open-source status makes the apps it installs safe. It does not, and the distinction is important. Obtainium is open-source and publicly auditable on GitHub, which supports transparency about the tool itself — what it does with your list, how it checks sources, what it sends over the network. That auditability says nothing about the APK a third-party project attached to its latest release.
The fact data is explicit here: Obtainium has no centralized app review or malware scanning comparable to a major app store. It installs and updates directly from upstream release pages, which means trust shifts to the sources you configure. If you add a project whose releases are well maintained, signed consistently, and published by people you have reason to trust, you get a clean result. If you add a project that is sloppy or compromised, Obtainium will faithfully install that too.
It is also worth correcting what Obtainium is not. It does not host or mirror APK files itself; it points at release pages and works from what those pages expose. It is not a drop-in Play Store replacement, and pasting a Play Store link will not make it update a Play app — it needs a supported source with a release page it can read. And it is not a substitute for F-Droid’s curated repository, which is a different model with different guarantees.
On privacy, the picture is modest and mostly good. No account is required, the tracked app list is stored locally, and network requests are made to the sources you configured. That is a sensible design for a tool like this. The caveat is that no independent privacy audit or detailed formal privacy policy is known from public sources, so the privacy story rests on the code being open and the architecture being local rather than on any third-party certification.
Obtainium Background Update Checks and Local Backup: Battery, Network, and Migration Realities
Periodic update checks and notifications are core features, and direct APK install and update are available when you act on them. That phrasing matters, because it corrects the idea that Obtainium silently auto-updates everything in the background. The app’s job is to notice and tell you. Installing is a step with a permission prompt attached, and on most setups that step involves you.
Migration is handled the way you would hope for a local-first tool. Export and import of the tracked app list is the documented path for backing up or moving your setup to another device. Since no account is required and the list is stored locally, there is no server-side copy to fall back on — if you do not export, you do not have a backup. Anyone who has rebuilt a tracking list by hand will appreciate how much this matters.
The unknowns here are real and should be stated rather than glossed. The battery and network impact of frequent checks is not documented in the fact data, and the precise background auto-update behavior is not documented either. If you plan to track a large number of apps on a metered connection or an older phone, that is a configuration question you will have to answer empirically rather than from a spec sheet.
One more misconception to clear up: Obtainium does not require root to install or update apps. Nothing in the fact data supports root or privileged-helper requirements. What it does require is the ability to sideload and the install/unknown-source permission, which is a normal user-level setting on most Android devices — though some locked-down devices do not allow it at all, and on those Obtainium simply cannot do its job.
Obtainium vs F-Droid
These two tools get compared constantly, and the comparison usually goes wrong in the same way. F-Droid is a curated open-source Android app repository with its own client and update mechanism. Obtainium is a tracker that watches release pages you point it at. One is a catalog with a review process; the other is a pair of eyes on an upstream project’s publishing habits. If you want the broader picture of how a curated open-source catalog actually works, the article on F-Droid: An Open Source App Catalog for Android explains the repository model that Obtainium deliberately does not replicate.
The practical split follows from that. Use F-Droid when you want a maintained catalog, a single update mechanism, and the modest assurance that comes from a repository’s inclusion process. Use Obtainium when the app you want is not in F-Droid, when F-Droid’s build lags behind upstream, or when the project publishes only on GitHub or GitLab and has no repository presence at all. The two coexist fine, and in fact F-Droid is one of the verified sources Obtainium can read from.
What Obtainium is not is a replacement for F-Droid’s curated repository. It has no review step, no inclusion criteria, and no catalog. It will track whatever URL you give it and report what it finds. That is a feature for power users and a hazard for anyone who reads “open source” as a safety label. If your reason for using F-Droid was curation, Obtainium does not give you that.
Obtainium vs Aurora Store
Aurora Store provides another way to install apps outside Google Play, which makes it a natural point of comparison for Obtainium’s direct-from-release updating model. The overview of Aurora Store on Android: What It Does and Who It Suits covers that app’s approach in detail, and the contrast is instructive: Aurora is built around reaching a store catalog without the store client, while Obtainium is built around the release pages of individual projects.
The difference in trust is the interesting part. Aurora’s model still routes through a store-style catalog, with whatever review that catalog implies. Obtainium’s model routes through upstream release pages, which means the only review is whatever the upstream project does and whatever you do before adding it. Neither app performs its own malware vetting in the way a major store does, but the failure modes are not the same.
There is also a licensing gap worth naming. Obtainium does not provide Play Store paid app licensing or in-app purchases. If your library depends on either, this is not the tool for that part of it. It is a release tracker for freely distributed APKs, and it should be judged on that scope rather than stretched to cover store functionality it does not claim.
Obtainium suits sideloaders who track release pages themselves, not store-only users
Obtainium suits a specific kind of Android user: someone who already sideloads, who knows which projects they trust, who is comfortable granting the install/unknown-source permission, and who would rather have one local list of release pages than check a dozen GitHub tabs by hand. That user gets real value from periodic checks and notifications, and from export/import when they change phones.
NewPipe is a good illustration of the category. It is a well-known open-source Android app that sits outside the usual store path, which makes it a concrete example of the kind of app Obtainium is designed to manage; the overview of NewPipe on Android: What It Does and Who It Suits covers that app on its own terms. The pattern generalizes to any project that publishes releases on a supported source and expects users to fetch updates themselves.
The list of people who should skip it is longer, and worth being blunt about. Non-technical users who want a one-tap Play Store experience will find the URL-adding and permission prompts tedious. Anyone who needs a curated, malware-vetted catalog should stay with a repository. People who expect automatic updates for apps with no release page are asking for something the app cannot do. Users who cannot sideload or grant the unknown-source permission are blocked at step one. Anyone needing paid app licensing or in-app purchases is in the wrong tool. And anyone on a locked-down device without sideloading enabled should not bother installing it.
Verdict
Obtainium is a good tool with a narrow scope, and it is best judged on whether that scope matches you. As a local release tracker for sideloaded Android apps, it does the job its description claims: add apps by URL from supported sources, check periodically, notify, install directly, and let you export the list. It is free, open-source under GPL-3.0-only, requires no account, and keeps your tracked list on your device.
It is not a store, and the moment you expect store behavior it disappoints. There is no curation, no malware scanning comparable to a major app store, no paid licensing, and no magic for apps that never publish a release page. Update detection is only as reliable as each source’s release format and rate limits allow, and the documented behavior around split APKs and signature changes is thin enough that you should verify it yourself before relying on it. The exact latest version, download size, and user numbers are not publicly documented, which makes it harder to assess maturity from the outside.
Use it if you are the power user described above and you accept that trust moves upstream to the projects you choose. Skip it if you want a curated catalog, a one-tap experience, or a Play Store substitute. F-Droid and Droid-ify cover the curated end, and downloading releases manually from GitHub covers the same ground as Obtainium with more clicks and no list to maintain. Obtainium’s contribution is convenience and organization for people who were already doing this by hand — no more, and no less.
Pros
- Open-source and publicly auditable on GitHub
- Can track apps from multiple upstream sources instead of relying on one store
- No account is required; the tracked app list is managed locally
Cons
- Requires sideloading and granting install/unknown-source permission
- Update reliability depends on each source's release format and API/rate limits
- No centralized app review or malware scanning comparable to a major app store
The link goes straight to ImranR98. We do not host app files.
Frequently asked questions
Is Obtainium free?
The recorded pricing model is Free.
What license does it use?
It is listed under GPL-3.0-only.
Where can I download the official version?
The official link points to https://github.com/ImranR98/Obtainium.