Industry · Transport & logistics

Custom driver app development for road, taxi and courier.

A custom driver app for truckers, taxi drivers, couriers and service engineers: native iOS and Android, offline-first, with proof of delivery, route instructions, tachograph readout, BCT integration and a direct link to your TMS or planning system.

Native iOS & AndroidOffline-firstPOD & CMR signingTachograph & BCT

The driver is your most important end user.

Between the planning desk at the office and the delivered load stands one person: the driver. What they do with the app on the road determines whether your planning holds up, whether your customer knows in time when the shipment will arrive, whether you have to fix your driving-time records afterwards, and whether proof of delivery stands up legally. A custom driver app is therefore not a loose mobile shell on top of a TMS. It is a work product in its own right, designed from the cab or the van, not from a dashboard at the office.

We build these custom apps for transport companies, taxi organisations, courier services and service companies who find that the standard driver module from their TMS supplier falls short. For the broader range of mobile work apps, see our app development; for the planning and back-office layer this app connects to, read our page on custom transport software.

At first glance, a driver app overlaps with a field service app or a work order app: a mobile professional handling work on the road, taking photos and collecting signatures. The difference lies in the transport-specific parts: driving-time regulations, tachograph, BCT cradle for taxis, AETR for international transport, CMR digital signing, and integrations with TMS systems such as Transics, MendriX and Carrierweb that no other field service app supports out of the box.

Beyond the work on the road, there is the question of whether a driver is deployable at all: driving licence, Code 95 and medical certificate each have their own expiry date. How we keep track of all three is covered on driving licence and Code 95 monitoring.

Three flavours of driver app.

Which direction suits you depends on your type of transport, how deeply the app needs to sit in your planning and compliance chain, and which hardware your drivers use. In the first conversation we advise which combination makes sense.

Compact project · fixed sprint budget

Driver app for couriers and van transport

For parcel, food and general cargo couriers with a fleet of vans. Receiving trip assignments, navigation instructions, proof of delivery with photo and signature, returns flow and instant reporting back to planning. Works offline on slower 4G in fringe areas and syncs as soon as signal returns.

Trip assignmentsPOD flowPhoto & signatureReturns administration
Mid-sized project · fixed sprint budget

Trucker app for road transport

For carriers with tractor-trailers, distribution or long-haul transport. Trip assignments with loading and unloading documents, CMR digital signing, tachograph readout via Bluetooth, load management, route instructions with truck-specific routing and exception reporting (traffic jams, damage, refusal at the gate). Integrates with TMS systems such as Transics, MendriX and Carrierweb and with your planning API for real-time ETAs.

CMR signingTachographLoad managementTMS integration
Larger project · fixed sprint budget

Taxi or service engineer app with hardware

For taxi organisations with a BCT obligation or for service companies with service engineers on site. BCT cradle integration for taxis, including the Boordcomputer Taxi protocol, an integration with a customer portal for ETAs, BLE connection with vehicle and truck sensors, hardware buttons on ruggedised Zebra or Honeywell devices, and a work order layer for service engineers — overlapping with our work order app.

BCT cradleZebra & HoneywellBLE sensorsCustomer portal ETA

What a driver app typically does.

