Service · App development

Building a car app for dealers, leasing or connected cars.

Custom apps for the automotive sector: from a customer portal for a dealer or garage to a driver app for leasing and a connected-car layer for a manufacturer. Telematics integration, eCall awareness and GDPR-grade handling of driving behaviour, without being locked into a standard OEM app.

Connected carFleet & leaseCarPlay / Android AutoTelematics APIs

A car app is more than a small screen next to the car.

A car app touches three worlds at once: the vehicle (telematics, OBD-II, OEM APIs), the driver (driving behaviour, location, identity) and your operation (planning, invoicing, maintenance, DMS). That means building one is rarely a matter of putting a mobile shell on top of existing software: it needs deep integration, and privacy and compliance questions are on the table from day one.

The market around car apps is also mature enough to give you a choice. For commodity fleet tracking, Webfleet, Geotab and Verizon Connect are excellent. For brand-specific connected-car functions, Volvo Connect, Mercedes me, Audi MMI and BMW iDrive provide their own OEM apps. We don't build to replace those for what they already do well. We only come into the picture when you want your own brand experience, a niche audience, a multi-vendor reality or an AI-augmented use case that no standard package can handle.

Since 2015 we have been building mobile apps for automotive users: a dealer chain with a maintenance portal for customers, a lease driver app with fuel receipt scanning and odometer reading integration, and a connected-car layer for a brand that didn't want to outsource its telematics data to a third party. The broader framework for our mobile app projects follows the same approach: cross-platform where possible, native where performance or OEM integration demands it, and always with an honest assessment of whether a custom app is the right answer at all.

The three types of car app we build most.

The difference lies in who the end user is and how much data comes from the vehicle itself. In the first conversation we'll advise which type suits your situation; often it's a combination.

For dealers, garages, MOT stations and importers

Customer app for a dealer or garage

A branded app where your customers can see their vehicle: maintenance reminders based on mileage or date, automatic MOT notifications linked to the RDW vehicle registration (the Dutch vehicle licensing authority), an online booking flow with calendar integration, photo updates on repairs in progress, invoice history and vehicle registration requests. It integrates with the DMS (ICAR, Autoplus, AutoTaxXL), so your service reception avoids double work and customers can book an appointment themselves in the evening.

MOT notificationBooking flowDMS integrationPush notifications
For lease companies, fleet managers and insurers

Driver app for lease & fleet

Your drivers and lease customers get a single app for fuel receipt scanning with OCR, damage reports including photo upload and GPS location, periodic mileage readings, vehicle registration details and maintenance appointments at a connected dealer network. Managers get a dashboard with insight into costs, damage claims, compliance and TCO trends, often alongside our fleet management app. For lease companies that don't want to push their drivers into Athlon Driver or ALD Mobile, this is the white-label alternative.

Fuel receipt OCRDamage reportingMileage readingsManager dashboard
For manufacturers, importers and car-sharing platforms

Connected car & brand app

Real-time vehicle status: location, fuel or battery level, pre-set climate control, unlocking doors, starting a charging session and viewing trip history. A white-label brand app for a manufacturer or importer, or a car-sharing flow with keyless entry via a digital car key. It integrates with OEM APIs (Volvo Connect, Mercedes me, Audi MMI, BMW iDrive), with generic telematics (OBD-II, Webfleet, Geotab, Trimble) or with your own in-vehicle gateway for brands that keep their data layer in-house. eCall awareness is built into our approach as standard, because it is mandatory for new vehicles in the EU.

OEM APIReal-time dataKeyless entryEV charging

What you get at the end of the project.

A production-ready iOS and Android app, everything around it to run it, and clear agreements on who manages what after go-live. We hand over deliberately, so your IT team or another agency can maintain the app later without you being tied to us.

  • iOS and Android appNative or cross-platform (React Native or Flutter), ready for the App Store and Play Store, using your own developer accounts.
  • Backend and integrationsA cloud backend (GCP, AWS or Azure) plus the integrations with your DMS, telematics vendor, payment provider and vehicle registration source through our API integration approach.
  • Privacy documentationDPIA, privacy statement text for your lawyers, and a data model setting out which vehicle and driver data is processed, for what purpose and for how long.
  • Codebase and architectureFull source code, build instructions, a CI/CD pipeline and an architecture overview so another team can take it over later.
  • End-user and admin trainingSessions for your service reception or fleet managers, plus a short video onboarding for end users within the app itself.
  • Maintenance contract (optional)Monitoring, OS updates, security patches, OEM API version management and ongoing development. Fixed monthly price with clear response times.

When a custom car app is the right choice.

For a commodity fleet, Webfleet, Geotab or the standard OEM app are often perfectly fine. We build when you recognise one of these patterns.

White-label

Dealer group or brand wants its own app

You have your own brand and customer base, and you don't want your drivers stuck in a generic OEM app or in your lease provider's app. The app carries your name, your colours and your service stack.

Niche target group

No standard package fits

A car-sharing start-up, classic car club, camper van rental, B2B parts platform or MOT test station with a booking flow: your target group is too specific for a commodity app.

Multi-vendor

Multiple telematics sources

You combine Webfleet, Geotab and Volvo Connect in a single fleet, or you want your drivers to see both your own vehicles and rental cars in the same app. That requires an abstraction layer that an off-the-shelf app doesn't provide.

AI-augmented

Predicting instead of reporting

Driving-behaviour coaching, predictive maintenance based on OBD signals, or a pay-as-you-drive tariff for an insurer. This is where the AI Act comes into play: predictive scoring for insurance is high-risk and requires a careful set-up.

How a car app project runs.

1

Introduction and data scan

What is in your DMS, which telematics vendor are you using now, and which OEM APIs are available? In the first conversation we map this out and determine which integrations are technically feasible within the scope.

2

Planning, DPIA and user research

A workshop with your team, interviews with a handful of end users (service technician, lease driver, customer) and a DPIA for the vehicle and location data. By the end, the scope, planning and first screen flows are in place.

3

Building in sprints

Every two weeks you get a working build to test, first on TestFlight and the Play Console internal track. We tackle the riskiest integration first, usually the telematics or DMS integration, so that risk is covered early.

4

App Store review and rollout

Privacy labels, App Store review, a phased rollout to your first user group and monitoring. After that we move on to a maintenance rhythm, or hand over to your own team.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Who we build car apps for.

The automotive sector is broad. The target groups below regularly ask us for a dedicated app. For each type, we outline which core features typically fall within the scope.

Dealers & car trade

Online maintenance booking and customer history

A customer portal with service history per licence plate, MOT reminders, an online appointment flow and push notifications as soon as a repair is finished. For dealer chains with multiple branches, there is a routing layer so customers can choose their own location.

Lease & rental

Driver app for lease drivers

For lease companies that want to use their own brand instead of Athlon Driver or ALD Mobile: fuel receipts, damage reports, mileage, maintenance appointments, licence plate entitlements and, optionally, driving-behaviour coaching with clear GDPR consent.

OEM & importer

White-label brand app for brand owners

For manufacturers and importers who want to run their connected-car layer under their own brand. Real-time car status, climate, doors, charging, plus a service layer towards the dealer network.

Connected-car platforms

Telematics plus app layer

For companies that want to merge vehicle data from multiple sources (OBD dongle, OEM API, own gateway) into a single app for the end user. We build the abstraction layer that hides the differences between sources.

Car sharing & MaaS

Keyless unlocking and booking

For car-sharing start-ups and mobility platforms: digital car key, booking, damage check-in and check-out, and integration with MaaS providers. It calls for carefully designed offline modes for when coverage drops out.

Insurers

Pay-as-you-drive and driving behaviour

Telemetry data to differentiate premiums or for prevention programmes. The AI Act and GDPR are decisive here: predictive scoring for insurance is high-risk and requires explicit explainability, opt-in and human review.

Garages & MOT stations

Appointment flow and repair progress

For independent garages and MOT stations: an appointment flow, photo updates during repairs, invoices in the app and a reminder for the next MOT. It works without its own DMS through a lightweight scheduling layer.

Breakdown assistance & roadside recovery

Reporting and technician app

Two connected apps: a reporting app for the driver with location sharing and status, and a technician app for the roadside patrol with a job flow, navigation and reporting. Often linked to a central dispatch system.

Tech stack and telematics choices.

A

Cross-platform: React Native or Flutter

For most customer and driver apps, we start with React Native or Flutter. One codebase, two app stores, faster delivery and lower TCO. For 80 per cent of the features you need — forms, photo upload, push notifications, OCR — that is more than enough.

B

Native iOS and Android where needed

We build natively where the feature genuinely demands it: heavy background services for continuous trip logging, complex Bluetooth LE integrations with an OBD dongle, or native CarPlay and Android Auto extensions that are not available through cross-platform frameworks.

C

OEM APIs: Volvo Connect, Mercedes me, Audi, BMW

For connected-car features tied to a single brand, we integrate with the OEM's API. This gives the deepest data — charge status, climate, doors — but ties you to one brand and to the manufacturer's API policy. We check upfront which endpoints are stable and which still fall under a developer API.

D

Generic telematics: OBD-II, Webfleet, Geotab

For multi-brand fleets, we use OBD-II dongles or existing telematics vendors such as Webfleet, Geotab, Verizon Connect or Trimble. This gives less detailed data than an OEM API, but works across all the brands in your fleet.

E

Backend in the cloud, sometimes at the edge

The backend runs on GCP, AWS or Azure by default. For connected-car applications where latency matters — unlocking doors instantly, real-time climate control — we look at edge compute or an in-vehicle gateway. It's not needed for every project, but the difference between 200ms and 2s sometimes matters.

F

DMS integration for dealer flows

For dealer and garage apps, the DMS integration is often the riskiest step. We have proven experience with ICAR, Autoplus and AutoTaxXL, and we tackle that integration in sprint one so any surprises surface early.

Compliance: GDPR, AI Act, eCall and licence plate rights.

Car apps collect sensitive data. Not only location and driving behaviour, but also employer-driver relationships and, in some cases, biometrics. Four compliance themes come up in almost every project.

GDPR

Location and driving behaviour are personal data

Vehicle location linked to a person is personal data. For employees, rules on electronic monitoring apply on top of the GDPR. We start with a DPIA, build in data minimisation and purpose limitation, and provide a granular opt-in that lets the driver review their own data trail.

AI Act

Predictive scoring is high-risk

Pay-as-you-drive and driving-behaviour scoring for insurance premiums fall under the AI Act, often as high-risk. That means requirements around explainability, human review, monitoring and logging. We run the AI Act assessment upfront and build those requirements in, rather than bolting them on afterwards.

eCall

Mandatory in new vehicles in the EU

Since 2018, eCall has been mandatory in new passenger cars in the EU. For your own connected-car app, that means: know when a vehicle already has an eCall system, don't conflict with it, and respect the privacy buffer around accident data.

Licence plate rights and RDW

Official sources, no scraping

For MOT reminders, ownership checks or licence plate rights requests, we work with official channels — RDW open data, licence plate check APIs or MOT data — not scraping. This is more robust and stays within the rules.

Frequently asked questions.

What clients usually want to know before we start.

What falls under a car app?
The term car app covers three families: customer apps for a dealer or garage (appointment flow, maintenance reminders, MOT), driver apps for lease and fleet (fuel receipts, damage reports, mileage) and connected-car apps that pull data directly from the vehicle (location, fuel, climate, keyless entry). In practice, we combine functions — for example, a dealer customer app with a connected-car layer for brand owners, or a lease driver app with a car-sharing component for pool cars within the fleet. Which type suits you depends on your end user, your operation and the data sources you have available.
What is the difference between a fleet app, a driver app and a dealer app?
A fleet app is for the fleet manager: costs, damage, planning, compliance — mainly a dashboard. A driver app is for the employee or lease driver behind the wheel: fuel, damage, mileage, appointments. A dealer app or garage app focuses on the customer who has their vehicle serviced with you: appointment, repair status, invoice and licence plate permissions. We often build them as a single platform with multiple role-based apps or screens.
Which connected-car APIs do you use?
We work with the common OEM APIs where your target group requires it: Volvo Connect, Mercedes me Connect, Audi MMI, BMW iDrive and Tesla's API. For brand-agnostic work we use generic telematics sources such as OBD-II dongles, Webfleet API, Geotab, Verizon Connect and Trimble Driver. For heavy commercial vehicles we also look at Daimler Truck Suite, MAN ServiceCare and Volvo Connect Trucks. Things worth checking up front: which OEM APIs are open to third parties, what data they expose, which subscription tier is required, and how often the API version changes. Some OEM APIs change every quarter — that is a maintenance burden that needs to be built into the planning.
Do you work with Apple CarPlay and Android Auto?
Yes, for apps where the user needs a function while driving — navigating to the garage, listening to a maintenance alert, recording a trip log. Apple and Google are strict about which app categories may run in the in-car environment (mainly navigation, audio, communication and parking). During the scoping phase we advise whether CarPlay or Android Auto is really needed, or whether a regular mobile app will do.
How do you handle GDPR for driving-behaviour tracking?
Location and driving behaviour are personal data, and for employees extra strict rules apply to electronic monitoring. We start every project with a DPIA, build in privacy by design (data minimisation, purpose limitation, granular opt-in, a clear right to erasure and visibility of what is recorded about the driver) and supply a privacy statement text for your legal team. For insurers considering pay-as-you-drive we also look at the AI Act, because predictive scoring for insurance can fall under high-risk and requires the score to be explainable to the driver. For lease companies that want to use driving-behaviour data for coaching or premium differentiation, we document up front what purpose it serves and how long the data is retained — otherwise it remains legally grey.
How do you choose between Webfleet, Geotab and an OEM API?
It depends on your fleet and your operation. Webfleet (Bridgestone) and Geotab are strong for multi-brand fleets with OBD dongles and an extensive dashboard. OEM APIs such as Volvo Connect or Mercedes me give deeper insight into a single brand but don't connect to other brands. We regularly advise combining both: an OEM API where possible, a generic telematics dongle where necessary.
What determines the cost of a car app?
Mainly the number of integrations (DMS, telematics, payments, licence plate permissions, RDW, OEM APIs), the number of user roles, and whether the app can be cross-platform with React Native or Flutter or needs to be native iOS and Android for specific OEM features or CarPlay extensions. Connected-car features with real-time data increase complexity, especially if multiple telematics sources come together or if the app has to support keyless entry or a digital car key. GDPR and AI Act requirements also add to the scope. In the first conversation we give you an honest indication based on your brief.

Talk to us about your car app.

A no-obligation introductory call of half an hour. We listen to your target group, your existing telematics choices and your DMS, and give you direction you can act on straight away. If charging is a key part of the project, you may want to look at our EV charging point app page first, or at our transport software page if the cars are part of a logistics flow.

Edit content