Damoov was named Vehicle Telematics Innovation of the Year in the 2026 AutoTech Breakthrough Awards.

Don’t Start From a Blank Screen: Build on Zenroad’s Telematics App Source Code

Developer workspace with telematics application code on a computer monitor and a smartphone displaying GPS route tracking, illustrating mobile telematics SDK integration and telematics app development.

Don’t start from a blank screen. Zenroad is Damoov’s free, open-source reference app: a working iOS and Android implementation of trip detection, mileage, driving scores and DataHub connectivity, built on the Damoov telematics SDK. The complete telematics app source code is on GitHub.

In short: register a free DataHub workspace to get your InstanceId and InstanceKey, create a Firebase project for user login, clone the Android (Kotlin) or iOS (Swift) repository, put your keys in AppConfig.kt or Configuration.plist, and build the app to a phone. Trips recorded by that build appear in your DataHub workspace. Then keep the SDK and replace the screens with your own.

If you want the generic API/SDK overview, that already lives on Getting Started with Telematics APIs & SDKs. This page is the missing piece: start from Zenroad, not from an empty accelerometer buffer.

What a blank-screen telematics build actually costs

Teams rarely underestimate the UI. They underestimate the invisible work: trip start/stop, background modes, permission wizards, battery, and the first scored trip that actually looks like driving. That pipeline is explained in How Automatic Trip Detection Works — sensor fusion, a motion state machine, and iOS/Android background rules. Rebuilding it is a long project, not a sprint.

A blank-screen build usually goes in this order:

  • First, GPS points on a map. It looks like progress.
  • Then false trips, split commutes and battery complaints.
  • Scoring and data export come last, and often still aren’t production-grade.

Zenroad starts you at the other end. In the reference app, the SDK already detects trips, walks the user through permissions and scores driving. You add your own keys, then replace the UI.

What Zenroad is — and is not

Zenroad is Damoov’s free, open-source reference telematics app for iOS and Android. It automatically records trips, logs mileage, and calculates safety and eco-driving scores. The source is on GitHub under the Mobile-Telematics organization, and Damoov maintains it as the reference implementation of its telematics SDK.

You can white-label it: rebrand, change the UI, and use it as a starting point. You can also treat it as a demo of the stack before you add the SDK to an app you already have.

What it is not:

  • A finished product for your users. Onboarding, brand, store listing and back-office workflow stay with you (see “What you still have to build”).
  • A required shell. You can keep only the SDK and build every screen yourself.

The reference app shows the data layer working end to end. Your product still owns workflow, exports and brand.

What you get in the GitHub repos

Two complete apps, one per platform:

  • TelematicsApp-Android — Kotlin reference app. The Zenroad page lists a dashboard, trip feed, trip details, rewards, leaderboards, driver profile and vehicles, settings, Bluetooth OBD connection, and joining a company.
  • TelematicsApp-iOS — Swift reference app with the same screens, plus a Claims screen.

Both live in github.com/Mobile-Telematics. The data is split in two. Login and personal details sit in your own Firebase project, in the region you choose (the Zenroad page lists US, Europe and Singapore). Telematics data is processed and stored by the Damoov platform, in Europe by default, with an option to export it to your own server.

Configuration is file-based: AppConfig.kt on Android, Configuration.plist on iOS. Your DataHub InstanceId and InstanceKey go there. The steps are below.

The clone path: keys, Firebase, build, first trip

The Zenroad page lists the developer steps; the two READMEs add the Firebase and Google Maps setup the build needs. In order:

  1. Register a developer workspace. Start free in DataHub (a 90-day sandbox, no credit card) and copy your InstanceId and InstanceKey.
  2. Create a Firebase project. Turn on Authentication and the Realtime Database, then download google-services.json (Android) or GoogleService-Info.plist (iOS). Zenroad uses Firebase for user login and personal data.
  3. Get a Google Maps API key. Both READMEs walk you through creating one in the Google Cloud Console.
  4. Clone the repository. TelematicsApp-Android (Kotlin) or TelematicsApp-iOS (Swift).
  5. Add your keys. Put the InstanceId and InstanceKey in AppConfig.kt (Android) or Configuration.plist (iOS), add the Firebase file to the project, and set the Maps key as the README describes.
  6. Build and run on a device. Grant the permissions the in-app wizard asks for, then drive. Tracking is automatic, with no start/stop button. Trips from this build appear in your DataHub workspace.

