It depends on the duration of the actual recording.
We are preparing a new setting for adjusting the quality within the project settings. Adjusting the quality can increase/decrease the size of the video.
The video size is determined by the bitrate. Default bitrate for both the iOS and Android SDKs is 80 000 b/s. That should generate data of an approximate size of 0.5 MB per minute. The video quality depends on the resolution used with a certain bitrate setting.
The video quality setting is in progress. Users should be able to choose the right setting for their app in the project setting.
The video upload is done in an asynchronous manner, in the background. The data are uploaded in parts. The session is then made available on the Smartlook Dashboard within 10 minutes.
That’s up to you. Smartlook allows you to decide if you want the sessions to be uploaded exclusively using a Wi-fi connection or by using the user’s mobile data connection. You can turn this option on or off in the project settings.
Yes, it is. The initializing method can be selectively called for a specific group of users. You can achieve this by wrapping the initialization method with the appropriate logic. For example, you could check if the user is a beta/tester user.
The initialization method is what makes the Smartlook run in your application. It’s up to you to define the criteria under which the SDK will initialize.
You can already use Smartlook SDK with React Native.
We are now working on recording games built with Unity. If you are a game developer, feel free to get it touch, we already have a working version.
We currently support integration with Crashlytics. Additional integrations, such as Google Analytics, Mixpanel and Slack will be available soon.
Our session replay is near real-time. The data for the session recordings is uploaded to our servers as soon as the user finishes the session. This requires an internet connection.
For privacy reasons, we do not show form inputs and web view content. We do not show web view content because we are unable to determine if the web view container depicts any sensitive data. Thus, we have decided not to capture such content.