It depends on the duration of the actual recording. We estimate that the mobile recording should generate data of an approximate size of 0.5 MB per minute.
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 bit-rate. The video quality depends on the resolution used with a certain bit-rate setting.
The video quality setting is already in progress. Users should be able to choose the right setting for their app in the project setting.
The recording is done in an asynchronous manner, in the background. This means that the running of your application is not affected. Once the user finishes his session, the data are then transferred to our servers, if there is. This, however, requires an internet connection. The recording of the session is then made available on the Smartlook Dashboard.
At the current moment, the data only gets transferred to our servers if there is a wi-fi connection.
We will give the developers an option to opt between “wifi-only” or enabling the usage of mobile data. “Wi-fi only” will be the default setting.
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.
We are currently working on making the Smartlook SDK compatible with React Native. Moreover, compatibility with several other technologies in on our pipeline.
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.