Experience recipes
An endpoint tells you how to make one request. A recipe shows the requests, client state, and UI controls that make a complete experience.
Start with the outcome you want. Each recipe includes an interaction map, request sequence, implementation shape, and links to every operation involved.
Build a complete group chat
Join, load the room, receive updates, send messages, add reply and reaction controls, recover from reconnects, and exit cleanly.
Interaction designAdd message actions
Turn each message row into a useful surface with quote, thread, react, edit, delete, and report actions.
Trust & safetyModerate a live chat
Connect user reports to moderator queues, decisions, room-level effects, and the live event stream.
Live telemetryShow live audience activity
Build synchronized presence counts, reaction pulses, and continuous activity meters without storing raw client events yourself.
What belongs in a complete experience
Section titled “What belongs in a complete experience”| Layer | What the user sees | What your integration handles |
|---|---|---|
| Entry | A room opens with current content | Identity, room lookup, join, initial cursor |
| Live state | New activity appears without refresh | Updates loop, cursor persistence, reconnect |
| Actions | Composer and contextual controls work | Send, reply, quote, react, edit, delete, report |
| Safety | Reporting and moderator decisions take effect | Queues, decisions, user effects, event updates |
| Lifecycle | Presence remains accurate | Session touch, tab visibility, exit |
Foundation recipes
Section titled “Foundation recipes”Use these focused recipes when you need one part of the flow: