
Independent BitChat guide
BitChat iOS vs Android: Downloads and Version Checks
Published · Last verified · By BitChat Guide editorial team
BitChat has separate iOS and Android codebases and release channels. Their version numbers and release dates do not need to match, so verify each platform independently.
Distribution at a glance
| Check | iOS | Android |
|---|---|---|
| Normal install path | Apple App Store | Google Play |
| Official source | permissionlesstech/bitchat | permissionlesstech/bitchat-android |
| Store identifier | App ID 6748219622 | Package com.bitchat.droid |
| Alternative build path | Project releases / build from source | APK on official GitHub releases / build from source |
| Version source used by this guide | Official GitHub release feed plus Apple cross-check when available | Official GitHub release feed |
iOS verification
Use the public App Store listing for normal installation. Apple publishes the current public version, release date, minimum OS, and release notes. TestFlight is a separate beta channel and is not required for the public release.
The official iOS repository is the source for code, project notices, and GitHub release history. A store version and a Git tag may format the same number differently—for example, 1.7.0 versus v1.7.0.
Android verification
The Google Play package must be com.bitchat.droid. An older or unrelated package name is not interchangeable.
If Google Play is unavailable and you choose to sideload, open the official Android releases, select the release you intend to install, and use only its attached APK asset. Compare the digest published with the asset when available. Do not download a copy re-hosted by this guide or an unknown APK site.
Why versions differ
The platforms have different repositories, operating-system APIs, background limits, permission systems, and release-review processes. A new Android version does not imply that the iOS listing is stale, and vice versa. Compare the date and notes within the correct platform channel.
Daily status check
The current version cards are updated from a Cloudflare Worker that runs once each day. It reads both official GitHub release feeds, attempts an Apple public-listing cross-check, then records the result and detected changes in Workers KV. The page shows the last successful check time and links back to every primary source.
Automated version matching is useful for freshness; it does not verify source-to-binary reproducibility or software security.