Skip to main content

React Native & Expo SDK

Integrate telematics in React Native and Expo apps through a single JavaScript API.​

📄 Integration Guide

How to add the SDK and configure the project.

📄 Permissions Setup

Mandatory permissions and how to declare them.

📄 Permissions Runtime Behavior

How permissions behave at runtime and how to handle them.

📄 Usage Examples

Code examples for common flows.

Overview​

The TelematicsSDK for React Native and Expo provides access to the native telematics capabilities of iOS and Android through a single, unified JavaScript API.

It is available as a React Native module (@driviantelematics/telematics-sdk-rn) and as an Expo module (@driviantelematics/telematics-sdk-expo), which expose the same API. Both integrate the native TelematicsSDK for iOS and Android and expose their functionality to React Native via a platform bridge, allowing applications to share the same business logic across platforms.

All telemetry logic, permission handling, and background execution behavior are implemented natively. The React Native layer acts strictly as a forwarding interface and does not reimplement native behavior.

This section provides an overview of the React Native & Expo SDK and points you to the relevant guides for integration, permissions setup, and common usage patterns.

How to use this documentation​

Use the sections below to navigate the React Native & Expo SDK documentation:

  • Integration Guide: Learn how to install the React Native or Expo module and configure native dependencies.
  • Permissions Setup: Understand which permissions are required on each platform and how they must be declared in the native projects.
  • Permissions Runtime Behavior: Learn how the native SDKs evaluates permissions at runtime and how it reacts to permission changes, interruptions, and telemetry gaps while the app is running.
  • Usage Examples: Explore common flows such as SDK initialization, authentication, vehicle management, telemetry control, and event handling.

Each section builds on the native SDK behavior and should be read with the understanding that platform-specific rules still apply.