Build guide
Building an on-demand laundry app from scratch
In short
An on-demand laundry app is a customer app for booking, scheduling and tracking, plus a back end the operations team uses to run pickups and deliveries. The hard part is retention, because push notifications drive repeat orders. A first release takes roughly 8-14 weeks.
Who this is for
Founders starting a laundry, dry-cleaning or similar pickup-and-delivery service who want to know what the first app must include.
What the product has to do
- Customer appSign up, addresses, booking and order history.
- Booking and schedulingPickup and delivery slots, with capacity limits.
- Order trackingStatus from pickup to delivery, updated live.
- Service catalog and pricingItems, services and prices the customer can choose from.
- Back-office and operationsStaff see orders, assign pickups and change status.
- Push notificationsStatus updates and reminders to reorder.
- PaymentsCard or cash handling and receipts.
- Support and messagingA simple way to ask about an order.
The stack, and why
| Layer | Choice | Why |
|---|---|---|
| Customer app | Flutter and Dart | One codebase for both stores. |
| Back end | Laravel with PHP | Quick to build order, customer and admin features with a mature ecosystem. |
| Live order updates | Firebase | Real-time order status without building the plumbing. Today I would still pick it for a small launch. |
| Messaging and push | Firebase | Status updates and reorder reminders were a real ordering channel for this product. Add queue workers early if your own back end sends them. |
What ships first, and what waits
Version one
- Sign-up and address book
- Booking with pickup and delivery slots
- Order status tracking
- Push notifications for status changes
- Back-office to manage orders
Later
- Subscriptions or bundles
- Loyalty and referral offers
- Reorder reminders by push
- Courier app for pickups
- Promo codes
Build order and timeline
- 1-2 weeksService designServices, slots, pricing and order states.
- 3-5 weeksBack end and back-officeOrders, schedules and an admin to run them.
- 3-5 weeksCustomer appBooking, tracking and push in the app.
- 1-3 weeksPilot and store releaseLive pilot in a small area and published apps.
Want a number for your own scope? The app cost calculator turns platforms and features into an estimate.
Rules you cannot skip
- Payment method for physical services
Google Play says payments for real-world services such as cleaning should not use Google Play billing.
Official source - Payment method on iOS
Apple requires apps that sell physical goods or services consumed outside the app to use other payment methods, such as cards.
Official source - Push notifications
Apple says apps must not require push to function, and that promotions or direct marketing by push need explicit opt-in with a way to opt out.
Official source - Account deletion
If your iOS app lets people create an account, it must let them delete it from inside the app.
Official source
Where these projects go wrong
- Ignoring retention
Repeat orders matter as much as new customers. On Spotless Laundry a well-tuned push strategy proved to be a real ordering channel.
- Over-notifying
Too many pushes cause opt-outs and uninstalls, and marketing pushes need consent on iOS.
- Slots without capacity limits
If bookings exceed what your drivers and staff can handle, service quality collapses. Limit slots from the start.
- Order state confusion
Unclear order statuses create support calls. Define a small set of states and show each one plainly.
- Operations tools forgotten
The customer app gets attention, but staff need a fast back-office to run daily pickups.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
Problems you will meet on this stack
Response status code: 401My Flutter request returns 401 Unauthorized, but the same call works in PostmanTarget of URI doesn't exist: 'firebase_options.dart'.firebase_options.dart does not exist in a Flutter projectUndefined class 'FirebaseUser'.FirebaseUser no longer exists in firebase_authCould not find com.google.firebase:firebase-analytics-ktx:.Gradle cannot find com.google.firebase:firebase-analytics-ktxThe method 'play' isn't defined for the type 'AudioCache'.AudioCache has no play method after updating audioplayersemit was called after an event handler completed normally.Flutter Bloc throws that emit was called after the event handler completed