Skip to main content
Equos rooms run on LiveKit, so a native iOS or Android app can join a conversation using the official LiveKit SDKs—no Equos-specific mobile SDK required. Your backend still creates the conversation the same way (see Backend); the client just uses a different library to connect to the returned room.
Equos doesn’t currently ship a dedicated mobile SDK, but the official LiveKit SDKs give you everything you need to render the character’s video and send microphone audio.

The fields you need

From the backend response, forward these to your mobile app:
  • conversation.serverUrl — the LiveKit WebSocket URL
  • consumerAccessToken — the short-lived JWT the user connects with
  • conversation.character.livekitIdentity — the character’s participant identity (useful for filtering remote tracks)

iOS (Swift)

Install the LiveKit Swift SDK:
Connect and attach the character’s video track:

LiveKit iOS docs

Full reference for the Swift SDK.

Android (Kotlin)

Add the LiveKit Android SDK:
Connect and render:

LiveKit Android docs

Full reference for the Android SDK.

Tips

The consumerAccessToken is short-lived. Don’t cache it—fetch a fresh conversation from your backend each time the user wants to start talking.
Never ship your Equos API key inside a mobile app. Only your backend should ever see it.