SDK Guides
Choose the package for the framework or platform your application already uses. Start with its supplied room, prove create and join, then add product operations one at a time.
Build this: compare runnable Starter Projects. View source: start with the multi-platform native reference, then return to this SDK guide for package-specific operations and limitations. Before release, put reusable create and join authority behind the secure backend proxy.
Current SDK packages
| Application | Package | Guide |
|---|---|---|
| React web | mediasfu-reactjs@4.3.7 | ReactJS |
| Angular web | mediasfu-angular@2.4.1 | Angular |
| Bare React Native | mediasfu-reactnative@2.4.5 | React Native |
| Expo-managed React Native | mediasfu-reactnative-expo@2.5.5 | React Native Expo |
| Vue web | mediasfu-vue@1.2.1 | Vue |
| Flutter | mediasfu_sdk@2.3.6 | Flutter |
| Framework or wrapper authors | mediasfu-shared@1.2.5 | Shared core |
| Android | com.mediasfu:mediasfu-sdk-android:1.0.7 | Android |
| Kotlin Multiplatform | com.mediasfu:mediasfu-sdk:1.0.7 | Kotlin |
| Swift / Apple | MediaSFUAppleSDK 0.1.3 + MediaSFUSDK 1.0.3 | Swift |
| Unity | com.mediasfu.unity@0.1.0-preview.2 | Unity |
Choose Android for an Android-only Compose app, Kotlin Multiplatform for shared Kotlin code, or Swift for a native Apple app. Each guide starts with its own installation and room example.
Develop first, secure before release
For isolated local development, use restricted and revocable development credentials if your SDK's direct helper requires them. Do not commit them. Before distributing the app or opening it to external testers, move reusable MediaSFU Cloud credentials behind your authenticated backend. The client should receive only the room result or short-lived authority it needs.
- Install the package for your application.
- Prove create or join with the supplied room UI in local development.
- Test microphone, camera, remote media, leave, and host end with two users.
- Complete the production credential boundary before release.
- Choose UI overrides, custom components, or headless mode only after the room works.
Reference path
Find the right implementation guide
Use the sidebar group for your SDK as your primary guide. Each group brings together its setup, room lifecycle, customization options, tutorials, and known limitations for that platform.
Build by outcome is useful when you know what you want to add—such as joining a room, managing participants, collaboration, or recording. Focus on your SDK by choosing the guidance that names its package and version.
Before release
- Test on the browsers or physical devices you support.
- Test each product role, including denied actions and reconnect.
- Confirm local and remote media rather than stopping at a connected socket.
- Confirm participant leave differs from semantic host end.
- Stop local tracks, remove listeners, clear app-owned room data, and revoke temporary authority.
- Never log credentials, reusable room authority, private messages, or media contents.
For signatures and generated package references, open the API reference.