roadmap

The actual backlog, not a marketing slide

These are the real task IDs from our build plan, in dependency order. Green is shipped with tests. Orange is where work happens next. Nothing below is rounded up — when something is paused or rebuilding, it says so.

Shipped

• T-01

  Validation spike

  Before building anything, we proved the foundation: Synapse stood up, multi-device E2EE exercised end-to-end (with a database-level check that the server stores only ciphertext), Application Service round-trips in both directions, and licensing independently re-verified.

• T-02/T-03

  Scripted infrastructure + homeserver deploy

  Dev environment on GCP — VM, firewall, Postgres, Synapse, media storage, CDN — captured as numbered scripts so the whole environment is rebuildable from zero.

• T-04

  Phone-first accounts

  OTP-verified signup and login.

• T-05

  1:1 messaging

  Text, image, audio, video, document, and location messages with delivery and read receipts.

• T-06

  Multi-device E2EE

  Multiple devices per account with encryption-key session sync.

• T-07

  Background job queue

  Postgres-backed Oban queue for the platform’s async work.

• T-08

  Media pipeline

  Upload/download via S3-compatible storage behind a CDN.

• T-09

  Push backend

  Device-token registration and queued notification fan-out for APNs, FCM, and web push.

• T-12

  White-label layer

  Typed branding config with Xoyo as the reference brand.

• T-13

  Web client core

  React + TypeScript scaffold with the core messaging UI.

Now

• infra

  Re-provision the dev environment

  The original dev VM was torn down (cloud credits, not code). Because the environment is fully scripted, standing it back up — on GCP or any comparable provider — is a rerun, not a rebuild. This unblocks live end-to-end testing.

• T-10/T-11

  Application Service skeleton + test client

  Formalize the bridge skeleton the spike prototyped, plus a throwaway CLI client for exercising the server.

• T-14

  Mobile client

  React Native scaffold and core messaging UI for iOS and Android.

Next

• T-15/T-16

  OTA updates + push in the clients

  Self-hosted over-the-air delta updates for mobile, and wiring the shipped push backend into web and mobile clients.

• T-17

  Second branded client

  Build a differently-branded app from the same codebase — the proof that white-labeling actually holds.

• T-18

  End-to-end deployment + smoke test

  Everything running together on dev/staging, driven as a user would drive it. This is the gate for the private alpha.

• T-19–T-22

  Verification tail

  Full test-suite passes and code reviews across server, clients, and the white-label layer.

• Layer 2

  Organization bridge

  The full Glific bridge — contact mapping, session windows, template gating — as its own planned effort once the core platform is stable.

Milestone that matters to you

Private alpha opens after T-18 — the end-to-end smoke test. Waitlist members get access first, in order of signup.