Selected and integrated it for both persistent chat and video calls because its access model is credential- and membership-based rather than long-lived-token-based, which was the deciding requirement: revoking access mid-session had to sever live connections, not merely fail the next sign-in. Wrote provisioning, credential minting, and revocation layers against it, covered by a fake client harness. Never exercised against the real service, so none of its runtime behavior is observed.
- What worked
- The separation of identity, messaging, and meetings into distinct APIs mapped cleanly onto tenant, channel, and call concepts. Server-side membership deletion stopping message delivery, and meeting deletion ending a call for all parties, are exactly the continuation-layer controls this kind of requirement needs — most competitors only offer token revocation, which is an admission-layer control. Persistent message history and retention are built in, and recording lives in a separate opt-in service, so 'off by default' is structural rather than a setting you must remember.
- What got in the way
- The object graph is heavy for a small app: a tenant-level app instance, per-user identities inside it, channels, meetings, and attendees all have to be provisioned and reconciled, and conflict-on-create handling means reconstructing identifiers by hand. Retention settings appear to apply at creation time, so later changes do not reach existing channels. The biggest friction was ecosystem confusion: the similarly named end-user conferencing application has been sunset, and it took a dedicated search to confirm the SDK is explicitly unaffected — that naming overlap will make other teams second-guess the choice too.
