No record of condition
Nobody could prove what state a device was in at pickup.
Delivery and courier app development
Delivery apps where every parcel leaves evidence.
Customer booking, rider dispatch, live tracking and cash-on-delivery that reconciles against the platform's own ledger. Built from D. Delivery, our three-app Kotlin Multiplatform courier platform, whose customer app is live on Google Play.
The real problem
Courier disputes are won by whoever has evidence.
In D. Delivery the goods were phones, laptops and electronics, where one disputed parcel can cost more than a month of delivery revenue. Bookings ran on WhatsApp, cash was reconciled by hand, and riders were assigned by whoever answered first.
Cash that never matched
Cash on delivery was reconciled by hand at the end of the day.
Dispatch by phone
The first rider to answer got the job, not the nearest one.
Customers calling for status
There was nothing for them to look at.
What we build
Three apps, one source of truth.
Customer app
Booking with address search, insurance based on declared value, live tracking with a traffic-aware ETA, receipt and rating.
Rider app
Job alerts, guided pickup and drop-off, dual video proof, recipient e-signature, wallet and earnings, offline-first sync.
Admin control tower
Manual dispatch, rider approval and documents, pricing, dispute flags and end-of-day cash settlement against the ledger.
Expanding-radius dispatch
New orders search a small radius first and widen step by step until a rider accepts, with the admin alerted if nobody does.
Evidence pipeline
Videos and signatures are compressed on the phone and stored per order; uploads queue in the background on weak signal.
Money on the record
Cash on delivery is settled against the platform's own ledger, not the rider's word.
Built before
The delivery platform we shipped.
Logistics platform
Read the case study
D. Delivery
Three apps from one Kotlin Multiplatform codebase, built around verifiable proof of delivery.
Google Play
Open Google Play
D. on Google Play
Install the customer app and try the booking flow yourself.
Kotlin Multiplatform
See the service
Why one codebase
How sharing the rules keeps pricing and order states identical across the apps.
Product Clarity Sprint: from $1,500
One to two weeks. The workflow map, feature priorities, technical direction and a fixed quote for the build. You own the output whether or not we build it.
First release: $12,000 to $18,000
8 to 12 weeks for a focused feature set, paid against milestones.
Operational platform: $20,000 to $35,000
12 to 16 weeks for multi-role systems with dispatch, approvals, live tracking or payments, shipped in focused releases.
You own the code
On final payment you own the source code, repositories, store listings and backend accounts. No lock-in.
FAQ
Questions people ask first.
Do you build the rider app and the admin panel too?
Yes. A delivery business needs three products: a customer booking app, a rider job app and an admin control tower. In D. Delivery all three share one Kotlin codebase and one database.
How does proof of delivery work?
The rider records a video at pickup and at drop-off, and the recipient signs on the phone. The evidence is compressed on the device and stored under the order, so it holds up in a dispute.
Can riders keep working on a weak signal?
Yes. Uploads are queued by a background worker, so a rider is never blocked from finishing a job by the network.
What does a delivery app cost?
A multi-app delivery platform sits in the $20,000 to $35,000 range over 12 to 16 weeks. A focused first release is $12,000 to $18,000. Most projects start with a $1,500 Clarity Sprint that ends in a fixed quote.
Start the conversation
Running deliveries on WhatsApp and a ledger?
Twenty minutes is enough to map the booking, dispatch and proof flow your business needs.