When using Tealeaf to capture a mobile session, to replay the session in Tealeaf using the traditional replay, the images from the mobile application are sent to the Tealeaf server. If the images from the mobile application are already stored on the replay server, the mobile application does not upload the images during an active session. Uploading the images to the replay server reduces the amount of data sent and prevents any performance issues. Replay uses a unique identifier for each image and retrieves only the needed images from the replay server.

Note: If you are using enhanced replay, the Tealeaf SDK does screenshots of your app, and the screenshots are used for replay.

Collect images from your application

Before you upload the images from your application to the replay sever, you must collect the images from the application. Depending on whether you have an iOS application or Android application, the steps to collecting the images can vary.

iOS applications

For iOS applications, you can use the iOS image capture tool included with the iOS SDK. For more information, see Enabling traditional replay in the Tealeaf iOS SDK.

Android applications

For Android applications, you can use the image capture tool that is included with the Android SDK. For more information, see Android Image Capture tool.

Target simulator

The iOS and Android image capture tools should be the primary tool to capture images in your application for the respective environments. However, if the image capture tools cannot support your image replay experience, you can use the target simulator.

Target Simulator is a command-line program that runs on your local machine and acts as an Acoustic Tealeaf target page to collect the images in your application. The tool assigns unique identifiers to the images and collects them in a folder.

You can use the target simulator tool with both the Android SDK and iOS SDK. For more information, see Collect images with the target simulator tool.

Obtain templates for the replay server

Tealeaf has functions to log screen layouts for screenviews of native mobile app sessions. You can use these screen layouts to replay a mobile app session. The screen layouts of the native mobile app sessions are captured in Tealeaf JSON format. The screen layouts are sent to the replay server. The replay server uses a template engine, which interprets the JSON into HTML format. You can then replay the screen layout from the native mobile app session as HTML pages.

You can obtain the base templates used in the template engine from NativeTemplates.

Upload the images and templates to the replay server

You can upload the image and template package files for your organization as .zip files.

1. Log in as the Organization Administrator.
2. Click Admin > Company settings and click Edit.
3. Find the Native replay files section of the screen.
4. Click Image package Upload file.
5. Browse to the file location, select the file to upload, and click Upload. You can upload the file as a .zip file.
6. Click Template package upload file.
7. Browse to the file location, select the file to upload, and click Upload. You can upload the file as a .zip file.
8. Click Save.

Manage replay assets

After you upload the images and templates, you can use the Asset Manager to manage the individual assets.

You can use the asset manager to browse read-only versions of the native image files that you uploaded. You can also use asset manager to download, delete, and upload individual files. For information on how to use the asset manager, see Manage replay assets from asset manager.