A single app usually covers a set of work processes that sit separately in standard TMS modules, or don't work on mobile at all. For your driver, it is one streamlined flow, from logging in at the start of the shift to closing down and syncing on getting home.

  • Receiving and confirming trip assignmentsFrom your planning system or TMS, the trip is pushed to the device. The driver sees the address, load, customer contact and special instructions, then confirms acceptance or reports a problem straight back to planning.
  • Route guidance with truck routingNo consumer navigation without height or weight restrictions, but a navigation layer that takes account of truck routes, time windows in cities and low-emission zones. For taxis and couriers, it includes city routing with turn-by-turn directions and exemptions for permit holders.
  • Proof of delivery: photo and signatureOn delivery: a photo of the delivered load in the right place, the recipient's signature on screen, and optionally their name and position. The file goes to your TMS as a PDF and serves as evidence in the event of a later claim.
  • Digital CMR signingFor international road transport, a digitised CMR consignment note with an eIDAS-compliant signature from sender, carrier and recipient. It complies with the e-CMR protocol and is accepted by most European customs authorities in countries that have ratified that protocol.
  • Reading the tachograph via BluetoothFor road transport with a digital tachograph: the driver reads their card without a cable cradle, using a Bluetooth connection to the tachograph. Driving times, breaks and activities are visible in the app and can optionally be passed on to your trip administration.
  • BCT integration for taxisThe Boordcomputer Taxi (BCT, the on-board taxi computer) is mandatory in the Netherlands for contract transport. The app communicates with the BCT cradle, records the start and end of the shift and whether a trip is free or occupied, and sends the payroll data to your taxi administration. The driver doesn't have to switch between two screens.
  • Drawer and stock managementIn distribution, the right load sits in the right drawer in the right order. The app prevents wrong deliveries by asking at each stop which packages come out of which drawer, with optional barcode or QR scanning for certainty.
  • Exception reportingTraffic jams, damage to the load, refusal at the gate, an empty address, a dangerous situation: exceptions are reported in a few taps, with a photo and optionally a short voice note, and reach planning immediately. No more disruptive phone calls on the road.
  • Background location and geofencingThe app tracks the vehicle's position for ETA calculation and geofence events at loading and unloading addresses. It is invisible to the driver, but gives your planning team and your customer portal real-time insight into when a shipment will arrive.
  • BLE sensors in the tractor unit or vanBluetooth integration with sensors for temperature (temperature-controlled transport), open doors, fill level or tyre pressure, with readings tied to stops. A deviation triggers an alert to the driver or straight to planning.
  • Hardware buttons on ruggedised devicesFor drivers using Zebra TC, Honeywell CT or similar rugged devices, we map the hardware buttons to functions that can be used without looking: scan, next stop, emergency button. It also works with gloves on and in the rain.
  • Customer portal integration for ETAsThe position and stop data from the driver app feed your customer portal: the recipient sees when the shipment will realistically arrive, gets a notification at the stop before, and can follow up on a delay proactively if needed.

When a custom driver app is the right choice.

We don't replace the driver module of Transics or MendriX for commodity functions. Custom makes sense when your flow differs from what those modules can do out of the box. If you recognise one of these patterns, we'd be glad to talk further.

UX for the cab

A standard app stays awkward in practice

Your drivers have been complaining for years about buttons that are too small, screens that have to be filled in three times per stop, or steps in the wrong order. Standard TMS modules usually can't adjust those UX choices. Custom lets us redesign the screens around how your people actually work, often with large buttons, one-handed operation and glove-friendly controls.

Type of transport

A niche flow that doesn't fit the mainstream

Temperature-controlled transport with proof requirements, dangerous goods (ADR), heavy haulage with route notification, crane trucks, car transport or medical transport all have reporting and protocol requirements that aren't built into mainstream driver modules. A custom app makes that discipline-specific flow genuinely workable.

Deep integration

TMS, planning and customer portal together

You want a stop in the app to immediately send its status to your TMS, your planning, your customer portal and your invoicing system, without anyone manually re-entering data along the way. We build that integration layer (see also our page on the transport planning API), with conflict resolution for the offline moments when several systems have tried to change something at the same time.

Hardware choice

Bring-your-own-device or a rugged fleet

Do you work with your drivers' personal phones under a BYOD policy, or with a fixed fleet of Zebra, Honeywell or TomTom devices? Or a mix, with a rugged device in the cab and a personal iPhone for break administration? A custom app takes that hardware choice into account, including MDM, kiosk mode and hardware buttons.

Taxi with BCT

On-board computer requirement for taxis

For contract transport in the Netherlands the BCT (on-board taxi computer) is mandatory, so a driver module that doesn't support it smoothly is not an option for a taxi organisation. We build in the integration with the BCT cradle, including the pay data flow to your taxi administration, shift and quarter overviews, and correct trip classification.

International transport

AETR, e-CMR and cross-border compliance

Transport outside the Netherlands is subject to the AETR agreement on driving times, the e-CMR protocol for the digital consignment note, and country-specific rules on cabotage or low-emission zones. A custom app builds those rules into the screen flow so your driver doesn't have to remember what is allowed in each country. The app warns them before a violation occurs.

How a driver app project works.

1

Introduction

A conversation in which we learn what type of transport you do, which TMS you use, what hardware your drivers work on, and where the current flow gets stuck. By the end we'll know whether a custom app is realistic for your scale or whether a lighter solution will do.

2

Cab interviews and scope

