Follow the user's path through your app

Record Android route names so replays, timelines, and agents can place logs and touches in the context of the screen the user visited.

Named screen visits make a session easier to reconstruct. Add screen-view events from your app’s navigation flow so you can follow the route to an issue alongside logs, gestures, and screenshots.

Manual Screen Views

AnsightRuntime.screenViewed(
    "Orders",
    mapOf("route" to "/orders")
)

Use stable names and compact details such as route, tab, or presentation.

The Android SDK exposes screenViewed(...) as the supported app-code API. Call it from your navigation observer, route callback, or screen lifecycle hook when the current route changes.

fun onRouteChanged(route: String) {
    AnsightRuntime.screenViewed(route, mapOf("source" to "app-navigation"))
}