@react-native-drivekit/trip-analysis

React Native interface for DriveKit Trip Analysis

Prerequisite

Before installing @react-native-drivekit/trip-analysis you must have installed @react-native-drivekit/core, especially if you have disabled the DriveKit auto-initialization.

Installation

Install the library:

npm install @react-native-drivekit/trip-analysis

Install iOS pods:

cd ios && pod install

Initialization

Android setup

If you have disabled the DriveKit auto-initialization, call initialize method in the onCreate() method of your Application class.

// MainApplication.java
import com.reactnativedrivekitcore.DriveKitCoreModule;
import com.reactnativedrivekittripanalysis.DriveKitTripAnalysisModule;

// ...
  @Override
  public void onCreate() {
    super.onCreate();
    DriveKitCoreModule.Companion.initialize(this);

    // ADD THESE LINES
    final RNTripNotification tripNotification = new RNTripNotification("Notification title", "Notification description", R.drawable.common_google_signin_btn_icon_dark)
    final RNHeadlessJSNotification headlessJSNotification = new RNHeadlessJSNotification("Notification title", "Notification description");
    DriveKitTripAnalysisModule.Companion.initialize(tripNotification, headlessJSNotification);
    ...
  }

ℹ️

The properties in RNTripNotification are used to configure the notification displayed when a trip is recording.

The properties in RNHeadlessJSNotification are used to configure the notification when the HeadlessJS service is running

If the DriveKit auto-initialization is enabled, you have to

• configure the trip notification content displayed during a trip analysis by calling the following method:

final RNTripNotification tripNotification = new RNTripNotification("Notification title", "Notification description", R.drawable.common_google_signin_btn_icon_dark)
DriveKitTripAnalysisModule.Companion.configureTripNotification(tripNotification);

• configure the HeadlessJS notification content by calling the following method:

final RNHeadlessJSNotification headlessJSNotification = new RNHeadlessJSNotification("Notification title", "Notification description");
DriveKitTripAnalysisModule.Companion.configureHeadlessJSNotification(headlessJSNotification);

Authorization

In order to collect data, you need to configure multiple permissions :

• Location permission: native documentation
• Activity recogniton permission: native documentation
• Nearby device permission: native documentation
• Notification runtime permission: native documentation

Our recommandation is to use react-native-permissions. You can find an implementation example in the demo application inside this repository.

Battery optimization

In order to make Trip Analysis SDK to work properly, you need to disable battery optimization for your app: native documentation

Our recommandation is to use react-native-battery-optimization-check.You can find an implementation example in the demo application inside this repository.

IMPORTANT

This library is not actively maintained. The problem is that the method that call the native modal is not promisified. It means that we can't wait for the user answer before continuing. At the moment, our recommandation is to check this permission at the end of your flow. On our side, we are working on implementing a better solution.

This is the better solution we found. If you find a better solution, please feel free to open an issue/PR in this repository.

iOS setup

If you have disabled the DriveKit auto-initialization,, call initialize method in your AppDelegate.mm.

// AppDelegate.mm
#import <RNDriveKitTripAnalysis/react-native-drivekit-trip-analysis-umbrella.h>

// ...

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  [[RNDriveKitCoreWrapper.shared initialize];
  [RNDriveKitTripAnalysisWrapper.shared initializeWithLaunchOptions:launchOptions]; // ADD THIS LINE
  ...
}

Note: If you are using Swift, initialize method is also available.

Configure capabilities

You need to turn on Background Modes & enable Location updates. For more details please follow the iOS documentation

Authorization

In order to collect data, you need to configure multiple permissions :

• Location permission : native documentation
• Motion permission : native documentation

Our recommandation is to use react-native-permissions. You can find an implementation example in the demo application inside this repository. For location permission, please use requestIOSLocationPermission() method for iOS.

When the application requests permission for background locations or motion activities, a message will be shown to the user. You must configure this message by changing the value for the following keys in Info.plist

• NSLocationWhenInUseUsageDescription
• NSLocationAlwaysAndWhenInUseUsageDescription
• NSMotionUsageDescription

Our Demo App plist file contains an example of messages you can use for these permissions

Validation

To validate that the initialization has been done successfully, please check your native logs and verify that you can see the following success message.

Android

iOS

Listeners

Note: These listeners will not be triggered on Android when the app is in background, due to system limitation. Please read the Headless JS part.

You can listen to events thanks to the addEventListener api.

useEffect(() => {
  const listener = DriveKitTripAnalysis.addEventListener(
    'tripStarted',
    (startMode: StartMode) => {
      console.log('trip start', startMode);
    }
  );
  return () => listener.remove();
});

Here is the list of supported events:

• tripPoint, callback (tripPoint: TripPoint) => void: This event is triggered when a trip is started and confirmed, for each GPS point recorded by the SDK.
• tripStarted, callback (startMode: StartMode) => void: This event is triggered each time a trip is started. StartMode indicates which event starts the trip.
• tripCancelled, callback (cancelTrip: CancelTrip) => void: This event is triggered when a trip is cancelled. CancelTrip indicates which event cancels the trip.
• tripFinished, callback (post: PostGeneric, response: PostGenericResponse): This event is triggered when a trip has been recorded by the SDK and sent to DriveQuant's server to be analyzed. PostGeneric object contains raw data sent to DriveQuant's server, PostGenericResponse object contains the trip analysis made on DriveQuant's server.
• tripSavedForRepost, callback () => void: This event is triggered if at the end of the trip, the trip can be sent to DriveQuant's server for the analysis. The trip is saved locally on the SDK and will be sent later.
• beaconDetected, callback () => void: This event is triggered when a beacon sets in the SDK is detected.
• significantLocationChangeDetected, callback () => void: This event is triggered when a user significant location change is detected. (only for iOS)
• sdkStateChanged, callback (state: State) => void: This event is triggered every time the state of the SDK changed with the new state as parameter.
• crashDetected, callback (info: CrashInfo) => void: This event is triggered when crash detection feature is enabled and available for your team and when a crash has been detected.
• crashFeedbackSent, callback (crashFeedback: CrashFeedback) => void: Event triggered when crash feedback is enabled and a confirmed crash is detected. This callback will contain crash information and the feedback from the user.

Headless JS (Android only)

To display a notification when the trip is finished or cancelled for example, it is not possible to handle listeners like the iOS platform, because listeners are not triggered when the device is locked or the app is not in foreground. To manage that limitation, a Headless JS service has been introduced on Trip Analysis component.

Follow these steps :

• Register the Headless task named DKHeadlessJS on your index.js file.
• Replicate the DKHeadlessJS.js file that exists on the demo package.

API

| Method | Return Type | iOS | Android | | --------------------------------------------------------------------- | ------------------------------- | :-: | :-----: | | activateAutoStart() | Promise<void> | ✅ | ✅ | | startTrip() | Promise<void> | ✅ | ✅ | | stopTrip() | Promise<void> | ✅ | ✅ | | cancelTrip() | Promise<void> | ✅ | ✅ | | isTripRunning() | Promise<boolean> | ✅ | ✅ | | activateCrashDetection() | Promise<void> | ✅ | ✅ | | enableMonitorPotentialTripStart() | Promise<void> | ✅ | ✅ | | setStopTimeout() | Promise<void> | ✅ | ✅ | | getTripMetadata() | Promise<TripMetadata \| null> | ✅ | ✅ | | setTripMetadata(metadata: TripMetadata) | Promise<void> | ✅ | ✅ | | deleteTripMetadata(string?: string) | Promise<void> | ✅ | ✅ | | updateTripMetadata(key: string, value: string) | Promise<void> | ✅ | ✅ | | setVehicle() | Promise<void> | ✅ | ✅ |

activateAutoStart

activateAutoStart(enable: boolean): Promise<void>

The automatic mode detects vehicle movements and triggers the trip analysis without driver intervention while the application is in background. The analysis is stopped automatically at the end of the trip.

This feature is recommended to avoid driver distraction and phone handling while driving. The automatic mode has been optimized to limit the battery drain.

To enable automatic trip detection mode, call the following method:

activateAutoStart(true);

To disable automatic trip detection call the same method with parameter enable set to false

