See the gestures behind app behavior

Replay Android touches and stylus or eraser strokes, pressure, tilt, and hover beside screenshots and telemetry.

Touch evidence helps you understand what the user did before the app changed or a problem appeared. The Android runtime captures app-local input when touchCapture is configured and the runtime is active.

Configure

val options = AnsightOptions.createBuilder()
    .withTouchCapture(
        moveCaptureDistanceThreshold = 8.0,
        moveCaptureFramesPerSecond = 20,
    )
    .build()

Disable it:

val options = AnsightOptions.createBuilder()
    .withoutTouchCapture()
    .build()

Runtime Toggle

AnsightRuntime.enableTouchCapture()
AnsightRuntime.disableTouchCapture()

Guard Capture

Android exposes a runtime touch guard:

Ansight.setTouchCaptureGuard {
    sessionManager.isDebugSessionAllowed
}

The guard is evaluated before captured touch records are accepted.

Touch records include action, pointer data, surface coordinates, normalized coordinates when available, and capture time. Keep touch capture scoped to approved local development or QA workflows.

Stylus and eraser records add available pressure, tilt, orientation, hover distance, button state, and contact or tool dimensions. The runtime also retains historical samples from batched move events and captures stylus hover enter, move, and exit. Reported fields depend on the pen and digitizer; absent sensor values are not estimated.