What drives the price
A full taxi service with rider and driver apps, a live map with real-time tracking and offline mode is the Advanced level, which is where the price on this page starts. If a fleet already runs its own dispatch and needs only a driver app, the entry MVP level is enough: 8–12 screens and one role; Standard adds a user account, payments, chat and an admin panel. All level ranges are in the table above. Fare calculation, a dispatch console and automatic assignment of bookings to drivers are not in the standard price list: every service has its own rules, so we describe them in the specification and price them separately. Face ID sign-in, trip-status widgets and crash monitoring can be added to any level. The configurator gives the total, and the contract fixes it.
Two sides of the service: rider and driver
The rider needs little: enter an address, see which car is coming and when, pay the usual way and message support if something goes wrong. The driver needs to receive a booking, get a route and switch statuses with one tap without distraction. The driver app runs on budget Android phones and is careful with the battery while it streams location. On a weak signal, offline mode keeps trip data and sends it when the network returns. Both sides are multilingual; in Uzbekistan that means Uzbek and Russian. We choose the map provider by address accuracy in your city and by the cost of its API calls, which becomes a noticeable expense at high trip volumes.
Payments, stores, and your own app versus an aggregator
A ride is a real-world service, so Apple and Google rules allow payment through local providers inside the app; in Uzbekistan that means Payme and Click, with cash to the driver as an option. A trip counts as paid only once the provider confirms it on the server. Developer accounts are registered to your company; Apple requires your company’s D-U-N-S number, which we request in the first weeks. Your own app gives the service its brand, its own rider base and its own rules for drivers. It also has a cost: development, servers and support. If booking volume is still low, joining an aggregator may make more sense, and we will say so at the first meeting.
How the work runs and what the contract says
We start with discovery: how bookings are taken today, how the service prices a trip, how it assigns and pays drivers. That becomes a specification covering the rules that are not in the standard price list. Then flows, a clickable prototype and development in two-week cycles: at the end of each you install test builds of the rider and driver apps on your phones and run trial trips. The timeline from 32 weeks is in the contract: every day of delay cuts the invoice by 2%, up to 10% of the contract in total. Bugs are fixed free with no time limit, and your engineer may audit the code against the contract: any unfulfilled item means a 10% refund.