Native media
How calls, livestreams and screen sharing run natively on Android and iOS, and what has been verified.
Native apps use LiveKit's native SDKs (LiveKit Android 2.30, LiveKit Swift 2.19) through the Lynkoria Android and iOS SDKs. React Native uses the same native SDKs through a TurboModule. Nothing renders media in a WebView or in JavaScript.
Joining
- The app asks its product backend to join a call.
- The backend authorizes the user, then calls
POST /v1/calls/{id}/join-tokenwithuserId,deviceId,displayNameandrole. - The app connects with the returned
{ url, token }:LynkoriaCall.join(context, credentials)(Android),LynkoriaCall.join(credentials)(iOS) orjoinCall({ getJoinToken })(React Native).
Roles are fixed by the token. A viewer cannot publish even if the app tries; promotion goes through POST /v1/calls/{id}/participants/{identity}/permissions from the backend.
Capabilities
| Capability | Android | iOS | React Native |
|---|---|---|---|
| 1:1 and group audio/video | LynkoriaCall | LynkoriaCall | NativeCall |
| Livestream publish / view | Same API; role from token | Same | Same |
| Screen share | MediaProjection (startScreenShare(intent)) | In-app capture; system-wide needs a ReplayKit Broadcast Upload Extension | startScreenShare() |
| Audio routing | AudioSwitch devices | AVAudioSession (LiveKit manages the session) | audioDevices() / selectAudioDevice() |
| Reconnection | LiveKit reconnect; state RECONNECTING | Same | onStateChange |
| Video rendering | TextureViewRenderer | SwiftUIVideoView / VideoView | <LynkoriaVideoView> |
Background and lifecycle
- Calls continue in the background on iOS only with the
audio(andvoip) background modes and an active CallKit call. On Android, keep a foreground service of typephoneCallduring calls on Android 14+. - The messaging client should disconnect in the background; push delivers incoming calls and messages, and reconnecting replays missed events.
Verification status
lynkoria-android and the Android sample compile with ./gradlew build, and the Lynkoria Swift target compiles for macOS with swift build. Nothing has run on a device or emulator, the iOS-only CallKit/PushKit code needs an Xcode iOS build, and the React Native native modules have not been compiled in a host app. React Native codegen accepted the specs and the generated signatures match the native implementations. Device validation is tracked in testing completion criteria.