Welcome
Configuration
Configuring HCL Discover involves setting up and managing Discover user authorization and configuring Discover server components and services that process captured data.
HCL Discover Native Mobile SDK Manual
Discover Android SDK
Discover monitors the traffic between your application and server. It captures device context and user activity so that you can monitor and evaluate the performance of your applications.
Technical Integration
The Discover Android SDK provides a comprehensive instrumentation framework for native Android applications, enabling the capture of:
Key Notes and Best Practices

Product Overview
Customer Experience is now the number one differentiator in decision making when transacting online. It is crucial that you are able to monitor, understand and manage those online experiences using quantitative data and insights from your actual customer sessions.
Release Notes
Installation, Deployment, and Upgrade
Installing HCL Discover involves planning and preparing your environment, installing and configuring prerequisite software, obtaining the HCL Discover installation files, and running the HCL Discover installer.
Configuration
Configuring HCL Discover involves setting up and managing Discover user authorization and configuring Discover server components and services that process captured data.
- HCL Discover Configuration Manual
- HCL Discover Event Manager Manual
- HCL Discover UI SDK Manual
- HCL Discover Native Mobile SDK Manual
  - Discover Android SDK
    Discover monitors the traffic between your application and server. It captures device context and user activity so that you can monitor and evaluate the performance of your applications.
    - Technical Integration
      The Discover Android SDK provides a comprehensive instrumentation framework for native Android applications, enabling the capture of:
      - Installing SDK
      - Android Permissions
        The Discover Android SDK requires the following permissions to support network communication, connectivity awareness, and device-level context required for event capture and data transmission.
      - Application-level Initialization
      - Manual Touch Event Instrumentation
      - Screen (Activity) Recording
      - Data Upload Configuration
        To enable transmission of captured events and session data from the application to the backend, the Discover SDK must be configured with a valid data ingestion endpoint.
      - Screenshot Capture Configuration
        Screenshot capture behavior in the Discover Android SDK is controlled through the DiscoverLayoutConfig.json configuration file. This allows centralized management of screenshot enablement and masking behavior without requiring code changes.
      - Auto Instrumentation (Type 4)
      - Key Notes and Best Practices
  - Discover iOS SDK
    Discover iOS SDK has two parts:
  - Configurations for Android
  - Configurations for iOS
  - Discover React Native SDK
  - Implementing Discover in Flutter
    To implement HCL Discover in Flutter, complete the following steps:
  - Discover Flutter Plugin
    Discover Flutter plugin serves as a bridge between Dart code and native platform code (iOS and Android).
Administration
Administering HCL Discover involves configuring and integrating the HCL Discover client framework with your web applications or mobile native applications, installing and administering the databases used by HCL Discover, defining event objects and configuring events, hit attributes, dimensions, and other object attributes used by HCL Discover to monitor mission-critical metrics of your web application's performance.
Cloud-native HCL Discover
Notices

Key Notes and Best Practices

Register TrackerInitializer only once in the Application class to avoid duplicate lifecycle callbacks and unintended event capture.
Type 4 auto-instrumentation is fully configuration-driven, allowing behavior changes through configuration files without modifying application code.
Safe to enable or disable across builds without requiring recompilation or redeployment of the application binary.
Always validate configuration changes in a non-production environment before rollout.