Files
Warp/apps
tajniak81andClaude Opus 5.5 b8ddbaacf3 Mobile calls: keep call memberships in memory; answering keeps the call screen
Found testing calls between two phones on the Compose call stack:

- The famedly SDK keeps only "important" state in memory for a room that
  hasn't been opened, so call memberships of other rooms were invisible:
  no ring (it was cleared at once, the call looking empty), no room-list
  marker. org.matrix.msc3401.call.member is now important state.
- The incoming-call card closed itself with Navigator.pop when the ring
  cleared, which popped the call screen pushed above it on Answer. The
  buttons now close the card first, and it closes itself only while it
  is the top route.

Tested: a voice call in a room of two (ring, answer, both connected
through LiveKit), and a video call in an encrypted room (to-device media
keys, frame cryptors OK on both sides, each phone showing the other's
video). The web client sees a phone's membership and rings for its
notification.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 09:08:01 +02:00
..

Clients

Directory What State
ui/ shared Vue 3 + Tailwind design system: tokens, fonts, icons, components in use by admin and web
admin/ admin web panel, served by its own optional warp-admin binary done for the current admin API
web/ web client (Vue SPA on matrix-js-sdk), served by its own optional warp-web binary rooms, timeline, sending text and files, invites; E2EE next
desktop/ Wails v3 shell reusing the web frontend next: web has a timeline
mobile/ Flutter app on the famedly Matrix SDK, Android first rooms, timeline, files, replies, reactions, threads, spaces, E2EE with QR and emoji verification, push, calls, sliding sync

The frontend packages are a pnpm workspace (pnpm-workspace.yaml at the repository root); the Go hosts join go.work.

pnpm install
pnpm admin:dev
pnpm web:dev