F-Droid
Catalog and installer for free and open-source Android apps, no Google account required.
Private alternatives to Google Play Store, Samsung Galaxy Store, vetted against our public criteria.
Catalog and installer for free and open-source Android apps, no Google account required.
Installs and auto-updates Android apps directly from their upstream release sources.
Open-source Google Play client that lets you download apps anonymously without a Google account.
Security-focused Android app store with signing key pinning and signed repository metadata.
No matches for those filters.
| Tool | Source | Cost |
|---|---|---|
| FOSS repo | Free |
| Upstream | Free |
| Play proxy | Free |
| | Own repo | Free |
Installing Android apps the normal way means a Google account and the Play Store’s tracking, even for free and open-source software that asks nothing of you in return. These app stores let you install and update apps without signing into Google, pulling from open-source repositories or straight from a developer’s own releases. They run alongside the Play Store rather than replacing it outright, so you can move most of your installs off your Google account while keeping the one app that still demands it.
The Play Store is the app-delivery arm of the same Google account that already follows you across search and maps, and that link is the design rather than a bug. Every install and update is logged against your identity, even side-loading is nudged back toward the official channel, and there is no setting that turns the store into an anonymous catalogue, because the account is the point of it. Breaking the connection means going around the store: a separate repository that builds open-source apps itself, an anonymous client that fetches Play apps without your account attached, or an installer that pulls a developer’s signed releases directly. That is the gap each tool here fills.
Every store here is measured against our public listing criteria. We require that a store verify app signatures, so you can trust an app really came from its developer, and that it deliver updates promptly, since an app that goes stale is a security risk of its own. We favour open source and a transparent supply chain, because a store is only as trustworthy as where it gets its apps. We are explicit about which gap each one covers, and we only list a store we would install on our own phone.
The first question is always where the apps come from and who vouches for them, and the answer differs by store. An open-source repository like F-Droid builds apps from public source and is ideal for FOSS, an anonymous Play client like Aurora Store reaches Google’s catalogue without tying installs to your account, and a release-tracker like Obtainium pulls a developer’s signed files straight from the source. Beyond the source, check that updates arrive promptly and that signatures are verified, since that supply chain is what keeps you safe.
Because no single store covers every app, and each design solves a different problem. Open-source apps live in open-source repositories, mainstream and proprietary apps usually exist only in Google’s catalogue, and a few apps a developer ships only from their own site. Trying to force all three through one store leaves gaps. The common setup is a FOSS repository for the open apps, an anonymous Play client for the ones only Google has, and a release-tracker for the independents, with the Play Store itself kept on standby for the rare app that refuses anything else. Running a few stores is the norm here, not a sign you did something wrong.
You do not have to replace the Play Store all at once, and trying to is the mistake that makes people give up. Add an open-source store for the FOSS apps it carries, an anonymous Play client for the apps only Google offers, and a release-tracker for apps that ship on their own, then move your installs across as you reinstall or update them. Keep the Play Store installed if one stubborn app insists on it. If the goal is cutting Google out of the phone more broadly, the Google Play alternatives page covers the store specifically, a hardened mobile OS reduces what Google sees underneath, and the de-Google playbook handles the rest of the ecosystem.