MultiStore

A native Android app that aggregates third-party app stores into one catalogue. Search across all of them at once, compare what each publishes for the same app, download and install APKs from the store you pick, and keep what you installed up to date.

One search across many Android app stores.

Search them all at once, compare what each one publishes for the same app, and install from the source you choose, through the same verification pipeline every time.

What it does One search, many sources. A query fans out to every enabled store in parallel; results stream in as each answers and are grouped into one row per app, with every store that has it listed underneath. Nothing waits for the slowest source, and a store that fails or gets rate-limited is named next to the results instead of silently vanishing.

It says which one to trust. Not every store is the same. Some publish a SHA-256 for each file, some publish the package name, some redistribute modified builds. The app page reports what verification was actually able to prove, and "verified" and "not contradicted" are different sentences. Settings says what to expect from each source.

It admits when it cannot be sure. Stores disagree about package names, and some publish none at all, so "the same app on two stores" often has to be inferred. Below a confidence threshold nothing is merged silently: the second listing shows up as a possible match with the reason, and the choice is yours.

Seven checks before anything is installed. Size, streamed SHA-256, archive read with apksig, package-name match against the listing (a hard, non-bypassable block), signer comparison against the already-installed certificate including v3 key rotation, anti-downgrade, and a record of what was installed from where. The file that is verified and the file that is installed are the same bytes: the hash is computed while writing into the install session, not before it.

Split containers install properly. XAPK, APKM and APKS bundles are opened, the right ABI and density splits are chosen for the device, every language split is kept, and base plus splits go into a single PackageInstaller session.

Updates come from the store the app came from. Changing publisher mid-life breaks the update at the OS level, so each installed app remembers its own update channel. You can change it deliberately and get warned about the signature conflict.

Three ways to install. The standard system confirmation always works; Shizuku and root, where available, install silently. No feature requires a privileged channel. Where one is only available with it, the interface says so.

Everything stays on the device. No telemetry, no accounts, no analytics. The diagnostics log is off by default, lives locally, and is exported by you as a plain-text file you can read before sending it anywhere.

Five languages, light and dark. English, Italian, French, Spanish and German, all complete or the build fails. Every screen has a screenshot baseline in both themes, and each one is run through the Accessibility Test Framework.

What it is not MultiStore does not host, mirror or rehost anything. It reads publicly reachable pages the way a browser does, on requests a person has just made. It does not solve captchas, forge TLS fingerprints or rotate addresses to get around a block. Where a download genuinely needs a human tap, you make it.

Stores The sources MultiStore reads today:

AN1 APKCombo APKMirror APKMODY F-Droid LiteAPKs MODYOLO PDALIFE Uptodown