xoyo
rebrand:

product

What it does, shown on the real thing.

Every screenshot on this page was captured from the development build on 3 September 2026 with test accounts. Nothing is a mock-up. Feature status further down maps to numbered requirements in the product spec and to task ids in the roadmap.

Web app

A three-zone layout: conversations, the thread, and a devices panel. Runs in any modern browser against your own homeserver.

Sign-in card asking for a phone number, with a note that a one-time code will be sent by SMS
Phone-first sign-in. A number and a one-time code, the flow people already know. Email is optional and only for recovery.
A conversation with the green banner: messages in this chat are end-to-end encrypted; outgoing messages carry double ticks
An encrypted conversation. The green banner is the room’s live encryption state, not a slogan. Double ticks are read receipts.
The same conversation from the other participant's account
The other side. The same room from the second account. Names come from Matrix profiles; identity is the verified phone number underneath.
Your devices panel listing the current web session as verified with a lock icon
Your devices. Every session you hold, with its verification state. Keys move between your own devices, never through the server in the clear.

Mobile app

React Native for iOS and Android, sharing logic with the web client. Shown here on the iPhone simulator.

Chats list on the phone: each conversation carries a lock or a warning glyph showing its encryption state
Chats. The trust glyph sits next to every conversation: a lock for encrypted rooms, a warning for rooms that aren’t.
A thread on the phone with an amber banner: not encrypted, messages are protected in transit but readable by the server operator
A thread. Bubbles, receipts, attachments and location from the composer. The banner says exactly what this room is.
An encrypted room on the phone with a green banner explaining that mobile encryption is not yet available and sending is disabled so nothing is sent unprotected
Honesty over pretence. Mobile device encryption is the next tier of work. Until it lands, the phone refuses to send into an encrypted room rather than send unprotected.
Devices screen on the phone listing two devices with their last-seen times
Devices. One account, many devices. This phone and a web session, each with its last-seen time.

Feature by feature

Chips are derived from the task ledger. Shipped means built with tests and verified live. Building means in progress now. Planned means not started.

  • F-1

    Phone-first accounts shipped

    Sign up with a phone number verified by one-time code. Your phone number is your identity, mapped to a Matrix account behind the scenes.

  • F-2

    Messaging with receipts shipped

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

  • F-3

    Multi-device, one identity shipped

    Phone and web signed in together, history and keys synced between your devices with Matrix’s device verification.

  • F-4

    End-to-end encryption, honestly labeled shipped

    Direct conversations are encrypted by default with Olm/Megolm. Every room shows its state; bridged rooms are marked in amber, always.

  • F-6

    Media that scales shipped

    Uploads and downloads through S3-compatible object storage behind a CDN, content-addressed, on any provider that speaks S3.

  • F-9

    Reliable background work shipped

    Push dispatch, media processing and webhook delivery run on a Postgres-backed job queue. No extra broker to operate.

  • F-11

    White-label branding layer shipped

    Name, icon, logo, splash, colors and bundle identifiers come from one typed config. The brand switcher in this site’s header runs on the same tokens.

  • F-8

    Web client shipped

    React and TypeScript. Sign-in, conversations, encrypted rooms, devices. Responsive layout below tablet width is on the fix list.

  • F-7

    Mobile client shipped

    React Native for iOS and Android with the core messaging UI. Device encryption on mobile is the next tier; over-the-air updates follow it.

  • F-10

    Organization bridge into Glific shipped

    A Matrix Application Service exposing a Gupshup-compatible API: send, template send, template discovery, signed webhooks, session window and consent, interactive messages, pacing, health. Verified live with a Glific instance. Details on the organizations page.

  • F-5

    Push notifications building

    The backend fan-out for APNs, FCM and web push is shipped. Wiring it into the apps waits on production push credentials.

  • T-15

    Instant mobile updates planned

    Self-hosted over-the-air delta updates so fixes reach phones without waiting on store review.

Want to see it on your own numbers?

A pilot runs on a server we stand up for you or on yours, with your brand on the apps. Tell us what you run over chat today.

Talk to us See the full roadmap