Term | Definition |
Absolute date range | Always remains within the specified start and end dates. |
Active User | Active users are unique individuals who visit your app at least once within the selected period. UXCam defines a unique user based on the Install ID; however, you can also set up your own User ID. |
Alias | Randomly generated alias for a given user, assigned by UXCam. |
API Key | A code of your choice that serves as a password for accessing your app data and has to be provided in the API call. Please note that the API key and App key allow accessing your data on UXCam’s servers, even without access to the dashboard. |
App ID | Unique identifier of your app to be provided as an argument in the API call. |
App quit rate | Percentage of screen visits at which the users quit the app within the selected date range. |
Coded Event | Coded events are user interactions tracked in an application using an event API, providing flexibility for defining and logging a wide range of events. These events are not limited to gestures or screen visits, support custom properties, and are implemented externally to the app. Coded events do not apply retroactively to past sessions, starting tracking from the moment of implementation. |
Crashes | A crash occurs when there's an unexpected exit caused by an unaddressed exception or signal during development. When an unexpected signal occurs, the app will crash and be forced to close. After a crash, users need to re-open the app to continue using it. |
Custom User properties | Customizable user information beyond default details, associated with a user's profile in UXCam. Users can send up to 100 additional properties using the UXCam API. |
Dashboards | Custom dashboards provide a centralized, fully customizable interface for monitoring app KPIs, analyzing user experiences, and gaining actionable insights. |
Device Time | Local time on the user’s device when a session started. |
DPI | Dots per inch for the device |
Event | An event can indicate any user interaction with your app, such as pressing a button, completing a process, seeing an error message, etc. UXCam detects two events by default: rage taps and UI freezes. However, if you want to track other actions from your application, you must send them as Custom Events. |
Event Properties | Each event can have up to 20 properties attached; these properties can provide further information about the events. E.g., count, status, name, category, type, etc. For example, for events "Add to cart", we can send properties such as "product name", "quantity", "price" etc. |
Exception | In the realm of mobile app development, an exception denotes an unforeseen error or irregular event that deviates from the expected flow, potentially causing the app to behave abnormally, crash, or produce unintended outcomes. Specific handling mechanisms are employed to address these exceptions, ensuring the app's stability and safeguarding the user experience. |
First seen | The date in which UXCam has recorded the earliest session for a user. |
Fragments | A modular and reusable component that represents a self-contained portion of a user interface, often used within activities to build flexible and responsive layouts. |
Install ID | UXCam uses a Vendor Device ID to identify unique users (UIDevice.currentDevice.identifierForVendor.UUIDString), which is a random UUID tied to the app publisher. |
kUXCam_UserIdentity | Set by the UXCam.setUserIdentity API. This is a custom user property that you can send to UXCam to identify your users. (Do not send PII). |
Last seen | The date in which UXCam has recorded the latest session for a user. |
MainActivity | In Android app development, MainActivity is a designated Java or Kotlin class that functions as the primary entry point for the application. This class is responsible for setting up and displaying the main user interface, handling user interactions, and coordinating the overall navigation and behavior of the app. It plays a pivotal role in initializing the app's layout and initiating key functionalities when the app is launched. |
New User | New users are unique individuals that visit your app for the first time during the selected period. UXCam defines a unique user based on the Install ID; however, you can also set up your own User ID. |
Rage Quits | Indicates when a user quits the app right after a rage tap. |
Rage Tap or Gesture | A rage tap represents rapid-fire taps in frustration. It's defined by at least 3 taps within a certain radius on the screen and at most 300ms between consecutive taps. It would show you when users are frustrated with a certain element in your app. Please keep in mind that if there's any button in your app that users need to click rapidly (e.g. plus button to increase some kind of quantity), you can always decide not to track rage taps on a specific screen. This can be achieved in App settings. |
Recording Time | Shows when the SDK recorded a session in UTC. |
Relative date range | Dynamically updates to show a period relative to the current date. |
Reverse flow | Invert the screen flow and understand how users navigate through your app before they quit. |
Schematic Recording | By default, UXCam generates a schematic representation on iOS apps to visualize in-app behavior without recording the app’s screen. This technology reconstructs the session by drawing rectangular shapes and texts in a way that reflects the app’s actual screen layout. This only applies to iOS. All Android recordings will show images. |
Screens | Name of the screen/activity automatically recognized in the app or manually assigned via the screen tagging API. |
SDK | An SDK (Software Development Kit) is a comprehensive set of tools, libraries, and documentation facilitating the development of applications by providing essential resources such as code samples, APIs, and utilities. |
Session | A session is everything the user did within your app, from launch until they sent it to the background. It includes all the meta-data collected during the user visit, including device and user data and interactions with your application such as screen visits, events triggered, and gestures. |
Session ID | It’s a unique ID assigned by UXCam to each session. |
Session label | A feature allowing the application of personalized tags to users or sessions for easy identification and subsequent filtering. |
Smart Event | A smart event refers to a predefined mechanism within an application designed to capture specific user interactions, focusing on gestures and screen visits. These events are limited to actions like taps and swipes on UI elements and are created directly within the UXCam platform, providing ease of implementation and management. Smart events typically have core properties such as element ID, element name, and element type, offering detailed information about the UI elements involved. They apply retroactively to past sessions, allowing for analysis of historical data related to these events. |
Top app version | Most often used app version within the last X days |
Top country | The country (according to the IP address) from where the most app sessions originated. |
Top devices | The most frequent size of all devices using your app. |
Top event | Most frequent event per user within the selected timeframe. |
Top events | The most frequently fired event in your app within the selected timeframe. |
Top week day | Day of the week on which your app is visited most often. |
UI Freezes | Indicates when the app is unresponsive or frozen. We detect a UI freeze when you run a process on the UI thread that takes too long and can't process the user input. We track it by adding a piece of code that tries to run on the main thread at regular intervals. If the gap between runs is unexpectedly high, more than one second, we declare a UI Freeze. |
Unresponsive Gesture | Represents a tap or gesture that triggers no response from the application. It could be either an interaction with an element that is not responding (e.g., bug) or the user trying to interact with a static element of the screen (e.g., text). |
Uploading Time | Time when the session is uploaded to the UXCam server, in UTC. |
User label | A feature allowing the application of personalized tags to users or sessions for easy identification and subsequent filtering. |
User name | Provided user name or a randomly assigned alias. |
Video | It is a video representation of the session (Video is a smaller part of the session and represents its recording) that shows the exact reproduction of what the users did with the application. How they interacted, how the screens were displayed, what messages or errors they had, etc. |
View Controller | In software development, specifically within the context of mobile app development, a view controller is a crucial architectural component responsible for managing and coordinating the user interface of an application. It governs the presentation of visual elements on the screen, facilitates user interactions, and often encapsulates the logic related to a specific screen or view in the app. Example: In an iOS mobile app, a view controller could be a "LoginViewController" responsible for handling the user interface and interactions related to the login screen. It manages the display of login fields, buttons, and handles user input, orchestrating the logic for authenticating users and transitioning to subsequent views upon successful login. |