Latest Releases
17 apps · 17 with a recorded certificate
The newest build of every app we list, ordered by release date. This is the page to check when you want the current version of something rather than whatever a mirror happened to cache eighteen months ago — stale APKs are how known-fixed vulnerabilities stay in circulation long after the developer has patched them.
New is not automatically better. A fresh release is also a fresh opportunity for someone to slip a repackaged build into circulation while nobody has looked closely yet, and it is the moment when an app is most likely to quietly acquire permissions it did not ask for before. Check what the update changed and compare the signing certificate fingerprint against the version you already have — Android will reject a mismatched key on update, and so should you.
Everything below has been traced to a publisher we can name. Where the app is on an official storefront, that link sits at the top of the listing and we do not try to outrank it — the store copy has the shortest chain of custody available. Where we host or mirror a build instead, the listing carries its SHA-256 hash, the signing certificate fingerprint, the version code, and the full permission list, so the file can be checked before it is installed rather than trusted after.
Before you install anything from this page
How is this list ordered?
By the release date of each app's newest build, most recent first. It is the date attached to the build itself, not the date we added the app or last touched the page, so an app that has not shipped in a year will sit near the bottom where it belongs.
Should I always install the newest version?
Usually yes — updates are how fixed vulnerabilities actually reach your device, and an old APK from a mirror can leave a known hole open indefinitely. But read what changed first. Updates are also where new permissions arrive, and a build that suddenly wants contacts or accessibility services for features you cannot identify deserves a pause. The changelog and permission list on each listing are there for exactly that.
How do I check an APK is genuine before I install it?
Two checks, both on the listing page. Hash the file you downloaded with SHA-256 and compare it to the hash we published — if one byte differs, the whole hash differs. Then compare the signing certificate fingerprint to the publisher's earlier releases. Android enforces that match itself: it will refuse an update signed with a different key than the version already installed, which is why a matching fingerprint is meaningful evidence and a matching version number is not.