Contact person: iOS and Android Mobile App -- 3

Phone:Show

Email:Show

Location: London, United Kingdom

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I’m building a mobile experience that lets residential and commercial clients book, manage, and rate cleaning services from their phones. The core of the project is a smooth booking flow—customers choose a service, pick a time, and receive an instant confirmation—but I also need the surrounding ecosystem that keeps cleaners, customers, and admins perfectly in sync on both Android and iOS.

What the app must do
• Customer side: schedule appointments, view past and upcoming jobs, pay in-app, re-book with one tap, chat with support or their assigned cleaner, and leave ratings and feedback.
• Cleaner side: accept or decline jobs in real time, follow GPS directions to the site, clock in/out for compliance, confirm completion with photos, and review personal safety and health guidelines before each shift.
• Admin side: view a live calendar of every cleaner, edit time slots, insert upsell offers, handle refunds, monitor health-and-safety acknowledgements, and export data for payroll and reporting.

Technical expectations
• One codebase targeting both Android and iOS—Flutter, React Native, or another modern cross-platform stack you’re comfortable owning end-to-end.
• Secure backend with role-based access, real-time chat, and push notifications.
• Payment gateway integration (Stripe preferred) with support for tips and promo codes.
• GDPR-compliant data handling and basic location tracking limited to active jobs.
• Clean, maintainable code plus hand-off documentation so my in-house team can extend features later.

Acceptance criteria
1. A published (or TestFlight/Play Console) build for each platform that passes our internal QA checklist.
2. Admin web panel or mobile module that edits services, prices, staff, and availability.
3. Database and API fully deployed on our cloud account with access keys transferred.
4. Source code, environment files, and a concise README delivered in a private repo.

If this all fits within your wheelhouse, let’s talk about timelines and milestones—looking forward to collaborating." (client-provided description)