Pump — Home Services Marketplace

Key Results

The Problem

Home maintenance in Saudi Arabia relies on fragmented, word-of-mouth networks. Customers struggle to find available, verified technicians on demand, while independent technicians have no reliable channel to receive job requests in their area.

• Customers have no centralized platform to compare service pricing or book verified home technicians — they rely on personal contacts or unvetted listings.
• Technicians waste time traveling to distant jobs with no location-based matching — no system to route nearby requests to available workers.
• No real-time communication between customer and technician during a job, leading to missed addresses, schedule confusion, and no-shows.
• The Saudi market is Arabic-first but most platforms offer poor RTL support and lack proper Arabic localization.

The Solution

Built a complete two-sided Flutter marketplace — customers browse a 3-tier service catalog, book tasks, and track orders in real-time; technicians receive geo-matched job notifications, accept/decline with one tap, and manage their earnings. Firebase handles real-time data, auth, and push notifications while a Laravel API manages secure OTP delivery.

1. 1Designed a 3-level service architecture — Services → Sub-Services → Tasks with per-task pricing in nested Firestore subcollections. Seeded 12+ main categories (Plumbing, Electrical, HVAC, Cleaning, Painting, Carpentry, CCTV, Satellite, Appliances, Pest Control, Moving) with Arabic + English names.
2. 2Built dual authentication flows — Firebase Phone Auth (SMS) with automatic WhatsApp OTP fallback via a Laravel server proxy that keeps Meta API credentials off-device. Added Google Play reviewer bypass with hardcoded test numbers.
3. 3Implemented geohash-based technician matching — encodes customer coordinates into a geohash, queries nearby technicians by hash prefix (1km → 7 chars, 5km → 6 chars, 20km → 5 chars), filters by availability, schedule conflicts (±3h window), and service specialization, then sorts by rating.
4. 4Created real-time order lifecycle — full status machine (pending → confirmed → in_progress → completed/cancelled) with Firestore listeners. Each state transition triggers FCM push notifications to both parties through dual channels.
5. 5Built technician-side dashboard — earnings breakdown, ratings history, order queue, availability toggle, and a modal notification overlay with sound for new job matches.
6. 6Implemented real-time chat — Firestore subcollection per order with read receipts, delivered status, and batch marking.
7. 7Added promotional system — offers with audience targeting, promo codes with per-user limits, first-order-only discounts, service-specific applicability, and real-time expiration streaming.
8. 8Built dynamic theming from Firestore — admin can change colors, typography, and button styles live without requiring an app update.

Architecture Decisions

Key technical decisions made during the project and the reasoning behind them.

The Tech Stack

The Impact

A production app live on Google Play (play.google.com/store/apps/details?id=app.pump) with a marketing website at pumpnow.app — serving the Saudi Arabian home services market with full Arabic RTL support, real-time technician matching, and 47 screens across dual customer/technician interfaces.

Related Reading

Deep dives and comparisons related to the technologies used in this project.

Related Projects

Explore similar case studies with overlapping technologies and challenges.