On-demand app development

An on demand app development company that builds both sides of your marketplace

We build the customer app, the provider app and the admin panel as one booking system, fix the price of the first milestone in writing, and put the code and the payment accounts in your name.

Get a written scope for your on-demand app
Trusted by the world's fastest-growing brands

What an on-demand app is

Three apps that work as one booking

An on demand app development company builds software that connects people who want a service now with providers who can deliver it: one app for customers, one for providers and an admin panel for you. A booking has to move through all three without a person in the middle, and the money has to follow it.

Booking 1042Paid $120.00RequestedOfferedAcceptedOn the wayIn progressCompleteCustomer appLive map is openProvider appNavigate to the jobAdmin panelState: On the way

One booking, three screens

A request in the customer app becomes an offer in the provider app and a line in the admin panel. We design the booking states first, so the three screens agree on where a job stands.

Money in the right order

The customer pays at booking, and the provider’s share moves when the job completes. We build the split, the refund and the payout rules on Stripe, in your Stripe account.

Location only where it earns its place

The customer sees the provider on a map during an active job. Location is requested with a stated reason and switched off when the job ends, which is what the app stores look for.

Two ways to a marketplace app

A purpose-built app or a ready-made marketplace platform

Both put a working marketplace on a phone. They differ in what you can change once real customers use it.

Ready-made platformA licensed or white-label basePurpose-built appWritten scope and price
Booking rulesSet by the platform, with changes limited to its settingsDesigned around your service: windows, quotes, cancellations, minimums
Time to a first launchShorter, because the base already existsLonger, because the booking flow is built for your service
Payments and payoutsSupplied by the platform, with its fees and payout scheduleBuilt on Stripe in your own platform account, with your fee and payout rules
Code and accountsSet by the license; ask whether you receive the sourceRepository, hosting and store accounts in your name from the first commit
Best whenYour service fits a standard flow and speed matters mostYour service has its own rules, or the booking flow is the business
What goes in the first version

Our first version is small on purpose: one service, one metro, a human dispatcher for the first jobs, and the automatic matching written down for later.

Building a marketplace app in 2026

Six rules that shape an on-demand app

What Apple, Google and Stripe each say about payments, location and payouts. Sources under each.

  1. Apple paymentsApp Store

    Services consumed outside the app are paid for by methods other than in-app purchase.

    Guideline 3.1.3(e) puts physical goods and services consumed outside the app on a different footing: they are paid for by methods other than in-app purchase, such as Apple Pay or card entry. A booked cleaning or a delivery fits that description, and we check each service against the guideline in the scope.

  2. Apple locationApp Store

    Apple expects location to be relevant to the feature and requested with consent.

    Guideline 5.1.5 says to use Location Services only when directly relevant to the app’s features, to notify people and obtain consent before collecting location, and to explain the purpose in the app. For an on-demand app, the live map during a job is that feature.

  3. Apple background useApp Store

    Location is one of the background services Apple lets an app use for its intended purpose.

    Guideline 2.5.4 lists location among the intended purposes for background services, next to VoIP, audio playback and task completion. A provider’s phone keeps sharing position while the screen is locked on the way to a job, and the purpose has to match what the app says.

  4. Google locationGoogle Play

    Google Play requires approval to read location in the background.

    Google’s policy says background location may only be used when it provides a significant benefit and is relevant to the app’s core functionality, and apps that use it must be approved through the permission declaration process. Without approval, updates can be blocked or removed.

  5. Splitting a paymentStripe

    Stripe’s separate charges and transfers split one payment between several parties.

    Stripe describes it as a charge on the platform’s account with transfers to connected accounts, and names a delivery platform that pays a restaurant and a courier as an example. The platform balance is debited for Stripe fees, refunds and chargebacks, which shapes the refund rules we write.

  6. Provider payoutsStripe

    By default, Stripe pays connected accounts out on a daily rolling basis.

    Charges accumulate in the connected account’s balance and are paid out daily on a rolling basis by default. Depending on the setup, a platform can change the schedule, pay out manually or hold funds in its own balance, so the payout rule is a decision made in the scope.

What we build

Six parts of an on-demand app, and what each produces

Each part is built and tested on its own, then together as one booking.

9:413-hour home cleanCharlotte, NCWhenSat 10 a.m. to 1 p.m.Total$120.00PayOr pay by card

Customer app

The app a customer uses to find a service, choose a time, pay by card or Apple Pay, follow the provider and rate the visit, for iPhone and Android. You receive: the app, the screen flow and the store listing draft.

RequestTrackPay
Provider appOnlineNew job offer$102.00$120.00 job, less the 15% fee0:383-hour cleanSat 10 a.m. to 1 p.m.DeclineAccept

Provider app

The app a provider uses to set availability, see offers, accept or decline a job, navigate to it and mark it complete, with a clear view of earnings. You receive: the app, the onboarding flow for new providers and the test results.

Offer queueBooking 1042Provider 07Flagged for dispatchNo answerProvider 12Expires in 0:38OfferedProvider 31Dispatcher offers nextNextDispatcher overrideAssign by hand

Booking and dispatch

The rules that turn a request into a job: windows, minimums, offers your dispatcher sends to a provider, a timer that flags an offer nobody has answered, and a manual override to reassign the job. You receive: the state diagram of a booking and the dispatch rules in writing.

Arrives in12 minLocation sharingOn during a job only

Live location

A map that shows the provider’s approach during an active job, with location requested for a stated reason and switched off when the job ends. You receive: the permission copy, the platform settings for iPhone and Android and the battery test notes.

Payment splitPaid at booking3-hour clean$120.00Platform fee · 15%$18.00Provider transfer · 85%$102.00Cancel before acceptRefund $120.00After the jobDaily by default

Payments and payouts

Customer payment at booking, your fee, the provider’s share, refunds, cancellations and payout timing, built on Stripe in your own platform account. You receive: the payment rules, the test cases and the Stripe configuration notes.

JobsFee: 15%JobWindowState1042Sat 10 a.m.On the way1043Sat 1 p.m.Offered1044Sun 9 a.m.RequestedJob 1042Refund $120.00Pause provider

Admin panel

A web panel for you and your staff to approve providers, see each job and its state, issue refunds, change the fee and pause a provider. You receive: the panel, the permission levels and a runbook for the common tasks.

How it runs

Scope, design, build, hand over

You approve each stage, from the scope to the release.

version-one-scope.csv

Version one scope

Sample · Sample Doorstep home-services marketplace, Charlotte, NC
FeatureDecisionReason
Customer books a visit by address, date and windowInThe first assumption: people will book in an app
Provider accepts or declines a jobInThe provider side is the other half of the test
Card payment at booking, payout after the jobInBoth sides must trust the money
Live map once the provider is on the wayInCustomers ask where the provider is
Automatic matching to the nearest providerLaterA dispatcher can offer jobs for 40 providers
Recurring weekly visitsLaterBook by hand until customers ask
Pricing follows the In rows. Launch area: 4 ZIP codes.

Our stack

The tools behind your marketplace

What the three apps are designed, built, paid through and monitored with. Pick one for the detail.

Figma
Why Figma

Figma is the design tool where the customer, provider and admin screens are drawn and linked into prototypes.

How we use it

Customers and providers you name tap through both prototypes before any code exists, so a change to the booking flow costs a redraw.

Real-timeDev handoffTokens
FigmaYes
SketchSome
Static mockupsNo

Questions

On demand app development, answered

Start here

Get a written scope for your on-demand app

Tell us what people will book. We’ll send back the feature list for all three apps, the timeline and the price.