We ride along with two to four drivers from different disciplines, for example a long-haul driver, a distribution courier and perhaps a service engineer or taxi driver. We also interview your planning and back-office teams. By the end you have a concrete scope, screen flow sketches and a realistic plan per sprint.

3

Building in sprints

Every sprint delivers a working build that your drivers actually take on the road, not just something tested in the meeting room. We first get the trip and POD flow working, then navigation and exception reporting, then tachograph, BCT or CMR, and finally the deeper integrations.

4

TMS and hardware integration

Integration with your TMS (Transics, MendriX, Carrierweb or another platform), with your planning or a customer portal, and with the hardware in use: BCT cradle, tachograph, rugged scanners, BLE sensors in the tractor unit or van. By the end, the whole chain truly works end to end.

5

Rollout and maintenance

A phased rollout, with training for the driver-trainers and short video instructions for the rest of the fleet. After that, ongoing maintenance: App Store and Play Store updates, security patches, MDM rollouts for your rugged devices and further development based on what real-world use teaches us.

Compliance and regulations in a driver app.

Road freight and passenger transport are heavily regulated. A good driver app records the evidence that you meet the applicable requirements, not as after-the-fact reporting but built into the workflow on the road.

GDPR

Driver location is special-category personal data

In the Netherlands, an employee's position throughout the day is a sensitive category of personal data. We design the app with privacy by design: location is only recorded during working hours, there is no tracking during breaks, retention periods are set per data type, and drivers get a transparent overview of what the app stores about them. A DPIA is a standard part of every large project.

ATW & Rijtijdenbesluit

Working Hours Act and driving times

The Dutch Working Hours Act (Arbeidstijdenwet) and the Driving Times Decree (Rijtijdenbesluit) are the basis for the Dutch driving-time records of professional drivers. The app helps drivers stay within permitted driving and working hours, with advance warnings instead of fines after the fact, and provides the evidence for inspections by the ILT (the Dutch Human Environment and Transport Inspectorate).

AETR

International driving-time agreement

Road transport to countries outside the EU falls under the AETR agreement, which is similar to the EU driving-time regulation but not identical. The app switches to the correct rule set based on where the trip runs, and keeps track of whether a digital or analogue tachograph is being used.

BCT requirements

On-board taxi computer protocol

For contract transport and holders of a Passenger Transport Act (Wp2000) licence, the BCT (on-board taxi computer) is mandatory under the Taxi On-Board Computer Regulation. We build the integration with the BCT cradle in line with the protocol, including wage-data export to the Dutch Social Insurance Bank (SVB) and evidence for the ILT and the Tax Authority.

eIDAS

Legally valid digital signatures

A signature on a screen is not automatically a legally valid signature. For CMR signing and proof of delivery, where evidence matters in a claim, we use eIDAS-compliant signature levels, with an audit log for every signing event: who signed, when, at which location, and with which certificate.

ADR

Transport of dangerous goods

The transport of dangerous goods falls under the ADR agreement, with specific documents in the cab, route restrictions and orange-plate administration. The app keeps the ADR documents available, warns about prohibited routes (such as tunnels in certain categories) and logs evidence for any ILT inspection.

TMS systems we integrate with.

Most hauliers and taxi organisations already have a TMS or planning package. A custom driver app does not replace it, but wraps its own layer around what the package does not do itself, or replaces only the driver module, with a clean integration to the rest.

Dutch and European TMS packages

Transics, MendriX, Carrierweb

Transics (part of WABCO/ZF) and MendriX are common choices in Dutch and Belgian road freight; Carrierweb is popular with mid-market hauliers that want their own platform. They are strong in TMS functionality, but often more limited in mobile UX and sector-specific flows. We integrate via available APIs or via structured EDI or CSV exchange.

TransicsMendriXCarrierwebTranswide
Planning, ETA and routing

Ortec, Locus, Roadnet

For planning functions you are more likely to work with Ortec, Locus, Roadnet or similar optimisation packages. The driver app receives the planned route, sends deviations (traffic jams, delays, damage) back and supplies real-time position and stop data for the ETA model. For larger hauliers we often build a dedicated planning API as an integration layer; we wrote the page transport planning API about this.

OrtecLocusRoadnetCustom planning API
Hardware suppliers

Zebra, Honeywell, BCT cradle suppliers

For ruggedised devices, we mostly come across Zebra TC and Honeywell CT devices, and to a lesser extent Datalogic. For taxis, we work with the cradle suppliers certified in the Netherlands for the BCT (Boordcomputer Taxi, the taxi on-board computer). We make sure our app runs smoothly on these devices, maps the hardware buttons and rolls out with the right MDM solution (SOTI, VMware, Microsoft Intune).

Zebra TCHoneywell CTSOTI MDMIntune

Frequently asked questions.

What hauliers, taxi organisations and courier services usually want to know before we start.

Do you replace the driver module from Transics, MendriX or Carrierweb?
Sometimes entirely, sometimes only for specific flows. For commodity functions (accepting jobs, simple proof of delivery) those modules are often good enough. For industry-specific flows, niche transport or hardware integration that isn't supported as standard, we replace the driver module entirely with a direct integration to the TMS behind it. In the first conversation we determine which route suits your situation.
Does the app work on the road without a signal?
Yes, offline-first is standard. On a motorway outside the Randstad, on the edge of an industrial estate or in the shadow of a tall concrete structure, you sometimes get no data for minutes at a time. Job assignments, PODs, photos, signatures and exception reports are stored locally on the device and synchronise as soon as there is a signal again. Conflict resolution is built into the design, in case the planning team at the office has changed something on the same trip in the meantime.
How do you handle tachograph downloads?
For digital tachographs, we read out the driver card and optionally the mass memory via Bluetooth, provided the vehicle supports it. For older tachographs or fleets without a Bluetooth connection, we build a manual entry flow with validation against the ATW (Dutch Working Hours Act). With the driver's consent, the raw tachograph data can be forwarded to your trip administration or a specialised driving-time analysis package.
And the BCT for taxis?
For contract transport in the Netherlands, the Boordcomputer Taxi (BCT) is mandatory. We build the app in line with the BCT protocol, connecting to the certified BCT cradle in the vehicle. Shift, free ride, occupied ride and break are recorded properly; pay data ends up in your taxi administration or with the SVB. In an ILT inspection (the Dutch transport inspectorate), the readable evidence is immediately available.
Does CMR digital signing work with our customers?
e-CMR has been ratified in a growing group of European countries. For shipments between countries where the protocol is recognised, the sender, carrier and recipient can sign digitally via the app, with an eIDAS-compliant signature and an audit log for customs. For countries that still use paper, we build a hybrid flow: digital signing on the road, a paper printout at border crossings where that is still required.
Which hardware do you recommend?
It depends on your transport. For distribution and parcel couriers, a Zebra TC or Honeywell CT device works well: rugged, scan button, long battery life. For long-haul road transport, a personal smartphone with a sturdy cab mount may be enough, often combined with a ruggedised second screen for navigation. For taxis, the BCT cradle is the deciding factor and we connect the driver app to it. For service engineers, we often see an iPhone or Samsung Galaxy with a professional case.
How do you handle driver privacy?
Driver location is a special category of personal data and is more strictly protected by the GDPR than other data. We record location only during working hours, not during breaks or off duty, with retention periods per data type, and we give drivers insight into what the app stores about them. A DPIA is included as standard for projects involving location tracking, with agreements with the works council or employee representation where applicable.
Which type of carrier is this suited to?
Road hauliers with tractor-trailers or distribution vans, taxi organisations with a BCT obligation, courier services for parcel or food delivery, service companies with mobile engineers, and specialist carriers (temperature-controlled, ADR, heavy haulage, vehicle transport, medical). For the wider context of office-based transport software, see our page on custom transport software.
What determines the cost?
Three main factors: the number of different driver roles and flows in the app (one type of driver in one type of transport is far more limited than a mixed fleet with truckers and service engineers), the depth of TMS and hardware integrations (a single TMS API is much simpler than a combination of BCT, tachograph and BLE sensors), and the compliance layer (domestic road transport is lighter than international e-CMR with AETR and ADR). In the first conversation we give a realistic indication based on your scope.
Fabian van DijkBusiness developer · Appfront

Has worked with haulage companies, taxi organisations and courier services on mobile apps and planning integrations since 2015. Reach him at fabian.vandijk@appfront.nl for a no-obligation introductory chat.

Talk to us about your driver app.

A half-hour introductory chat, no obligation. We listen to your transport flow, dig into what is currently stuck and which integrations are needed — TMS, BCT, tachograph or customer portal — and give you direction you can actually use.

Edit content