How a Mobile App for Cleaning Solves the Scheduling Problem
Developing a mobile app for a cleaning service cuts order scheduling time from hours to seconds. In a typical service, cleaning is arranged via phone or messenger: the operator confirms the time, logs it in Excel, then confirms with the client. The process takes 10 minutes to an hour. If the client doesn't get through, they leave. Automation with a mobile app fixes this: the client sees free slots, picks one, pays — and the order enters the system. The cleaner gets a push notification. Everything takes less than a minute. Our team has implemented this scheme in dozens of projects. Result: 80% time savings for the client and 40% reduction in operator costs. Average client savings with recurring orders are 1500–3000 rubles per month.
Why a Single App with Three Roles Is a Necessity
The optimal architecture is one Flutter app with client, cleaner, and admin roles. The role is determined at login, and the UI switches completely. This is cheaper and easier to maintain than three separate apps.
| Role | Key Features |
|---|---|
| Client | Service selection, online calculation (area, extra services, urgency), payment, history, reviews |
| Cleaner | Schedule, navigation via Yandex MapKit, checklist, photo report with GPS tag, arrival status |
| Admin | Assignment, real-time map, tariff management, statistics |
How We Implement Dynamic Price Calculation
The cleaning cost is a function of type (standard, deep, post-renovation), area, extra services (fridge cleaning, windows), and urgency. The order form shows the total in real time when any parameter changes. On the backend — a tariff table with base rates and coefficients. The admin changes prices in the panel — no hardcoding. For example, an urgent order multiplies the base price by 1.5, and window washing adds 25%. In practice, a standard cleaning of a 60 m² apartment with window washing costs the client 2500–3500 rubles. Example calculation code:
double calculatePrice(ServiceType type, double area, List<Extra> extras, bool urgent) { double base = _basePrices[type] ?? 1000; double areaCoeff = area > 100 ? 1.2 : 1.0; double extrasCoeff = extras.fold(0.0, (sum, e) => sum + e.coefficient); double urgencyCoeff = urgent ? 1.5 : 1.0; return base * areaCoeff * (1 + extrasCoeff) * urgencyCoeff; } The database is PostgreSQL with PostGIS for geo-search. Queries execute in <50 ms.
Automatic vs Manual Assignment: Selection Criteria
Two modes:
-
Automatic: algorithm finds an available cleaner in the object's zone (PostGIS, geofences), with rating >4.0, no schedule conflicts. Assigns → push to cleaner → accept or decline. Assignment time — 2-5 seconds. In 95% of cases, automatic cleaner assignment is used, reducing client churn by 25%. This is 50 times faster than manual assignment.
-
Manual: dispatcher sees a list of free cleaners for the desired slot and assigns manually. Used for non-standard orders (very large, special equipment). Time — 1-5 minutes.
| Parameter | Auto | Manual |
|---|---|---|
| Assignment time | 2-5 seconds | 1-5 minutes |
| Dispatcher load | Minimal | Full occupation |
| Flexibility | Low (rules only) | High |
How Photo Reports with Geo-Tags Reduce Disputes
Cleaners photograph the object before and after cleaning through the app's camera. Each photo is tied to the task with a timestamp and GPS coordinates. The client sees the photo report and confirms completion or files a complaint. Practice shows: disputed situations decrease 5-fold because there is documented proof. According to App Store Review Guidelines 5.1, the app must request camera access — we include this at the design stage.
How Recurring Cleaning Orders and Push Notifications Work
Recurring cleaning orders: "cleaning every two weeks on Fridays" — the task automatically creates new requests on schedule. Payment is charged from the linked card via YooKassa recurring or manual payment. A notification arrives 2 days before — can be rescheduled or skipped. Repeat orders increase by 40% after implementing the recurring model. Push notifications (FCM) are used for: new order notification, 24-hour reminder, status change, payment confirmation, message from client. Push delivery delay does not exceed 5 seconds.
What Is Included in the Work
- Mobile app for iOS and Android (Flutter 3.x with Bloc)
- Admin panel (Laravel 11, PostgreSQL, PostGIS)
- Payment gateway integration (recurring via YooKassa)
- Push notification setup (FCM)
- API documentation for future support
- Staff training for the admin panel
- Source code access
- Server deployment and setup
- 3-month warranty support after release
Work Process: From Idea to Release
- Analytics and prototyping — gather requirements, design user scenarios for three roles.
- UI/UX design — design interfaces adapted to usage scenarios.
- Development — write code in Flutter and Laravel, integrate payments, maps, pushes.
- Testing — QA on real devices, check compliance with App Store and Google Play requirements.
- Deployment — publish to app stores, configure servers.
- Post-release — staff training, 3-month warranty support.
Timeline and Cost
MVP (client + cleaner, basic assignment, payment) — from 14 to 18 weeks. Full version (recurring orders, auto-assignment, advanced analytics) — from 22 weeks. Cost is calculated individually. Request a turnkey development and automate your service. Get a consultation — we'll discuss your project and prepare a proposal.