All Collections
Using Ballpark
Gathering responses
Prototype replay without screen recording
Prototype replay without screen recording

View prototype playback for sessions with mobile devices and when there is no screen recording enabled

Updated over a week ago

Prototype replay uses the events captured on your Figma prototypes to simulate where users tapped and the screens they visited.

We have created this feature because screen recording is not currently supported by mobile browsers. It is also available for desktop responses when screen recording is not enabled.

Combined with the webcam recording, prototype replay lets you see a user's reactions and listen to their observations as they go through the prototype.

To access replays of responses taken without screen recording, click the 'Prototype Recording' button located below free roam or prototype tasks on the response page:

Mobile_prototype_replay.gif

Limitations of prototype replay

Scroll simulation

Ballpark simulates how users may have scrolled based on the tap and click data available from Figma. This is because scroll events are not currently shared by Figma.

When we detect a tap or click that was made below the regular screen height, we'll simulate a scroll to that position shortly before the tap.

Component and layer support

At present we cannot show any interactions or transitions on interactive components or overlay components within Replay. This is due to a limitation on the data that we import and support from Figma. We are currently working on adding this support in the future.

Any taps and clicks made on interactive or overlay components will be shown on the base screen where that component appeared. This is so you can tell if a click occurred somewhere relative to that screen.

Screen size for desktop replays

All prototype replays that were made on desktop devices will be displayed in the common 1440x1024 resolution. This means that some responses may not exactly reflect the size of the participant's window.

This is due to desktop browser window sizes being harder to predict compared to mobile screen sizes, which are highly standardised.

⚠️ Important: Once your project receives responses, changes to your prototype can cause inaccurate prototype statistics. In particular, these changes impact paths, heatmaps, and prototype replays.

Did this answer your question?