Skip to main contentOverview
The Mobile SDK has an offline mode to keep your application working during network problems. This ensures a session is not interrupted if the device loses its internet connection.
What Will You Learn?
In this guide, you will learn how to:
- Handle network interruptions gracefully using the offline mode.
What Happens In The Offline Mode
When the SDK enters offline mode, it handles everything in the background so the user is not interrupted. The SDK will:
-
Continue to record and store audio securely on the device.
-
Save all session events that happen during the outage.
-
Automatically upload all saved audio and events when the connection returns.
The SDK notifies your app about these status changes using session delegate events.
Network Buffer For Temporary Connection Problems
Before, the SDK used to directly jump into offline mode when it detected a small network issue. This was not ideal as it would interrupt the user experience.
To address this, the mobile SDK now uses a 15-second buffer to handle temporary connection problems. This gives you time to show a notification in your UI, like Connection unstable, before the session goes fully offline. This is important to ensure a smooth user experience.
Common Causes For The Offline Mode
A session can enter offline mode for several reasons:
-
Poor or lost Wi-Fi or cellular connectivity.
-
The device switches between networks (e.g., Wi-Fi to cellular).
-
A temporary problem with the backend service.
-
A dropped connection while streaming audio.
-
An issue with an authentication token.
Important notesKeep the following key features of offline mode in mind:
-
The SDK manages all transitions between offline and online modes automatically.
-
Audio quality and session integrity are always maintained.
-
The SDK can queue multiple offline sessions and will upload them in order once a connection is available.
-
All data stored locally on the device is encrypted and secure.
-
Offline recording is optimized to conserve battery life.