Next, keep the SDK and replace the screens with your product’s own. Already have an app? Skip the clone: the quick start adds the SDK to an existing app in three steps, natively on iOS and Android or through React Native and Flutter. The Telematics SDK page has the overview.

A first trip is a milestone, not production readiness. Battery behavior, device-maker quirks and your permission copy still need product work.

What you still have to build

Zenroad is a reference, not your roadmap. You still own:

  • Onboarding, brand, and the permission explanations that app store reviewers and your users will read.
  • Tracking rules. The reference app offers automatic and on-demand tracking and business or personal trip tags; your product decides which apply and when.
  • Backend workflow: webhooks, payouts, coaching, underwriting. The API returns trips, scores, and events; it does not run your business process.

That split is the point. You don’t get a finished consumer app. You start from a working reference for the hard part.

Who this path is for

Engineers: you need a prototype that records a real trip before the architecture review. Clone Zenroad, or add the SDK to a sample app, and bring a trip in DataHub to the meeting, not a slide.

Product managers: you need progress you can show. “We forked the reference app and recorded our first trips” is a better status update than “we are still tuning GPS.”

If you need a personal mileage log rather than a product to build, see Best Mileage Tracking & Logbook Apps. For the sensor-level explanation, read How Automatic Trip Detection Works and its companion on background tracking and battery.

FAQ

Is Zenroad the same as the Damoov SDK?

No. Zenroad is the open-source reference app. The SDK is the library you embed. Zenroad uses the SDK so you can see the stack on a phone before you integrate.

Do I have to use the Zenroad UI in production?

No. White-label it, or keep only the SDK and build your own screens. The GitHub apps are a starting point, not a required shell.

Where do I try it without cloning?

Install Zenroad from the App Store or Google Play and drive normally to see trips, mileage and a driving score. To see trips in your own DataHub workspace, build the app with your own keys (steps above) or add the SDK to your app.

Do I need Firebase to run the reference app?

Yes, for the cloned app. Zenroad uses your own Firebase project for user login (Authentication) and personal data (Realtime Database). Telematics data goes to the Damoov platform under your DataHub keys. If you add the SDK to an app you already have, Firebase isn’t required: you register users through the Damoov API or the LoginAuthFramework libraries (quick start, step 2).

Start from the reference app

Don’t start your telematics app from a blank screen. Clone the reference, take one scored trip, then embed the SDK in the product you actually ship.

Try Zenroad: install it from the App Store or Google Play.

Start free: Start free in DataHub.

View source: Android · iOS · org.

View docs: Quick start · Install the iOS demo app · Add the SDK to your app · Automatic tracking.

Useful links to build your own app

  1. Company website: Damoov telematics platform
  2. Open-source telematics app: Damoov telematics app
  3. Telematics SDK: Damoov telematics SDK
  4. Telematics API: Damoov telematics API
  5. Developer portal: Damoov documentation
  6. Datahub: Damoov DataHub
  7. GitHub org: Mobile-Telematics
  8. Android reference app: TelematicsApp-Android
  9. iOS reference app: TelematicsApp-iOS

Related reading

Solutions Across Mobility Industries

Purpose-built telematics capabilities for fleet, insurance, mobility, and education verticals.

🚛

Fleet Management

Real-time location monitoring, driver safety scoring, and fleet-wide performance analytics.

📦

Logistics & Delivery

Trip logging, driver behavior monitoring, and real-time speed and location tracking for every delivery.

🚕

Mobility Platforms

Driver performance metrics, trip-level behavior analysis, and live location tracking for ride and mobility services.

🛡️

Insurance

Driving behavior data for usage-based insurance, risk scoring, and claims evidence.

🎓

Driving Schools

Student driving behavior assessment, lesson-by-lesson safety scoring, and progress tracking.

🚌

School Transport

Real-time vehicle tracking, driver safety monitoring, and trip visibility for parents and administrators.

🔑

Carsharing & Rentals

Vehicle location tracking, trip logs, and driver behavior monitoring for shared and rental fleets.