Blunt Stream
Blunt Audio
Your music, in one place. An Android music player from Blunt Audio.
- Latest version
- 0.3.9-pilot
- Released
- 8 October 2026
- Size
- 20.4 MB
- Requires
- Android 8.0 or later (API 26)
Android apps, direct from their makers.
Blunt Audio
Your music, in one place. An Android music player from Blunt Audio.
App King distributes Android applications outside a conventional app store. That makes traceability more important, not less.
Each release is treated as a specific binary, from a specific developer, signed by a specific certificate. Evidence stays attached to that exact file. If the file or its declared identity changes, the checks do not carry over.
The process is designed to make substitution, stale evidence and identity drift visible before a file can become the public release.
The APK is held outside the public catalogue. Its SHA-256 fingerprint and byte size are calculated from the stored file — never supplied by the uploader.
Android package metadata, version, minimum SDK and signing certificate are read from the APK and compared with the release record and the app’s pinned identity.
Signature verification, functional testing and any malware scan are recorded against those exact bytes. Anything not performed remains explicitly not run or not scanned.
Automation cannot approve a release. A person reviews the evidence, and any replacement APK invalidates the previous result before publication can continue.
Publication is a controlled pointer to one approved release, not the end of the process.
The public download resolves only to the current approved file. Storage remains private and the delivery link is short-lived.
Package name and signing certificate identify the app across versions. A mismatched update is blocked rather than treated as the same product.
Every new APK starts again with its own fingerprint and evidence. Results from an older version cannot authorise a newer one.
A release can be removed from the public download and update feed. That does not uninstall or remotely disable copies already on a device.
A valid signature proves who signed a file. A matching hash proves which file was checked. A scanner reports what it detected at that time. None of those facts can promise how software will behave in every circumstance.
We publish the distinction instead of flattening it into a reassuring badge.
An app enters the catalogue through an attributable developer, a signed Android package and a reviewable release record. Catalogue access is separate from publication authority: uploads, checks, approval and publication are distinct steps.
01
Establish who supplies the app and whether they are the maker or an authorised distributor.
02
Bind observed package metadata, signer identity and check results to the exact uploaded APK.
03
Review the evidence and limitations before choosing whether the release belongs in the public catalogue.