On-demand app development: three apps, real-time tracking, payouts and what it all costs

Every on-demand business runs on the same core: three apps and a real-time backend. Here's how dispatch, tracking and payouts work, and how to scope a version that launches.

Ride-hailing, food delivery, home services, laundry pickup, on-demand tutoring: they look like different businesses, but under the hood they share one architecture. On-demand app development is really three apps and a real-time backend: one app for customers, one for the people doing the work, and an admin panel that runs the marketplace. Most budget surprises come from underestimating the second and third.

This guide explains that architecture, how real-time tracking and dispatch work, how money moves from customer to platform to provider, and what drives cost, so you can scope a first version that launches in one market without overbuilding.

The three-app architecture

Some models add a fourth app. Food and grocery delivery usually needs a merchant app or tablet view so restaurants or stores can accept orders and mark them ready.

Dispatch and matching: the heart of the system

Dispatch decides which provider gets which job. It's the piece that most affects customer wait times and provider earnings, so design it deliberately.

• Broadcast: the job goes to every nearby provider, first to accept wins. Simple to build, works at low volume, but rewards whoever has the fastest thumb.
• Sequential offer: the job goes to the best-ranked provider, with a short timeout before moving to the next. Fairer and more controllable; slightly slower.
• Batched assignment: jobs are collected for a few seconds and assigned together to optimize the whole set. Used at higher volume; more complex.
• Scheduled booking: for services booked in advance (cleaning, repairs), matching runs against provider calendars, skills and service areas rather than live location.

For a first version, sequential offers with simple ranking by distance, rating and acceptance rate work well. Build the ranking so operations staff can tune it without a code change.

Real-time tracking without draining batteries or budgets

Live tracking is the feature customers notice most. It involves three parts:

1. Location updates from the provider app, sent every few seconds while on a job and much less often while idle. Background location needs clear permission prompts and justification for Google Play and App Store review.
2. A real-time channel (WebSockets, MQTT or a managed service such as Firebase) pushing positions to the customer app and the admin map.
3. Maps, routing and ETAs from Google Maps Platform, Mapbox or similar.

Maps can become a large line item at scale. Google Maps Platform changed its pricing on March 1, 2025, replacing the old $200 monthly credit with free monthly usage thresholds for each service, and moving the older Directions and Distance Matrix APIs to legacy status in favor of the Routes API. Estimate your calls per order (geocoding, route, ETA refreshes) and multiply by expected orders before choosing a provider. Caching routes and throttling ETA refreshes can cut the bill substantially.

Payments and payouts

On-demand apps collect money from customers, keep a commission and pay providers. That makes you a marketplace in payments terms, with obligations to match.

• Collecting payment: cards, Apple Pay, Google Pay and local methods. Authorize at booking, capture on completion, so cancellations and price changes are clean.
• Splitting and paying out: Stripe Connect's marketplace model is a common pattern in the US: the platform collects the payment, keeps an application fee and pays the rest out to providers' connected accounts, with Stripe handling provider identity checks. Stripe's own documentation notes that the platform is responsible for covering connected accounts' negative balances, so refunds and disputes need a policy. In India, gateways such as Razorpay and Cashfree offer split-settlement products.
• Tips, surge pricing and promotions all touch the payout logic. Design them in the ledger from day one, even if you launch without them.
• Cash payments, common in India and the UAE, need provider wallets that track cash collected against commission owed.

App store rules work in your favor here. Apple's guidelines 3.1.3(d) and 3.1.3(e) allow payment methods other than in-app purchase for services consumed outside the app and for real-time person-to-person services, so on-demand services generally don't pay Apple's commission. Digital add-ons sold inside the app follow different rules.

Tax and worker classification (for example 1099 reporting for US contractors, or GST in India) depend on your structure and location. Get local advice; this guide isn't legal or tax advice.

Trust and safety features you can't skip

