The HTML representation method replays a mobile app session in Browser Based Replay as it would an HTML web session. Without the HTML representation method, you would view the mobile app session as a series of screen captures.
There are several advantages to using the HTML representation method to replay mobile app session over screen captures.
- Ability to mask private information
- Ability to draw user interactions (UI events) onto the HTML pages that are created from the JSON data
- Smaller data size
HTML representation limitations
When replaying HTML representations of sessions that are generated from Android apps, there are often empty target pages in the Navigation List. During rendering, the target pages are converted to ScreenViews and UI Events. However, the original target pages remain in the Navigation List and appear as empty pages.
You can use the Ignore URLs rule to remove any of these original pages from the Navigation List that are not required.
To remove these original pages from the Navigation List, right-click the target.php page in the Navigation list, and click Remove this page from Replay.
The Ignore URLs rule does not work on sessions that are generated from iOS apps.
The HTML Representation method uses JSON data that is captured by the CX Mobile Logging Frameworks to create a collection of HTML pages. Each page is a collection of UI events within a JSON string. When the Replay Server finds a hit with a JSON string:
- Type 10 messages are converted into HTML through a template engine to render the collection of HTML pages that represent the mobile app screens
- Type 4 messages that follow a Type 10 message are filtered to produce associated UI Events that are visible in the Navigation List
The message breakdown provides you with a deeper insight into your mobile app sessions.
The templates that are used by the template engine can be customized to meet your business needs. To configure your templates, contact Professional Services.
When you replay a mobile app session and use a target page that does not match the naming convention of TealeafTarget.*, you might see native UI events that are associated to your unconventional target pages when they belong to an earlier page. To avoid this association, create an Ignore URL replay rule to filter your unconventional target pages out of the Navigation List.
Replaying mobile app sessions through HTML representation requires configuration of the Logging Framework.