Quick Usage

One map for MediaSFU integration decisions.

Use this page when you need the fastest route from product idea to the right MediaSFU surface: no-code dashboard guide, developer console guide, framework SDK, generated API reference, or React visual preview.

Recommended order

  1. Pick the SDK that matches your app shell and deployment target.
  2. Create rooms through a backend path so secrets never enter the client bundle.
  3. Launch once with the prebuilt room UI to validate media, permissions, and account configuration.
  4. Choose the lightest UI ownership model that gives the product the control it needs.
  5. Use generated API docs only after you know which package surface or helper you are integrating.
10SDK paths
Web + nativeDeployment targets
Prebuilt to headlessUI ownership
Cloud or OpenBackend choice
Documentation map

Pick the right public surface.

The old routes still point somewhere useful, but each surface now has a clearer job. Open docs and Storybook in a new tab when you want to keep your place in the main MediaSFU site.

Build path

Choose how much of MediaSFU should be visible.

Full UI-mode guide
Selected path

Fastest working room

Use a framework SDK and let MediaSFU render the room while you validate credentials, permissions, and room flow.

SDK matrix

All SDKs, with the best matches first.

All ten SDK paths remain visible as you compare build modes. Recommended matches are sorted first; install commands resolve the current registry release where supported, while native guides provide pinned baselines.

Compare all SDKs
mediasfu-apple-sdk

Swift / Apple

Swift Package Manager
iOSiPadOSmacOS
Also supported

Native Apple apps that need Swift-first room, media, and device control across supported Apple platforms.

https://github.com/MediaSFU/mediasfu-apple-sdk.git
mediasfu-unity-sdk

Unity

Unity Package Manager
UnityC#WebRTC
Also supported

Unity experiences that need real-time voice, video, and room state inside a game or immersive application.

https://github.com/MediaSFU/mediasfu-unity-sdk.git
mediasfu-shared

Shared Core

npm
TypeScriptHeadless
Also supported

Framework-agnostic TypeScript logic when you own the full UI and orchestration layer.

npm i mediasfu-shared socket.io-client mediasoup-client
Implementation playbooks

Use these guides instead of guessing from snippets.

The snippets below are orientation only. The linked docs pages are the canonical place for setup details, security boundaries, and framework-specific usage.

Copy-ready starters

Small snippets, clear boundaries.

These examples show shape and intent. Keep production credential handling on your backend and move to the SDK page once you choose a framework.

Generated API docs
ts

Backend boundary shape

// Keep MediaSFU credentials on the server.
app.post('/api/rooms/create', async (request, response) => {
  const room = await createRoomForClient({
    apiUserName: process.env.MEDIASFU_API_USERNAME,
    apiKey: process.env.MEDIASFU_API_KEY,
    roomName: request.body.roomName,
    mode: request.body.mode,
  });

  response.json(room);
});
tsx

React prebuilt room mount

import { MediasfuGeneric } from 'mediasfu-reactjs';
import 'mediasfu-reactjs/dist/main.css';

export function Room({ roomCredentials }) {
  return (
    <MediasfuGeneric
      options={{ credentials: roomCredentials }}
    />
  );
}
text

Native and immersive package sources

# Flutter
flutter pub add mediasfu_sdk

# Swift Package Manager
https://github.com/MediaSFU/mediasfu-apple-sdk.git

# Unity Package Manager: Add package from Git URL
https://github.com/MediaSFU/mediasfu-unity-sdk.git

# Kotlin / Android
implementation("com.mediasfu:mediasfu-sdk-android:1.0.1")

# Kotlin Multiplatform
implementation("com.mediasfu:mediasfu-sdk:1.0.1")
Choose by audience

Start from the guide that matches the job.

Use the dashboard guide for no-code operations, the developer console guide for API features, SDK guides for framework setup, generated references for exact symbols, and Storybook for React UI inspection.

Open documentation map