• Provider verification: ID, licences, vehicle documents and, where relevant, background checks through a compliant provider.
• Number masking for calls and chat, so neither side sees the other's personal number.
• Two-way ratings, with low-rated providers flagged for review.
• In-app SOS or emergency contact for ride and home-visit services.
• OTP or PIN at pickup or job start to confirm the right person.
• Audit logs of every status change, for disputes and support.

What drives on-demand app development cost

As a typical range from an offshore team, a focused first version (customer app, provider app and admin panel, one city, one service type) often lands in the mid five figures, while a multi-service, multi-city platform runs well into six figures. Our app development cost guide covers the general drivers, and how long it takes to build an app covers timelines.

Scope a first version that can launch

Successful on-demand businesses usually start narrow: one service, one city, a limited set of vetted providers. A practical first version:

• One service type with fixed or simple distance-based pricing.
• Card and wallet payments with weekly provider payouts.
• Sequential dispatch with distance and rating ranking.
• Live tracking for active jobs only.
• An admin panel focused on approvals, live jobs, refunds and support.

Leave surge pricing, multi-stop orders, subscriptions and loyalty for after you've proven unit economics. Our guide to MVP app development for startups goes deeper on what to cut, and you'll need a plan for both sides of the marketplace at launch, since providers without customers leave, and customers without providers don't come back.

Launch sequencing for a two-sided marketplace

1. Recruit supply first. Onboard and vet enough providers to cover your launch zone at peak hours before you spend on customers.
2. Soft launch in a small area with friends, local communities or a single partner business, and watch wait times, cancellations and completion rates daily.
3. Open demand gradually. Increase customer marketing only as fast as provider coverage allows. Long waits in the first weeks do lasting damage to ratings and word of mouth.
4. Track unit economics per order from the start: commission, payment fees, maps cost, promotions and support time.

Building your on-demand platform with Appryze

Appryze builds customer and provider apps in Flutter or native Swift and Kotlin, plus the web admin panel and backend, for clients in the USA, UK, UAE and India. You get a fixed-price written quote within 24 hours, free App Store and Google Play submission, and one month of launch marketing to start acquiring customers in your first market. See our Studio page for how projects run, or Growth for launch marketing.

Frequently asked questions

How much does it cost to develop an on-demand app?

As a typical range from an offshore team, a focused first version with a customer app, provider app and admin panel for one service in one city often lands in the mid five figures. Multi-service, multi-city platforms with surge pricing, wallets and several provider types usually run well into six figures. Instant dispatch, payments complexity and the number of markets are the biggest cost drivers.

What apps do I need for an on-demand service business?

Usually three: a customer app for booking, paying and tracking; a provider app for drivers or service professionals to accept jobs, navigate and see earnings; and a web admin panel for your operations team to approve providers, manage jobs, handle refunds and run reports. Food and grocery delivery often adds a merchant app for restaurants or stores.

How do on-demand apps pay service providers?

Typically the platform collects the customer's payment, keeps a commission and pays the rest to the provider. In the US, Stripe Connect is a common way to do this, with providers onboarded as connected accounts and paid out on a schedule. In India, gateways such as Razorpay and Cashfree offer split settlements. Cash jobs need wallet tracking of commission owed.

Do on-demand apps have to use Apple in-app purchase?

Generally no. Apple's App Store guidelines say apps selling physical goods or services consumed outside the app must use payment methods other than in-app purchase, and real-time one-to-one services may use other methods too. So rides, deliveries and home services typically use cards or wallets. Digital content or subscriptions consumed inside the app follow different rules.

How long does it take to build an on-demand app?

A focused first version with customer and provider apps, an admin panel, payments and live tracking typically takes about three to six months, depending on scope and team size. Scheduled-booking services are faster to build than instant dispatch. Store review, provider onboarding and testing in your launch city should be planned into the timeline.

Keep reading

More in On-Demand App Development · All app development guides