This Telematics App is developed by Damoov and is distributed free of charge. This app can be used to create your own telematics app for iOS in few steps.
Telematics:
- Telematics SDK — mobile telematics engine
- Setup Firebase© project
- Telematics SDK Setup
- LoginAuthFramework Authentication
- Dashboard
- Feed
- Trip Details
- Leaderboard
- My Rewards
- Profile & Settings
- Connect OBD device
- Join a Company
- Advanced Settings & Links
Create an account https://app.damoov.com and get InstanceId andInstanceKey auth keys to work with the telematics SDK & APIs.
How to obtain InsanceId & InstanceKey => https://docs.telematicssdk.com/docs/datahub#user-group-credentials
Additionally, to authenticate users in your app and store users data, you need to create a firebase account: https://firebase.google.com All user data will be stored in the Firebase© Realtime Database, which will allow you to create an app users database without programming skills.
In the next few simple steps, we'll show you how easy it is to create and configure an app in the Firebase© console.
Step 1: After creating your Firebase© account, open your console: https://console.firebase.google.com
Click "Create a project" button.
Step 2: Enter the name of your future Project. Click "Continue" button.
Step 3: For ease of integration, at the next step, we recommend deactivating the "Enable Google Analytics" checkbox.
Click "Create project".
Step 4: Now you need to create a configuration for your iOS app. Click on the "iOS icon" as it us shown on the picture below:
Step 5: Enter your unique iOS Bundle ID. This identifier must be used in your application in xCode. Enter App Nickname. Click "Register app" next.
Step 6: On this step, download the provided GoogleService-Info.plist file. You need to put it in our Telematics App source code, as it is shown on the picture below:
Step 7: You can skip the "Add Firebase SDK" & "Add initialization code" steps below, because we already did it for you in our Telematics App:) Finish the setup and click on "Continue to console".
Step 8: Important. In order for your users to create accounts to log into your app, you need to go to "Authentication" section on the left side of the menu.
Step 9: In the "Sign-in method" tab, click on the Provider's "Email/Password" on the right "pencil" (Edit configuration hint) as in the picture below. If you need to perform authorization using the "Phone" Provider - select the setting of this item.
In order for phone auth to work in your xCode project, you need to register Firebase URL Schemes in the Info section of your application.
Step 10: Switch to "Enable" and click "Save" button. Now your users can login to the app.
Step 11: We need to activate Firebase© Realtime Database. This will allow you to store the data of all your users in this simple web interface. Go to the Realtime Database section on the left side of the menu and click on the "Create Database" button.
Step 12: Choose any Realtime Database location value.
Step 13: Select "Start a locked mode" and click the "Enable" button.
Step 14: Now you need to change rules for your Realtime Database. You need to go to “Realtime Database” section on the left side of the menu. In the “Rules” tab change read and write fields to ".read": "auth.uid != null" & ".write": "auth.uid != null".
{ "rules": { ".read": "auth.uid != null", ".write": "auth.uid != null" } }
Important! After creating a user, his data will be entered into the database with the following field names. The structure is identical for iOS and Android and cannot be changed to sync user data across mobile platforms.
Step 15: Open our TelematicsApp.xcworkspace in xCode, make sure to transfer the GoogleService-Info.plist file to your project (See Step 5 above), instanceId & instanceKey in Configurator.plist and Enjoy!
Build & Run!
For your convenience, we have created a standard iOS file with parameters named Configuration.plist, where you can specify the basic settings for your future app.
Using this file, you can configure the basic parameters of your application by specifying server addresses, basic settings and links, as well as specifying several images for an individual design. Carefully study the parameters provided below for further work.
| Settings Key | Value |
|---|---|
| configName | Default Your app configuration name. Not need to change, you can use any of your choice. By default TelematicsApp_Configuration |
| instanceId | Unique ID code for the application to work. Required! |
| instanceKey | Unique KEY code for the application to work. Required! |
| indicatorsServiceURL | Basic https address to work with Indicators APIs. By default, we provide you https-address of our TEST servers for debugging. Before the release your app, you can get the addresses to enter PRODUCTION environment |
| driveCoinsServiceURL | Basic https address to work with DriveCoins API. |
| leaderboardServiceRootURL | Basic https address to work with the user leaderboard and Leaderboard API. |
| carServiceURL | Basic https address to work with CarService API. |
| sdkEnableHighFrequency | BOOL parameter, that activates High Frequency data in Telematics SDK. By defaults true |
| sdkEnableELM | BOOL parameter, that activates connection to ELM OBD Bluetooth devices in Telematics SDK. By defaults true |
| linkPrivacyPolicy | Link for Privacy Policy |
| linkTermsOfUse | Link for Terms Of Use |
| linkHowItWorks | Link for How It Works |
| telematicsSettingsOS12 | Link for Telematics Settings before iOS13 |
| telematicsSettingsOS13 | Link for Telematics Settings for iOS13/iOS14 |
| linkSupportEmail | Link for support email address |
| appStoreAppId | Your unique APPID for the AppStore |
| mainLogoColor | App logo in colors style for display in app. Specifies the file name, you need to use. |
| mainLogoClear | App logo is transparent style for display in the app. Specifies the file name, you need to use. |
| mainBackgroundImg | String name of the Asset image used in the Feed or Profile screen |
| additionalBackgroundImg | String name of the Asset image used in the Dashboard screen |
| mainTabBarNumber | TabBar number, which will open first when the application starts. By default 0 |
| dashboardTabBarNumber | TabBar number, where Dashboard will open. By default 0 |
| feedTabBarNumber | TabBar number, defining what the Feed screen will be in turn in the application. By default 1 |
| profileTabBarNumber | TabBar number, defining what the Profile screen will be in turn in the application. By default 2 |
| needUserDriveDistanceForScoringKm | The minimum distance required to display Indicators statistics and user scores. By default 10 km |
| needTripsDeleting | BOOL parameter, determining if user can delete their trips |
| needDistanceInMiles | BOOL parameter, determining use the default distance traveled in the entire application in km/miles |
| needAmPmTime | BOOL parameter, determining use AM/PM time format in the entire application |
| needEventsReviewButton | BOOL parameter, allowing to mark events on the map |
In the next few simple steps, we'll show you how easy it is to create access keys in the Google Cloud Console.
Step 1: After sign in your Google account open https://console.cloud.google.com/
Step 2: Create new project in Google Cloud Console: https://console.cloud.google.com/projectcreate
Step 3: Set billing for this project: https://console.cloud.google.com/projectselector/billing
Note: use of maps is free
Step 4: Enable MapsSDK for iOS
Step 5: Go to the Google Maps Platform → Credentials page → Create credentials → API key.
More info here: https://developers.google.com/maps/documentation/ios-sdk
We use CocoaPods dependency libraries.
The Telematics SDK is installed by default in the Telematics app using the pod 'RaxelPulse' command in the application Podfile.
For your convenience, enable fast access to macOS PathBar (screenshot), copy the path to the application folder (right click), enter the command 'cd (ctrl + v paste path address see screenshot)' -> Enter in the terminal.
Next you need enter the command pod install in the macOS Terminal. This will install the required dependency libraries for the app to work correctly.
Run Your new application by opening the TelematicsApp.xcworkspace file in the source code folder after.
Below we present the basic methods for AppDelegate that allow you to initialize the Telematics SDK in a few steps.
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
[RPEntry initializeWithRequestingPermissions:NO];
[RPEntry instance].lowPowerModeDelegate = self;
[RPEntry instance].accuracyAuthorizationDelegate = self;
[RPEntry sdkEnableHighFrequency:YES];
[RPEntry instance].virtualDeviceToken = `VIRTUAL_DEVICE_TOKEN`; // Unique user device token
if ([RPEntry instance].virtualDeviceToken.length > 0) {
[RPEntry initializeWithRequestingPermissions:YES];
}
[RPEntry application:application didFinishLaunchingWithOptions:launchOptions];
[RPEntry instance].apiLanguage = RPApiLanguageEnglish;
if ([ASIdentifierManager sharedManager].isAdvertisingTrackingEnabled) {
[RPEntry instance].advertisingIdentifier = [ASIdentifierManager sharedManager].advertisingIdentifier;
};
return YES;
}
You must add the necessary Background Tasks to the Info.plist file for the Telematics SDK to work.
<key>BGTaskSchedulerPermittedIdentifiers</key>
<array>
<string>sdk.damoov.apprefreshtaskid</string>
<string>sdk.damoov.appprocessingtaskid</string>
</array>
You can always find out all about the new changes with the release of xCode13 in our Telematics SDK documentation https://docs.damoov.com/docs/-download-the-sdk-and-install-it-in-your-environment In the new version of the Telematics App, these tasks are added.
An important part to record user's trips is to properly request permissions to use the user's Location and Motion & Fitness activity. Telematics SDK includes a specially designed Wizard that helps the user explain why the application needs it and make the right choice.
Note: this wizard is fully cutomizable, you can find the documentation here: https://docs.telematicssdk.com/docs/ios-sdk-asset-customisation
Below is an example of initialization with the launch of the step-by-stepWizard
[[RPCSettings returnInstance] setWizardNextButtonBgColor:[UIColor blackColor]];
[[RPCSettings returnInstance] setAppName:@"TelematicsApp"];
[[RPCPermissionsWizard returnInstance] launchWithFinish:^(BOOL showWizzard) {
[RPEntry initializeWithRequestingPermissions:YES];
[RPEntry instance].disableTracking = NO;
[RPEntry instance].virtualDeviceToken = `VIRTUAL_DEVICE_TOKEN`; // Unique user device token
}];
[[RPCPermissionsWizard returnInstance] setupHandlersWithUserNotificationResponce:^(BOOL granted, NSError * _Nullable error) {
NSLog(@"PUSH_NOTIFICATIONS INIT SUCCESS");
} motionManagerResponce:^(BOOL granted, NSError * _Nullable error) {
NSLog(@"MOTION INIT SUCCESS");
} locationManagerResponce:^(CLAuthorizationStatus status) {
NSLog(@"LOCATION INIT SUCCESS");
}];
We have created a special Framework that allows you to receive deviceToken, jwToken & refreshToken for full integration with our services. These keys are required to make calls to our APIs.
LoginAuth Framework is already integrated into this Telematics App.
You can find complete information about LoginAuth Framework in our repository https://github.com/Mobile-Telematics/LoginAuthFramework-iOS
Our goal is to provide your users with a user-friendly interface to get the best user experience.
To get the first data, user usually needs to drive a short distance. We set this parameter in the configuration file with the needUserDriveDistanceForScoringKm key.
Until the user overcomes the minimum required distance, he will see a special DemoDashboard, which we created in order to show user the main features of the application at an early stage. After overcoming the required minimum distance, the MainDashboard will be automatically available.
The Trips screen displays the trips users have made. To get rides, we use the method in the Telematics SDK library methods:
NSUInteger limit = 10;
__weak typeof(self) _weakSelf = self;
[self.dataSource setNextPageBlock:^(NSUInteger offset, PageLoadedBlock pageLoaded) {
[[RPEntry instance].api getTracksWithOffset:offset limit:limit startDate:nil endDate:nil completion:^(id response, NSError *error) {
RPFeed* feedScreen = (RPFeed*)response;
if (feedScreen.tracks.count) {
pageLoaded(feed.tracks); // Success
} else {
pageLoaded(@[]); // No user tracks
}
}];
}];
Using the example of the Telematics App, you can see how you can implement a page with trips, as well as use swiping with pagination and alternate loading.
The Telematics SDK allows users to change their Driver Signature role for any trip.
[[RPEntry instance].api changeTrackOrigin:'USER_DRIVER_SIGNATURE_ROLE' forTrackToken:'SELECTED_TRACK_TOKEN' completion:^(id response, NSError *error) {
dispatch_async(dispatch_get_main_queue(), ^{
// Success
});
}];
USER_DRIVER_SIGNATURE_ROLE can only take the following string values below!
- OriginalDriver
- Passenger
- Bus
- Motorcycle
- Train
- Taxi
- Bicycle
- Other
Depending on your product use cases, you can also use our Tags feature. You can learn more about it here: https://docs.telematicssdk.com/docs/tags We also offer you a convenient interface for switching certain tags for each trip. Feed screen will allow to quickly switch between tags for each trip.
The Telematics SDK allows users to add specific uniquetags to any ride for ease of use.
For example, by adding tag options to any trip, you will be able to mark specific trips for Business/Personal or other options:
RPTag *tag = [[RPTag alloc] init];
tag.tag = @"Business"; // Your custom tag
tag.source = @"TelematicsApp"; // Your AppStore app name
[[RPEntry instance].api addTrackTags:[[NSArray alloc] initWithObjects:tag, nil] to:`SELECTED_TRACK_TOKEN` completion:^(id response, NSArray *error) {
dispatch_async(dispatch_get_main_queue(), ^{
// Tag success installed. Reload Feed screen trips now
});
}];
You can also remove back any tag previously set:
[[RPEntry instance].api removeTrackTags:[[NSArray alloc] initWithObjects:tag, nil] from:<SELECTED_TRACK_TOKEN> completion:^(id response, NSArray *error) {
dispatch_async(dispatch_get_main_queue(), ^{
// Tag deleted. Reload Feed screen trips now
});
}];
NOTE: you can use DEL tag and hide the trips marked by it in the app. These trips will be shown in DataHub on List of Trips page with a special mark that these trips were hidden in the app.
We allow users to see the events that happened to them during the trip.
We detect major events:Acceleration,Braking,Speeding,Cornering,PhoneUsage.
In the Telematics App, we offer you a clear interface that allows the user to change any event on the map if it's not correct or delete this event.
Also this feature allows us to make our AI-models much clever.
You can learn more about these services by following to our docs: https://docs.telematicssdk.com/docs/leaderboards
All 9 types of Leaderboard are presented in the Telematics App and you can figure out which of these options you actually need.
Note! Only users who have trips during latest 14 days participate in Leaderboard. Use placeholders for new and lost users.
Our telematics app allows you to work with DriveCoins for each user:
You can learn more about these services by following to our docs: DriveCoins - https://docs.telematicssdk.com/docs/drivecoins
In detail, you can see the work with methods for rewards in the Telematics App source code in the DriveCoins section.
Settings screen gives you the opportunity to make specific settings for the entire application, provide links to any guides, as well as addresses of technical support etc.
Use the values in the Configuration.plist file for easy linking for Privacy Policy, Email address or Rate you app links. This will help you easily customize the Settings screen.
In the new version of the app, we have provided the ability to select Tracking Mode in Settings. There may be 3 options - Automatic Tracking, On-Demand Tracking, Tracking disabled.
TheOn-Demand Tracking provides an updated Dashboard by applying and programmatically increasing Constraints in InterfaceBuilder and a special method for increasing the vertical dimensions of the DashboardController.m file. In this Mode, the user can create a Job for himself.
JobName is a specific tag identifier that will be added for 1 or any number of trips made by the user. The user must necessarily start a certain job or order, and complete it accordingly. In the future, when the trip is enriched on our backend-side, the app will receive statistics for this JobName tag. The user will see the number of trips made for this task, the rating of maneuverability, risk score, etc. All this is available in a new section on our Dashboard.
On-Demand Tracking is great for any business like delivery service, taxi and many others. Currently, this Mode will be an integral part of the Telematics App and provide you with a new experience of integrations and work options.
In the Telematics App source code, we show you an option to clear user data after logging out. Do not forget - to stop tracking and record user trips, you need to explicitly delete VIRTUAL_DEVICE_TOKEN.
This can be done using Telematics SDK method:
[[RPEntry instance] removeVirtualDeviceToken];
[[FIRAuth auth] signOut:nil];
You can also disable SDK with the trips uploading to prevent already recorded and stored on the device trips been not uploaded to Damoov platform. Learn more about available SDK methods here: https://docs.telematicssdk.com/docs/methods-for-ios-app
Telematics App provides you with the optional functionality to connect the app with an OBD vehicle adapter using Bluetooth® technology. OBD adapter is a small device that plugs into the CAN-port of your car.
Telematics App created by Damoov, has a full range of functionality that allows you to read almost any information and indicators from your vehicle, and add it to trips recorded by the Telematics App on iOS/Android. Connecting and disconnecting to your iOS device happens automatically. OBD adapter can detect accidents.
Detailed documentation and the basic principles of operation can be found in the development portal https://docs.telematicssdk.com/docs/bluetooth-obd To fully work with this functionality, you need additional equipment, which we can provide upon your request.
If you have a Company invitation code, enter it in the Join a Company section in Settings of our Telematics App. We have made an additional possibility that now your users can join any company upon request, if required.
We have tried to make for you convenient settings and easy entry for any part of the application. Having studied in more detail, you will see that you can customize any part of the Telematics App or Telematics SDK for your purposes, including fonts, official colors used in the application, and much more.
For example, in the source code folder you can find:
Color.m - a file containing all the colors used in Telematics app.
Font.m - a file containing all the fonts used in Telematics app.
In theUI project folder you can find all sorts of improvements for labels, buttons or other styles used in the Telematics App.
To fully understand how the Telematics SDK and all our services work, use our detailed docs and guides https://docs.telematicssdk.com/ to make all the process as easy as possible.
All detailed information on using Firebase© can be found in the documentation https://firebase.google.com/docs/auth/ios/start
Happy coding!
Official API services web-page