You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike the web, mobile SDKs create and send videos, rather than a series of events that can be reconstructed into a replay. The replayer for mobile replays attempts to stitch together these videos to play in a single, combined timeline. Due to the nature of mobile applications, there can be be gaps between each video segment. The user, for example, can switch to another app, causing this gap in a replay session. This adds a bit of complexity to try to handle it seamlessly and will likely (and already has) be a source of bugs. We can improve the UX by informing the user of these periods of inactivity and at the same time reduce complexity and bugs.
Acceptance Criteria
If a user changes the current time index of the replay to be within the gaps duration, the current time index will skip to start of the next segment.
The user can see a visual indicator that informs them why the current time index of the replay is "jumping"
The text was updated successfully, but these errors were encountered:
billyvg
changed the title
Design: Gaps between segments in mobile replays is causing tonnes of bugs
Design: Show inactivity gaps between segments in mobile replays
May 7, 2024
Problem
Unlike the web, mobile SDKs create and send videos, rather than a series of events that can be reconstructed into a replay. The replayer for mobile replays attempts to stitch together these videos to play in a single, combined timeline. Due to the nature of mobile applications, there can be be gaps between each video segment. The user, for example, can switch to another app, causing this gap in a replay session. This adds a bit of complexity to try to handle it seamlessly and will likely (and already has) be a source of bugs. We can improve the UX by informing the user of these periods of inactivity and at the same time reduce complexity and bugs.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: