Skip to content
DT Nova
Services

Taxi app development company for rider, driver and dispatch apps

DT Nova is a taxi app development company for taxi firms, cooperatives, private hire operators and transport services that want their own booking and dispatch system instead of renting a place on someone else's marketplace. We build the rider app, the driver app, the dispatch console and the fleet admin as one system, set up for your city's fares, licences and payment rules, and your company owns the code.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

Who we build taxi apps for

Our taxi work is for companies that already run vehicles and drivers and need better software: taxi companies and driver cooperatives with a dispatch centre, private hire and chauffeur operators, airport and hotel transfer services, accessible transport and patient transport providers, and municipalities or operators running demand-responsive public transport. The common thread is a business that pays a commission to a ride-hailing platform for customers it could book directly, or that runs dispatch on an old system that drivers and customers no longer like to use.

What we build

Dispatch and fares, set to your rules

The heart of a taxi system is the matching: which car gets which trip. The simplest rule is the nearest free car by straight line, and it is usually wrong, because a car across a river or a one-way system is not near. We match on driving time from live map data, and then apply your rules: queue order at taxi ranks, zones, driver shifts, vehicle type, pre-booked trips that must be protected, and fairness between drivers if that is how your cooperative works. Dispatchers can always override.

Fares follow your licence and local law. Some cities require a certified taximeter for every trip, some allow a fixed upfront price for app bookings, and many have maximum tariffs set by the authority. The system supports metered, fixed, zone-based and upfront fares, with the rules for each city kept as settings your staff can read.

The rules that shape a taxi app

Taxi regulation in Europe is national and often local. The European Commission's Notice on well-functioning and sustainable local passenger transport-on-demand, published on 2 February 2022, guides national and local authorities on how internal market rules apply to taxis and private hire vehicles, but the licences, tariffs and vehicle rules remain theirs. A few EU rules shape the software everywhere (all sources read on 11 November 2026):

We do not give legal advice. Your legal advisers decide what applies to your business; we turn their conclusions into rules the system enforces.

Payments and the app stores

A taxi ride is a service consumed outside the app, so both stores require you to take payment outside their in-app purchase systems. Apple's guideline 3.1.3(e) says apps that sell physical goods or services consumed outside the app must use other purchase methods, such as Apple Pay or card entry, and Google Play's payments policy names transportation services among the cases where its billing system must not be used. In practice, card payments, Apple Pay and Google Pay run through a payment provider you choose, with cards stored as tokens, tips, pre-authorisation for the estimated fare and split settlement to drivers where they are independent.

Location is the other store topic. Apple's guideline 5.1.5 allows location services only where they are directly relevant to the app's features, with the user's consent. Google Play requires a declaration, a video demonstration and a prominent in-app disclosure before an app may access location in the background. Driver apps need background location for live tracking during a shift; rider apps usually do not, and asking for it is a common reason for rejection.

Integrations a taxi system needs

White-label taxi software or your own?

White-label taxi apps exist, and for a small fleet that needs an app next month, one of them can be the right start. The trade-offs show as you grow: a fee per trip or per car, the vendor's dispatch logic rather than yours, your brand next to theirs in the stores, and your customer and trip data in their platform. A custom system costs more to start and less to run as volume grows, follows your rules, and is yours to change. We say which fits your case in the first reply to your brief.

How we build it

  1. Rules and flows workshop. Dispatchers, drivers and managers show how trips are booked, matched and paid today, including the unwritten rules.
  2. Scope and fixed price in writing. Apps, cities, fares, integrations and what the first phase leaves out.
  3. Driver app and console first. Tested with a few of your drivers on real trips, while the old system still runs.
  4. Rider app and business accounts. Released through TestFlight and Google Play testing to your regular customers before the public launch.
  5. Launch, measure, extend. Booking share through your own app, time to pick-up and cancellations, tracked from the first week.

You own it

As a standard term, the source code is in a repository in your company's own account, and the store listings, cloud hosting, maps and payment accounts are in your company's name. Hosting runs in an EU region. You can keep us for maintenance, take it in-house or hand it to another team. For food and parcel delivery with couriers, read our guide to food delivery app development; for other services booked now or later, see on-demand app development. For freight and logistics, see logistics software development. For the build in general, see app development and cross-platform apps. See prices.

Questions we get

Do we need a rider app, a driver app and a dispatch system?

Usually all three, plus an admin view. Riders book and pay, drivers receive and complete trips, and dispatchers or the system match the two and handle the exceptions. A taxi company with its own dispatch centre may start with the driver app and the console, and add the rider app second.

Can the app use our existing taximeters and payment terminals?

Often, yes. Many fleets already have certified meters and card terminals in the cars. The driver app can read trip data from them where the supplier offers an interface, or the fare can be calculated in the app where your local rules allow a fixed or upfront price.

Can riders pay in the app without Apple or Google taking a commission?

Yes. A taxi ride is a service used outside the app, so both stores require you to use a payment method other than their in-app purchase, such as card payment through a payment provider, Apple Pay or Google Pay. The provider's fees apply, not the store's commission.

Does the EU Platform Work Directive apply to us?

It applies to digital labour platforms that organise work done by individuals through an app. If your drivers are your employees, much of it is already covered by employment law; if they are independent, it matters a lot. Your legal advisers decide; we build the transparency, human review and data limits it requires into the app.

Can we launch in one city first?

Yes, and we recommend it. Fares, zones, licensing and payment rules are local. The system is built so that a new city is a set of settings and rules, not a new app.

Who owns the apps and the data?

Your company. The source code is in your own repository, the store listings and the cloud account are in your company's name, and trip and customer data is hosted in the EU under your control.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote