Contents
Mobility app development means connecting people with vehicles, timetables and tickets – and the app has to work within seconds, often on the move and under time pressure. Whether it is a sharing service, ticketing for a transport operator or multimodal navigation, the technical requirements differ considerably. This article shows what matters for each type, which building blocks you need and what costs to expect.
Three types of mobility apps
The term mobility app covers very different products. How you classify yours determines architecture, budget and risks:
| Type | Examples | Core challenge |
|---|---|---|
| Sharing app | E-bikes, e-scooters, car sharing, cargo bikes, corporate fleets | Unlocking vehicles reliably via app, booking and billing |
| Ticketing app | Transit authorities, car parks, ferries, shuttle services | Secure, verifiable tickets, fare logic, payments |
| Navigation and information app | Multimodal journey planning, commuter apps, campus or plant transport | Data quality, real-time information, routing across modes |
Many projects combine elements, for example an employee mobility app with bike leasing bookings, a shuttle timetable and parking reservations. Even so, version 1 should put one type clearly at the centre.
Sharing apps: when the app becomes the key
In sharing services, the app is not just a booking interface – it is the key to the vehicle. That places high demands on reliability:
- Unlocking via mobile network and Bluetooth: the vehicle’s telematics unit is usually addressed via the backend. A Bluetooth fallback helps in underground car parks without reception.
- Condition records: photos before and after the trip reduce disputes about damage.
- Verification: car sharing requires a driving licence check, often via specialised identity verification providers.
- Payment handling: pre-authorisation at the start, billing by the minute or kilometre at the end, and handling of failed payments.
- Geofencing: maintaining no-parking zones, the operating area and speed zones in the backend and showing them in the app.
- Operator tools: a service app for battery swaps, redistribution and repairs is often as important as the customer app.
Telematics integration is usually the largest single cost item. Clarify early which hardware will be used and whether the manufacturer provides a documented API.
Ticketing apps: fares, inspection and payment
In ticketing, the challenges lie in the details. Public transport fare systems have grown over time and contain zones, concessions, season tickets and special rules. This logic belongs in the backend, not the app, so that fare changes are possible without an app update.
Key building blocks are:
- Fare information and purchase flow with as few steps as possible to a valid ticket.
- Tamper-proof tickets, for example with signed barcodes and dynamic elements that make screenshots harder to misuse.
- Inspection app for staff that can verify tickets offline.
- Payment methods such as cards, wallets and direct debit, plus contract management for subscriptions. More on this in our article on payment features in apps.
- Integration with sales and back-office systems of the operator or transit authority.
A ticket must be presentable even with no data allowance left or a weak signal. Purchased tickets should therefore be stored locally and securely on the device.
Navigation and passenger information
For information and navigation apps, data quality is the most important success factor. Public transport timetables are often published in the standardised GTFS format, with real-time data in complementary formats. Sharing services and road networks add further sources. The app has to merge this data, resolve contradictions and communicate honestly when things go wrong – nothing annoys passengers more than a connection that was cancelled long ago.
Decide whether to run routing yourself or use a specialised service. Your own routing engine based on open-source software is possible but requires operational know-how. With high user numbers, for instance at rush hour or during major events, the backend must absorb load peaks; see our article on app scalability.
Location data and privacy
Mobility apps process movement data from which home, workplace and habits can be inferred. Privacy is therefore a central quality feature:
- Collect location only while the feature needs it – not permanently in the background without a clear reason.
- Delete or anonymise trip histories after defined periods.
- Run analyses on aggregated data wherever possible.
- Use tracking and analytics SDKs only with valid consent.
- Host and process data in the EU with clear data processing agreements.
Our GDPR checklist for apps offers a structured overview. For a legal assessment of your specific project, please consult specialists – this article is not legal advice.
Costs of a mobility app
| Scope | Example | Guide price | Duration |
|---|---|---|---|
| MVP | Booking app for a corporate fleet without telematics, key handover on site | €5,000–15,000 | 4–8 weeks |
| Mid complexity | Ticketing for a shuttle service with login, payment and inspection app | €15,000–50,000 | 2–4 months |
| Platform | Sharing with telematics, verification, operator app, geofencing, billing | from €50,000 | from 4 months |
On top of development come running costs for hosting, payment providers, map services and, where needed, identity checks. AI-assisted development can reduce development effort by up to 40 %, for example in fare and billing logic, tests and admin interfaces. For a fixed-price offer after a free analysis, use our offer wizard.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
A mobility app has to work at the decisive moment: unlocking the vehicle, showing a ticket to an inspector or changing trains. Define the focus of version 1 clearly, invest in robust offline and fallback mechanisms, and treat location data with particular care. The background processes – telematics, fares, billing and operator tools – determine success at least as much as the user interface.
Frequently Asked Questions
How much does it cost to develop a sharing app?
A sharing app with telematics integration, verification and billing is usually a platform starting at around €50,000. Simpler booking apps without vehicle unlocking are possible as an MVP from €5,000–15,000.
How does unlocking a vehicle via app work?
After a successful booking, the backend typically sends a command to a telematics unit in the vehicle. A Bluetooth fallback ensures unlocking also works without mobile reception.
Where does a navigation app get timetable data?
Many transport operators publish timetable data in the standardised GTFS format, sometimes complemented by real-time feeds. Check availability and licence terms before the project starts.
Does a digital ticket have to work offline?
Yes. Purchased tickets should be stored securely on the device so they can be shown and checked by an inspection app without a connection.