features

What it does, and what it doesn’t yet

Every feature below maps to a numbered requirement in our product spec (the F- tags) and to real tasks in the roadmap. Status chips are honest: shipped means built with tests, building means in progress, planned means not started.

• F-1

  Phone-first accounts shipped

  Sign up with your phone number, verified by one-time code — the flow people already know from every mainstream messenger. Email is optional, for account recovery only.

• F-2

  1:1 messaging with receipts shipped

  Text, images, audio, video, documents, and location sharing, with delivery and read receipts — built on Matrix’s Client-Server API rather than a homegrown protocol.

• F-3

  Multi-device, one identity shipped

  Phone and web signed in together, with message history and encryption keys synced across devices using Matrix’s device-verification and key-backup machinery.

• F-4

  End-to-end encryption, honestly labeled shipped

  Direct conversations are E2EE by default (Olm/Megolm). If a conversation is ever bridged to an external organization, the UI marks it visibly — no pretending the bridge doesn’t exist.

• F-6

  Media that scales shipped

  Uploads and downloads go through S3-compatible object storage behind a CDN, addressed by content hash, consistent with Matrix’s content-repository model.

• F-9

  Reliable background work shipped

  Push dispatch, media processing, and webhook retries run on a Postgres-backed job queue (Oban) — no extra broker to operate.

• F-11

  White-label branding layer shipped

  Display name, icon, logo, splash screen, color theme, and bundle identifiers come from a typed per-deployment config. Anyone self-hosting can ship their own branded client from this codebase — the brand switcher in this site’s header runs on the same token shapes.

• F-5

  Push notifications building

  The backend fan-out (device-token registry + queued dispatch for APNs, FCM, and web push) is shipped. Wiring it into the clients lands with the mobile app.

• F-8

  Web client building

  React + TypeScript. The scaffold and core messaging UI exist; it’s growing toward feature-complete alongside the mobile client.

• F-7

  Mobile apps with instant updates planned

  React Native for iOS and Android, with self-hosted over-the-air delta updates so fixes reach phones without waiting on store review.

• F-10

  Organization bridge (Layer 2) planned

  A Matrix Application Service that can bridge conversations to organizational platforms (our first target: Glific, the NGO communication suite). The skeleton is prototyped; the full bridge is a later, separate effort — and bridged rooms will always be labeled (see F-4).

Want something on this list sooner?

The fastest way to move a chip from planned to shipped is to build it with us.