ReactJS
React web apps that need the richest documented MediaSFU UI and headless surface.
npm i mediasfu-reactjsUse 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.
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.
Use a framework SDK and let MediaSFU render the room while you validate credentials, permissions, and room flow.
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.
React web apps that need the richest documented MediaSFU UI and headless surface.
npm i mediasfu-reactjsAngular apps that prefer DI-friendly wrappers and shared-backed room behavior.
npm i mediasfu-angularBare React Native apps that need native mobile media, room UI, and device permissions.
npm i mediasfu-reactnativeExpo-managed mobile apps that want MediaSFU room flows inside an Expo app shell.
npm i mediasfu-reactnative-expoVue 3 applications that want composition-friendly SDK setup and UI control.
npm i mediasfu-vueFlutter apps across mobile, web, and desktop from one Dart codebase.
flutter pub add mediasfu_sdkNative Android and Kotlin Multiplatform apps with Compose-first MediaSFU surfaces.
implementation("com.mediasfu:mediasfu-sdk-android:1.0.1")Native Apple apps that need Swift-first room, media, and device control across supported Apple platforms.
https://github.com/MediaSFU/mediasfu-apple-sdk.gitUnity experiences that need real-time voice, video, and room state inside a game or immersive application.
https://github.com/MediaSFU/mediasfu-unity-sdk.gitFramework-agnostic TypeScript logic when you own the full UI and orchestration layer.
npm i mediasfu-shared socket.io-client mediasoup-clientThe snippets below are orientation only. The linked docs pages are the canonical place for setup details, security boundaries, and framework-specific usage.
These examples show shape and intent. Keep production credential handling on your backend and move to the SDK page once you choose a framework.
// 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);
});import { MediasfuGeneric } from 'mediasfu-reactjs';
import 'mediasfu-reactjs/dist/main.css';
export function Room({ roomCredentials }) {
return (
<MediasfuGeneric
options={{ credentials: roomCredentials }}
/>
);
}# 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")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.