This section discusses how is the user navigation in the application recorded
Understanding the way user uses the application is the purpose of the analytics. A typical mobile application breaks into several screens, between them users navigates to achieve their goals.
Smartlook attempts to track the transitions automaticallt and record them as navigation events, that are then available in the Dashboard. Another usage of navigation events is generating heatmpas.
To generate a meaningfull heatmap, a portion of the application UI with stable structure must be used. Smartlook assumes that a screen, i.e., interval between two subsequent navigation events is such a UI unit.
Properly dividing the user flow into individual screens important for correct heatmap generation, as each heatmap is generated for a particular screen, i.e., interval between two navigation events.
However, the accuracy and usefulness of these auto-tracked navigation events depends heavily on the way the application UI is composed. Smartlook understands well apps that use standard UI kits a paradigms for each platform. If the application is, however, made using a 3rd party frameworks, e.g., a gaming framework, that Smartlook SDK cannot detect the navigation logic of the application. Details abount the extent auto-detection of navigation events on each particular platform are provided in the API Reference.
In such a case, in orded to get useful navigation data, navigation events must be tracked programatically, using this method:
The navigation event recorded by this method is indistinguishable from the auto-detected navigation events.
where the type value is either of
exit kind. The
exit event also records the duration from the previous corresponding enter event.
More details about the navigation events, consult the API reference.