Examples and Product Recipes
Start with the product your users recognize, then open the operation guide for the SDK you are actually using. Each SDK row below names its own public symbols and lifecycle.
Familiar product shapes
| Product | What the blueprint explains | Architecture blueprint |
|---|---|---|
| Private consultation or WhatsApp-style call | Fixed room, secure join, two-person media, familiar controls, leave/end, cleanup | Compact call |
| Live host dashboard | Host layout, participant visibility, moderation, screen/content controls | Live host dashboard |
| Guest queue | Waiting users, requests, panelists, permission changes | Live guest queue |
| Support or AI console | App-owned shell, participant media, data/control integration, teardown | Support and AI console |
| Interactive classroom | Waiting, requests, polls, whiteboard, breakouts, recording | Interactive classroom |
| Remote podcast | Audio rendering, participant state, recording controls, cleanup | Remote podcast |
These pages are deliberately labeled blueprints: they explain composition and release behavior, but they are not presented as runnable tutorials. Complete code belongs in the SDK-specific operation paths below. A future page may be called a tutorial only after its code can be copied into a declared project, compiled, run, and followed through success, recovery, and cleanup.
ReactJS
- Build by outcome: complete room lifecycle, participants, collaboration, and recording.
- Customize: React UI overrides and the complete custom UI checklist.
- Blueprints: use the six product-composition pages above, then take runnable code from the linked React operation guides.
Angular
- Build by outcome: complete room lifecycle and participant collaboration.
- Customize: Angular UI overrides.
- Example: the lifecycle guide includes a declaration-checked application adapter and release checklist.
Vue
- Build by outcome: complete room lifecycle and participant collaboration.
- Customize: Vue UI overrides.
- Example: the lifecycle guide includes a Vue-specific room adapter and checks.
React Native
- Build by outcome: native room lifecycle and participant collaboration.
- Customize: React Native UI overrides.
- Example: the room guide includes native URL, permission, recovery, and cleanup behavior.
Expo
- Build by outcome: Expo room lifecycle and participant collaboration.
- Customize: Expo UI overrides.
- Example: the room guide includes an Expo-specific backend adapter and local policy tests.
Flutter
- Build by outcome: secure room and media lifecycle and participant collaboration.
- Customize: Flutter UI overrides.
- Example: the Flutter guide shows secure callbacks, media controls, screen sharing, leave, and release checks.
Android
- Build by outcome: Android room and Compose controls.
- Customize: Android Compose overrides.
- Example: the Android guide contains a copy/paste Compose room and custom control surface.
Kotlin Multiplatform
- Build by outcome: KMP room lifecycle and participant collaboration.
- Customize: Kotlin Compose overrides.
- Example: the lifecycle guide includes shared secure-room adapters and state observations.
Swift and Apple
- Build by outcome: hosted room and bridge controls.
- Customize: Apple presentation ownership.
- Example: the Swift guide shows installation, hosted room mounting, media controls, permissions, and release checks.
Unity
- Build by outcome: Unity room lifecycle and participant collaboration.
- Customize: Unity scene ownership.
- Example: the room guide includes the headless client lifecycle and media backend boundary.
Shared core
- Build by outcome: framework-owned room lifecycle and participant collaboration.
- Customize: shared-core UI ownership.
- Example: the shared-core guide binds the non-rendering room primitives to an application-owned UI.
Build a private consultation or direct call
This sequence covers booking, messaging, healthcare, support, and other two-person products:
- Reserve or create the room on your backend and store its stable room ID.
- Resolve the current join destination when the session starts.
- Authenticate the application user and return only the approved room handoff.
- Mount the SDK runtime inside your application; do not redirect users away.
- Render local preview, remote audio, remote video, and clear permission errors.
- Add microphone, camera, camera-switch, screen-share, and leave controls.
- Distinguish participant leave from host end.
- Stop tracks and clear room state before another call.
For a fully branded interface, follow the custom UI responsibility checklist. It covers the behaviors normally supplied by the complete room—including the easy-to-miss remote audio grid and alert surface.
Backend and SDK can be combined
Your backend may create, reserve, join, moderate, or terminate rooms through approved HTTP contracts while the SDK owns WebRTC media and visible room state. See platform HTTP and protocol operations and secure backend proxy. Keep long-lived account authority on the server.
Release test
Run the selected product journey with at least two users on target devices. Verify actual remote media, denied permissions, reconnection, participant updates, collaboration actions, leave/end semantics, cleanup, and a second call.