Tealeaf receives mobile dimensions from two sources, Tealeaf UI Capture and WURFL. WURFL is used as a fallback if UI Capture is not installed.

If both sources are missing, there is no data to render the mobile skin. A default dimension is applied and you will see the skin with no page inside.

Note: A mobile license is required for the mobile skin to show in the Mobile Replay.

Tealeaf UI Capture can provide better dimensions. Therefore, it is recommended to have UI Capture installed for better replay of mobile sessions.

Limitations in replay of mobile visitors

Replay of mobile visitor sessions works best for web pages that are designed for a mobile platform. These web pages are designed to fit the smaller screens of mobile devices and work well within the limitations of the device.

Personal computer designed web pages

Replay of web pages that are targeted for personal computers can vary widely from the actual experience. Many cell phones and cell phone networks modify the web page to best fit the display. Typical modifications include collapsing of frames, restructuring of tables, and resizing of images.

Because these modifications are specific to the device or network, Tealeaf does not attempt to emulate these behaviors. As standards improve for presentation of content that is targeted for personal computer screens delivered to small mobile screens, Tealeaf improves this emulation.

Mobile browser designed web pages

Replay of sessions for mobile devices that are captured from web applications that are designed for mobile browsers is likely to feature improved performance and visual display. However, if the content is delivered for a mobile-only device, there can be visual discrepancies in the replay, due to differences in the rendering and display issues of the browser controllers that are used in BBR.

Depending on the pixel density of the device and the pixel density of the monitor on which you are viewing the replay, the physical size of the displayed image cannot match the original image.

For Android devices, if the width or height is fewer than 320 pixels, the image is not scaled.

Limitations for unlicensed components

When CX Mobile module is not licensed, the following limitations are applied to replay of mobile-based sessions:

• No display of mobile-specific events, such as scroll and touch
• No display of mobile device data during replay
• No use of a mobile skin (Extended user agent parsing is also required.)
• No display of device orientation changes
• No resizing of the screen to the mobile browser dimensions

The underlying data is captured independent of the license; enabling the license allows mobile-based replay of already captured sessions.

Android-based device replay limitations

Some mobile replay limitations are because of the basic differences between mobile web design and desktop web design. Some mobile replay limitations are device-based. Android-based device Replay limitations include:

• Android-based devices can screen capture the main window but cannot capture pop-up windows.
• For hybrid applications, screen capture can be captured in a random order, and some screen capture can be missing due to timing issues.
• Clicks of the device buttons are not captured by the Android logging framework.
• When an Android-based web browser is minimized, the application is slept, instead of killed. As a result, session identifiers are not renewed when the application is reawakened, and the same session identifier can be used for what are two separate visitor sessions. When hits from this visitor's sessions are gathered into Tealeaf, the session data is mixed under a single session identifier.

Screen dimensions for mobile devices

BBR has multiple mechanisms for evaluating the screen dimensions as reported from the mobile device.

• If UI Capture is deployed and is submitting UI events to Tealeaf for capture, then the screen dimensions that are used in replay are taken from UI events that are captured in first hit of the session in replay from the browser of the mobile device.
• If UI Capture is not deployed or if UI events are not reported and captured in the first hit, then screen dimensions are taken from the WURFL standard for the device that is used by the visitor.

  Note: Because the device and the browser for the device can't report the same values, it is possible that replay of a session by using the screen dimensions reported by WURFL can not exactly match the dimensions of the captured session.

• If neither of the methods yields values for the screen dimensions, BBR set the screen dimensions during replay to the full, normal replay size.

User interface events captured from mobile browsers in BBR

If UI Capture is deployed, user interface events that are captured from mobile browsers are displayed in the Viewable Pages List in BBR.

Replay of scroll events that are captured by UI Capture is supported for mobile sessions only in BBR. Replay of scroll events are not supported for DOM Capture.

In addition to actions such as clicks, gestures such as pinching and zoom in and zoom out are displayed in BBR.

When the orientation changes in the session, the mobile skin is displayed along the new axis in BBR.