Get Started
Before starting DriveKit Driver Achievement integration, make sure that you have initialized DriveKit, especially if you have disable the SDK auto-initialization.
If you use DriveKit Driver Achievement without having initialized DriveKit, an exception will be generated and the SDK will not work in your application.
Integration
Get module from repository.
To add the Driver Achievement module to your app, add the following line to your dependencies in your application build.gradle
file:
Replace $drivekit_version
with the DriveKit version you are using in your app
Initialization
If you have disabled the SDK auto-initialization, an initialization phase is required to use the functions offered by the Driver Achievement component. To initialize Driver Achievement component in your app, you must call the initialization method in onCreate
method of your application class.
Get Streaks
To get Driver streaks, you have to call the following method:
SynchronizationType
can have 2 values:
DEFAULT
: if this value is used, the SDK will try to synchronize local trips with DriveQuant backend to get new trips or modified trips, and then return the trip list via the callback.CACHE
: If this value is used, no synchronization will be performed and only trips previously synchronized will be returned via the callback.
StreakSyncStatus
in the callback can have 3 values:
NO_ERROR
: synchronization has been successfully performed.CACHE_DATA_ONLY
: synchronizationType has been set to cache.FAILD_TO_SYNC_STREAKS_CACHE_ONLY
: synchronization has failed, only streaks previously synchronized are returned.
Streak description
Attribute | Type | Description |
| StreakTheme | Streak Theme identifier |
| StreakResult | Current streak result |
| StreakResult | Best streak result |
Streak themes description
The themes and conditions to increment the sequences of the trip are the following:
PHONE_DISTRACTION
: the driver has not handled his phone.SAFETY
: the safety score of the trip is higher or equal to 9.8.SPEEDING
: the speeding score of the trip is higher or equal to 9.8.ACCELERATION
: there wasn’t any harsh acceleration event during the trip.BRAKE
: there wasn’t any hard braking event during the trip.ADHERENCE
: there wasn’t any adherence thresold crossing during the trip.CALL
: the driver has not made forbidden call during the trip.
Streak Result description
Attribute | Type | Description |
| Double | Total distance travelled during streak |
| Double | Total duration travelled during streak |
| Int | Number of trips performed within streak |
| Date | Date of the first trip of the streak |
| Date | Date of the last trip of the streak |
Get Badges
To get Driver badges, you have to call the following method:
BadgeSyncStatus
in the callback can have 3 values:
NO_ERROR
: Synchronization has been successfully performedCACHE_DATA_ONLY
: SynchronizationType has been set to cache.FAILED_TO_SYNC_BADGES_CACHE_ONLY
: Synchronization has failed, only badges previously synchronized are returned.
If you want to notify users when they acquired a new set of badge you can get this value from the callback.
Get badge statistics
It can be practical to get some badge statistics, like how many badges have been won and how many remain to be acquired. To get these information, call the following method:
DKBadgeStatistics
Field | Type | Description |
---|---|---|
acquired | Int | Total badge acquired by the user |
remaining | Int | The number of badges not yet obtained |
total | Int | Total badge count |
Badge Description
Badge
Attribute | Type | Description |
| String | Badge theme identifier |
| BadgeCategory | Badge category |
| List<BadgeCharacteristics> | Badge properties |
BadgeCharacteristics
Attribute | Type | Description |
| Level | Badge level |
| String | Badge name |
| String | Badge icon name (for a won badge) |
| String | Badge default icon name (for a pending badge) |
| String | Clé localisable correspondant à la description pour l’affichage dans l'application. |
| String | Badge progress message |
| Double | Distance or number of trips performed |
| String | Badge congratulations message |
| Int | Distance or number of trips required to win the badge |
Level
The Level
enum values are:
BRONZE
SILVER
GOLD
BadgeCategory
The BadgeCategory enum values are:
GENERIC
SAFETY
ECO_DRIVING
PHONE_DISTRACTION
Get ranking
To get driver’s ranking, you need to call the following method:
Ranking parameters
Attribute | Type | Description |
| RankingPeriod | Period of the ranking |
| int | Number of participants in the ranking higher and lower than the current user. It could be between 5 and 20. |
| RankingType | Is the theme of the leaderboard. |
| SynchronizationType | Whether data are fetch locally or from server. |
RankingPeriod
The RankingPeriod enum values are:
WEEKLY
: is the period from the last Monday at midnight to the next Sunday at midnight.MONTHLY
: is the period from the 1rst day of the month (at midnight) to the last (at midnight).ALL_TIME
: is the period since the creation of the app.
RankingType
The RankingType enum values are:
SAFETY,
DISTRACTION,
ECO-DRIVING,
SPEEDING.
RankingSyncStatus
RankingSyncStatus
in the callback can have 3 values:
NO_ERROR
: Synchronization has been successfully performed.CACHE_DATA_ONLY
: SynchronizationType has been set to cache.FAILED_TO_SYNC_RANKINGS_CACHE_ONLY
: Synchronization has failed, only rankings previously synchronized are returned.USER_NOT_RANKED
: Driver not ranked.
Ranking Description
Attribute | Type | Description |
| String | Theme of the ranking |
| String | Period of the ranking |
| String | Ranking group name |
| Int | Position of the driver in the DriverRanked list |
| Int | Previous driver’s rank |
| List<DriverRanked> | List of the rated drivers |
| Int | Total number of rated drivers |
DriverRanked Description
Attribute | Type | Description |
| String | Unique identifier of the driver |
| String | Driver’s nickname |
| Int | Driver’s rank in the leaderboard. This value is determined from the score rounded to 2 decimal places. If there is a tie, the one who has travelled the most distance is first. |
| Double | Driver’s score (according to the theme). This is the average of scores of the trips made in the period under consideration. |
| Double | Covered distance by the driver in the specified period in km. |
Ranking access conditions
To enter a ranking, a driver must fulfill the following requirements:
Weekly ranking: 2 trips and 10 km since the first day of the week;
Monthly ranking: 5 trips and 20 km since the first day of the month;
Permanent ranking: 10 trips and 50 km since his first trip.
Data update
The scores, distances and ranks are updated every hour.
Last updated