Rendering modes
Rendering Modes: Handling Sensitive Data at the Whole Screen Level
Rendering modes is only fully available on some platforms. Please consult the respective platform API reference to see what rendering modes are available.
When your app shows sensitive or unnecessary data that you don’t want to record, you can set a Rendering mode. Rendering modes render your app in different ways to protect the information shown in your app to varying degrees. The detail of the session recording is based on the rendering mode you set. The Smartlook SDK contains three rendering modes:
Rendering mode | What is recorded |
---|---|
Native | Regularly captures the app screen which the SDK immediately processes to remove sensitive data. The frames are then complied to make the session recording. |
Wireframe | Renders the app using only a wireframe representation of the screen data. No user data is recorded. |
No rendering | No content is recorded. |
Wireframe rendering mode
Wireframe rendering is the preferred rendering mode for complete user privacy. Wireframe rendering removes all sensitive information from session recordings and replaces it with a representation of the app screen. Using the wireframe rendering mode removes any questions of user data protection.
When the default Native rendering is enabled, the Smartlook SDK records user sessions in both Native and Wireframe rendering modes. You can switch between rendering modes when viewing user sessions in the player. You can view wireframe mode in the player by clicking the Wireframe button.
Examples of wireframe rendering:
Example 1 | Example 2 |
---|---|
Setting the default Rendering Mode
The default rendering mode of the SDK is Native. You can change the rendering mode as described in the API reference.
Currently, the following platforms support wireframe rendering:
Updated almost 2 years ago