# Introduction

The Driver Data component manages the download and display in your mobile application of all trips made by the user.

The Driver Data component continuously performs synchronization between the remote DriveQuant database and the local database of the mobile SDK.

The Driver Data component has been designed to simplify the integration of DriveQuant services into your application and to drastically reduce your development time.

It has several benefits:

* The SDK contains its own database. You do not need to create a local database (or modify the existing one) to persist the user driving data.
* Network calls are fully automated. You do not need to implement API requests for driver data recuperation.
* The SDK includes a graphics library that displays the user's trip data. You do not need to develop new screens in your application. The trip analysis display screens are configurable and can be easily adapted to the style of your mobile application.

{% hint style="info" %}
The Driver Data component uses standard and powerful libraries recommended by Apple and Google for persistence management. On Android, the [Room library](https://developer.android.com/topic/libraries/architecture/room) is implemented. On iOS, the [Core Data](https://developer.apple.com/documentation/coredata) persistence framework provided by Apple is used.
{% endhint %}

{% hint style="info" %}
We recommend you to test this component in the [DriveKit Demo App](/master.md#the-drivekit-demo-app) before you integrate it in your application.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drivequant.com/driver-data/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.