Pick the surface you want to live in, then verify the posted build.
Android, Windows, and Ubuntu are the first committed native surfaces. The browser still matters for onboarding, lighter sessions, settings, and immediate access when no posted native build exists yet.
Posted Build Feed
3/3 native surfaces have a posted build
GitHub Releases is the source of truth. Each platform card below shows the latest release tag that actually contains that platform's posted artifacts.
Posted assets
6
Native surfaces live
3/3
Release tags represented
2
Start with the surface that matches the moment, not the slogan.
Posted builds can land on different tags. The right choice is whichever surface is actually available and best suited to the session you are starting.
Need the fastest start
Use the browser first. It covers onboarding, invite review, settings, and lighter chat without waiting for a native install.
Start On WebNeed a daily mobile home
Choose Android when a posted build exists. It remains the first-wave native client for day-to-day use.
Check AndroidNeed a desk-first surface
Choose Windows or Ubuntu when a posted build exists. If neither is posted, treat web as the fallback instead of guessing.
Open Release Feed.apk
Android
Primary beta client
The main way to use EmberChamber. Native client with local device storage and relay-assisted delivery.
Best for
Pocket-first daily use
- emberchamber-refs-tags-v0.1.0-beta.16-release.aab • 63 MB
- emberchamber-refs-tags-v0.1.0-beta.16-release.apk • 91 MB
.exe / .msi
Windows
First-wave desktop
Full desktop experience in a native Tauri shell for auth, messaging, groups, invites, and settings.
Best for
Longer sessions and desk-first use
- EmberChamber_0.1.0_x64-setup.exe • 1.9 MB
- EmberChamber_0.1.0_x64_en-US.msi • 2.9 MB
.deb / AppImage
Ubuntu
First-wave desktop
Packaged as .deb and AppImage for Linux operators and desktop-heavy testers who want the same first-wave desktop scope as Windows.
Best for
Linux operators and native desktop fans
- EmberChamber_0.1.0-beta.16_amd64.AppImage • 89 MB
- EmberChamber_0.1.0-beta.16_amd64.deb • 4.5 MB
What each surface can actually do.
All surfaces share the same relay contracts and local-first direction, but not the same current encryption maturity. Browser DMs and new groups are ahead of legacy compatibility history and native attachment encryption, so read these cards as current-state guidance rather than parity claims.
browser
Web
Fastest start — no install
- Onboarding & registration
- Direct messages
- Group messages
- Invite review & management
- Device-local search
- Account recovery
- Settings
- No push notifications
.apk
Android
Primary daily use
- Everything in web
- Local SQLite cache
- Native device integration
- Installable daily client
- Push wiring is complete on mobile and relay. Production delivery requires EMBERCHAMBER_FCM_SERVICE_ACCOUNT_JSON and EMBERCHAMBER_PUSH_TOKEN_SECRET to be configured as relay secrets — see the operator playbook.
.exe / .msi
Windows
Desktop daily use
- Everything in web
- Longer sessions
- Native desktop shell
- No desktop push channel yet
.deb / AppImage
Ubuntu
Linux / operators
- Everything in web
- Longer sessions
- .deb and AppImage packaging
- No desktop push channel yet
Beyond First Wave
iPhone and macOS remain later-surface work.
They still exist in the repo, but the first-wave release discipline is focused on Android, Windows, Ubuntu, and the browser companion.
Every client uses the same hosted-delivery model, but current history and attachment handling still differ by path.
Keys, search, and DM history stay device-centered, even though legacy group history and native attachment encryption are still being migrated.
If a platform build is not posted there, assume web is still the right surface for now.