User interface
Last updated
Was this helpful?
Last updated
Was this helpful?
Driver Data component includes an open source graphics library which provides a set of screens to display trip data recorded by the Trip Analysis component and analyzed by DriveQuant services.
The Driver Data component displays the list of trips made by the driver as well as the details of each trip displayed on a map with all driving indicators and driver scores.
Driver Data component gives a direct access to the formatted data on simple and readable screens. This way, you do not need to create specific screens in your application for illustrating driver’s trip analytics.
All the screens that display the trip results are fully customizable. You can configure the information you want to highlight and integrate styling elements from your application such as colors and fonts. The configuration options are detailed later in this section.
The use of this graphic library is not mandatory and you can develop your own screens if their actual style doesn't fit with your mobile application. In this case, the graphics library can be used as an example to design your own visualizations.
The Driver data component includes 2 cards that simplifies the display of driver behaviour scores synthesis:
The driver synthesis scorecard → shows the averages of each of the driving scores calculated over a 7 days since the last trip date.
The last trip widget → displays a short chronological list of the driver's last trips.
Driver Data Component provides a screen, “My synthesis”, where a driver can compare his average performances per week, month or year with reference levels and also with other drivers in the same community.
Each driver has a profile that corresponds to his habits. The driver's profile is determined from a statistical and historical analysis of his driving data:
how frequently the driver uses his car,
his regularity,
the most travelled road context,
the annual distance covered,
and his mobility area.
These information can be displayed to the driver thanks to the Driver Data graphical component of the DriveKit SDK.
You can find more details on the and documentation.
