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.
On-demand app development
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 appWhat an on-demand app is
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.
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.
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.
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
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 base | Purpose-built appWritten scope and price | |
|---|---|---|
| Booking rules | Set by the platform, with changes limited to its settings | Designed around your service: windows, quotes, cancellations, minimums |
| Time to a first launch | Shorter, because the base already exists | Longer, because the booking flow is built for your service |
| Payments and payouts | Supplied by the platform, with its fees and payout schedule | Built on Stripe in your own platform account, with your fee and payout rules |
| Code and accounts | Set by the license; ask whether you receive the source | Repository, hosting and store accounts in your name from the first commit |
| Best when | Your service fits a standard flow and speed matters most | Your service has its own rules, or the booking flow is the business |
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
What Apple, Google and Stripe each say about payments, location and payouts. Sources under each.
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.
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.
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.
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.
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.
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
Each part is built and tested on its own, then together as one booking.
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.
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.
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.
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.
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.
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
You approve each stage, from the scope to the release.
Version one scope
| Feature | Decision | Reason |
|---|---|---|
| Customer books a visit by address, date and window | In | The first assumption: people will book in an app |
| Provider accepts or declines a job | In | The provider side is the other half of the test |
| Card payment at booking, payout after the job | In | Both sides must trust the money |
| Live map once the provider is on the way | In | Customers ask where the provider is |
| Automatic matching to the nearest provider | Later | A dispatcher can offer jobs for 40 providers |
| Recurring weekly visits | Later | Book by hand until customers ask |
Our stack
What the three apps are designed, built, paid through and monitored with. Pick one for the detail.
Figma is the design tool where the customer, provider and admin screens are drawn and linked into prototypes.
Customers and providers you name tap through both prototypes before any code exists, so a change to the booking flow costs a redraw.
Questions
Keep exploring
Business software built around how you work, in your own repository.
Swift and SwiftUI iPhone apps, built in your own Apple Developer account.
Kotlin and Jetpack Compose apps, published from your own Google Play account.
Engineers on your product, working in your GitHub, Jira and Slack.
A remote team building in your repository, with the code in your name.
A first version at a fixed price, with a list of what to cut.
Portals, dashboards and SaaS-style tools that run in the browser.
Software for larger organizations, built around the systems already in place.
One TypeScript codebase for iPhone and Android, in your own store and Expo accounts.
Start here
Tell us what people will book. We’ll send back the feature list for all three apps, the timeline and the price.