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

From SDK Integration to Your First Recorded Trip

Developer workspace showing a laptop with code editor and a smartphone displaying a completed GPS route, illustrating mobile telematics SDK integration and the first recorded trip in a telematics application.

The first useful milestone in a telematics integration is not a compiled sample. It is a recorded trip you can open in DataHub: start, end, distance, and a score. This article is the quickstart narrative from SDK add → permissions → automatic tracking → that trip.

Canonical steps live in the docs. Do not treat this page as a substitute for Add the SDK to your app or the platform-specific Android guide. It is the story around those pages for Alex, with Priya able to follow the checkpoints.

If you have not seen a trip on a phone yet, Try Zenroad (via the cluster OneLink) so you know what “done” looks like.

Success is a recorded trip

Until a trip exists, you cannot validate scoring, events, or APIs. A map widget with live GPS is not the same object. The SDK’s job, per docs, is to capture trips, driving behavior events, GPS location, and crash data; the cloud exposes them through APIs and DataHub.

Set the team definition of done as: one real drive, permissions granted, trip visible in DataHub (or via API), with mileage and a safety score. Everything after that is product work.

Prepare: workspace, test user, DeviceToken

Docs preparation is short:

  1. Start free and create a developer workspace.
  2. Create a test user and obtain a DeviceToken — in DataHub or via the register-user API documented in the developer portal.
  3. Optionally clone TelematicsApp-Android or TelematicsApp-iOS if you want the reference UI instead of a blank host app.

Without a DeviceToken, the SDK has nothing to attach trips to. Do not skip this for a “just compile” demo.

Add the SDK (native and cross-platform)

The integration index covers:

  • Native iOS (Swift Package Manager or CocoaPods) and Android (Gradle)
  • React Native and Flutter wrappers that call the native SDK
  • Xamarin

Cross-platform note from docs: add the native SDK to the native layer, then use the bridge. Platform-specific Android steps are at Add the SDK to your app (Android). iOS demo install remains a high-click docs page — use it when you need a known-good host app.

For code-level trip callbacks and autoStartOn, the worked example is in How Automatic Trip Detection Works. Copy from docs, not from memory.

Permissions are part of the integration

Automatic background detection cannot work without the location and motion permissions the OS requires. Design the permission wizard as a product surface, not an afterthought. iOS Always authorization and Android background location plus battery exemption are the usual failure pair.

See docs.damoov.com permissions guides for the current copy and sequences. This article will not freeze screenshot text that the docs may update.

Enable automatic tracking

Initialize the SDK, set the device ID, enable it after permissions, and turn on automatic tracking. The behavior is documented in Automatic tracking: the SDK records trips without a user tapping start.

If your product should only record on-shift driving, do not leave automatic mode on 24/7. Switch to scheduled, on-demand, or Bluetooth-triggered tracking as documented. The first recorded trip for a proof-of-integration can still be automatic; the production mode can change later.

Confirm the trip

  1. Drive at vehicle speed long enough to leave the candidate state (a real street, not shaking the phone at a desk).
  2. Wait for trip end — a dwell window, not “speed hit zero at a light.”
  3. Open DataHub and find the test user’s trip: route, mileage, timestamps, score.
  4. Optionally hit the statistics / trips API with the same device token.

Docs also describe test trips for UI work once tracking itself is healthy. Do not use simulated UI data as a substitute for the first real trip.

Why the first trip fails

  • SDK enabled before permissions, or Always/background location denied.
  • Android battery optimizer killing the process. See the battery article.
  • No DeviceToken / wrong environment (demo vs your workspace).
  • Desk test: walking or GPS drift never commits to DRIVING.
  • Waiting 10 seconds after parking. Trip end is a dwell, not an instant.

When it works, you have a repeatable path: SDK + docs + sandbox. Then you start replacing Zenroad screens or wiring webhooks.

FAQ

How long until the first trip?

Docs describe a working integration that many teams finish in a first session, plus one real drive. Production hardening (OEM batteries, copy, QA) is longer. Do not quote a Damoov SLA that does not exist.

Should I start from Zenroad or an empty app?

If you need UI, clone Android or iOS. If you already have an app, add the SDK to it. Either way the first recorded trip is the same object.

Get the first trip on the board

Add the SDK, take one drive, and open the trip in DataHub. Docs: Add the SDK to your app. Proof app: Zenroad.

Try Zenroad: Try Zenroad (OneLink β€” desktop lands on the app page; mobile goes to the stores).

Start free: Start free in DataHub.

View source: Android Β· iOS Β· org.

View docs: 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

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.