01
Service catalogue
Categories, sub-categories, services and variants, with names in several languages and images.
Customer, provider and admin apps for home services
On-Demand Home Services Marketplace
Households book verified local professionals for cleaning, repairs and beauty; the platform assigns them, takes a commission and pays them out.
AT A GLANCEHOME SERVICES
- Apps
- Customer app, provider app, admin panel — as Android apps or one PWA
- Coverage
- Service zones drawn as polygons on a map
- Languages
- English and three Indian languages
- Built with
- Ionic / Angular on Firebase; React PWA on Express
12 MODULESBUILT AND SHIPPED
The problem
What it replaces
Home-services businesses match customers to independent professionals by phone. Nobody knows which provider covers which area, verification is a folder of photocopies, and working out each provider’s earnings after commission is a weekly spreadsheet.
This marketplace has a customer app for booking by service, slot and address; a provider app for jobs, earnings and withdrawals; and an admin panel for the catalogue, service zones drawn on a map, provider KYC, commissions, coupons and complaints. It has been built twice — first as native mobile apps on a serverless backend, then as a single progressive web app.
Who uses it
Customers
Choose a service, pick an address on the map and a time slot, pay, track the booking and raise complaints.
Service providers
Register with KYC, receive and complete jobs, chat with customers and withdraw earnings.
Admins and staff
Catalogue, zones, provider approval, assignment, commissions, coupons and reports, with role-based permissions.
Features
What the system does
02
Zones on a map
Service zones drawn as polygons; customer addresses are matched to a zone automatically, with a nearest-zone fallback.
03
Booking flow
Address book with map location, slot selection, provider availability check, cart and checkout that refuses an address outside the zone.
04
Booking lifecycle
Pending, accepted, in progress, completed or cancelled — with a timeline the customer can follow.
05
Provider assignment
Automatic, manual by an admin, or offered for providers to accept.
06
Provider KYC
Registration with identity documents and bank details that an admin approves.
07
Commissions and withdrawals
Commission rates by category, provider earnings statements and withdrawal requests by bank transfer, UPI or cash.
08
Online payment
Payment through an online gateway in the customer app, with PDF invoices showing the tax breakdown.
09
Provider subscriptions
Packages and subscriptions that providers buy to receive work.
10
Complaints and chat
Complaints with detail and follow-up, and chat between customer and provider.
11
Coupons and notifications
Discount coupons, push and in-app notifications for customers, providers and admins.
12
Admin and content
Employees with granular permissions, user export, static pages and a provider calendar.
Architecture
How the pieces fit together
The first generation ran native mobile apps directly on a serverless database and messaging backend. The second brings the three interfaces into one progressive web app on its own API, with zone matching done on the server.
Apps
- Customer appIonic · Android / PWA
- Provider appIonic · Android / PWA
- Admin panelweb
Platform
- Catalogue & zonespoint-in-polygon
- Bookings & assignment
- Provider KYC & earnings
- Coupons & invoices
Data
- Relational databasev2 schema
- Document databasev1, real-time
- File storageKYC documents
Connected services
- Maps
- Payment gateway
- SMS OTP
- Push messaging
- Translation
- BookA customer picks a service, an address inside a zone and a slot.
- AssignA provider in that zone is assigned automatically or by an admin.
- DeliverThe provider completes the job; the customer follows the timeline and can chat.
- SettleCommission is deducted and the provider withdraws their earnings.
Built with
- Angular
- Ionic
- Capacitor
- Firebase
- React
- Express
- Drizzle
- Google Maps
Built before, fitted to you
Start from an architecture that has already shipped
We have delivered this kind of system, so yours starts from a design that is known to work, not a blank page. Your workflow, your terminology and your approval chain shape what we build on top of it.