Mobile SDKs
Run Speko voice conversations inside iOS, Android, React Native and Flutter apps.
The mobile SDKs put a Speko voice agent inside your app. Each one captures the microphone, plays the agent's audio, streams a live transcript, and handles mute, volume, typed messages and hang-up. They match the browser SDK @spekoai/client, so the concepts and names carry over.
The mobile SDKs are in preview. Version 0.1.0 is not yet on the package registries; each platform page says how to build it from source until it is.
How a call starts
Your app never holds a Speko API key. Your backend creates the session with POST /v1/sessions and returns three short-lived values: transport, transportToken and transportUrl. The app passes them to VoiceConversation.create. Mint a session on your backend shows the server side once for every platform.
Pick your platform
Swift (iOS)
Swift Package and CocoaPods. iOS 15+.
Kotlin (Android)
Android library with coroutines and Flow. minSdk 24.
React Native
@spekoai/react-native with a useVoiceConversation hook. Needs a dev build, not Expo Go.
Flutter
speko_client for iOS and Android, with Streams.
What the mobile SDKs support
| Feature | Swift | Kotlin | React Native | Flutter |
|---|---|---|---|---|
| Cascade sessions over LiveKit | Yes | Yes | Yes | Yes |
| Cascade sessions over Daily (Pipecat agents) | Yes (Swift Package Manager only) | Yes | No | No |
| Reconciled transcript | Yes | Yes | Yes | Yes |
| Typed chat turns | Yes | Yes | Yes | Yes |
Provider-direct S2S (RealtimeVoiceConversation) | No | No | No | No |
Call listening (CallListener) | No | No | No | No |
A session your platform cannot run fails with the UNSUPPORTED_TRANSPORT error before any network call.