activateAutoStart(false);

⚠️

If a trip is running when automatic trip detection is disabled, the trip will not be cancelled. If you want to cancel the trip, you should also call cancelTrip method.

startTrip

startTrip(): Promise<void>

You can start a trip by calling the following method:

startTrip();

ℹ️

If a trip's already started, calling this method will have no effect.

stopTrip

stopTrip(): Promise<void>

You can stop a trip by calling the following method. The trip will be stopped instantly:

stopTrip();

ℹ️

If a vehicle stops longer than the timeout configured, the trip will be stopped automatically.

ℹ️

If there is no running trip, calling this method will have no effect.

cancelTrip

cancelTrip(): Promise<void>

If you want to cancel a trip, you can call this method:

cancelTrip();

isTripRunning

isTripRunning(): Promise<boolean>

This method returns false if the SDK is in INACTIVE state, and no trip is currently running.

const isTripRunning = await isTripRunning();

activateCrashDetection

activateCrashDetection(enable: boolean): Promise<void>

Crash detection features, included into the DriveKit Trip Analysis component, is able to collect and analyse smartphone sensors data to automatically detect when a car accident occurs.

Learn more about the feature on iOS / on Android

An input parameter is available in DriveKitTripAnalysis to enable or disable the feature:

activateCrashDetection(true);

To disable crash detection, call the same method with parameter to false

activateCrashDetection(false);

ℹ️

If no trip is running or if the trip has been sent to the server and is currently being analyzed, calling this method will have no effect.

enableMonitorPotentialTripStart

enableMonitorPotentialTripStart(enable: boolean): Promise<void>

To listen to trigger events that indicate a start of trip, even if the autostart is disabled, you can call the following method:

enableMonitorPotentialTripStart(true);

setStopTimeout(stopTimeout: number): Promise<void>

A trip being analyzed is automatically stopped after a period of inactivity (which begins when the vehicle has stopped).

The DriveQuant SDK allows to set the end-of-trip duration. Default value is 240s.

setStopTimeout(240);

⚠️

If a value greater than 480 is set, the value will be forced to 480.

If a value lower than 120 is set, the value will be forced to 120.

getTripMetadata

getTripMetadata(): Promise<TripMetadata | null>

If you want to get the metadata of your trip, you can call the following method:

await getTripMetadata();

setTripMetadata

setTripMetadata(metadata: TripMetadta): Promise<void>

If you want to set the metadata of your trip, you can call the following method:

await setTripMedata({ key: 'value' });

deleteTripMetadata

deleteTripMedata(key?: string): Promise<void>

If you want to a specific metadata, you can call the following method:

await deleteTripMedata('key');

If you want to delete all keys call it without parameter:

await deleteTripMedata();

updateTripMetadata

updateTripMetadata(key: string, value: string): Promise<void>;

If you want to update a specific metadata key, you can call the following method:

await updateTripMetadata('key', 'value');

setVehicle

setVehicle(vehicle: Partial<TripVehicle> | null): Promise<void>

To obtain a more precise analysis on driving behaviour, it's recommended to configure the vehicle used by the driver. You can do this by calling the following method:

await setVehicle({
  carTypeIndex: 1,
  carEngineIndex: 1,
  carPower: 150,
  carMass: 1400,
  carGearboxIndex: 2,
  carConsumption: 4.5,
  carAutoGearboxNumber: 6,
  engineDisplacement: 1200,
  frontTireSize: '205/55/16',
  rearTireSize: '205/55/16',
  length: 4.5,
  width: 1.8,
  height: 1.45,
  engineCylinderNb: 4,
  driveWheels: 0,
});

A detailed description of vehicle parameter is available here.

ℹ️

If no vehicle is configured a default vehicle will be configured with following parameters:

carTypeIndex = 1

carEngineIndex = 1

carPower = 150

carMass = 1400

carGearboxIndex = 2

carConsumption = 4.5

engineDisplacement = 1200

frontTireSize = "205/55/16"

rearTireSize = "205/55/16"

length = 4.5

width = 1.8

height = 1.45

engineCylinderNb = 4

driveWheels = 0