1) Project Summary (Vision & Scope) We aim to build a fully‑featured on‑demand Recovery/Towing platform for the UAE, similar to Uber/Careem but specialized for roadside assistance and vehicle transport (towing, battery boost, tire change, fuel delivery, etc.). Launch Goal: A strong MVP ready for commercial use, not a prototype. The system must be stable, scalable, and production‑ready. Geographical Scope: Phase 1: Abu Dhabi Phase 2: Expansion to all UAE emirates 2) Required Products (Deliverables) A) Customer Mobile App (iOS + Android) For users to request towing/recovery services. B) Driver Mobile App (iOS + Android) For drivers/operators to receive and complete jobs. C) Admin Web Dashboard For operations, pricing, drivers, orders, and reporting. D) (Optional) Super Admin / Support Panel For dispute management, customer support, and system oversight. 3) Detailed Feature List A) Customer App Features OTP login (SMS or WhatsApp) User profile management Auto‑detect location + manual map adjustment Select service type (towing, battery, tire, etc.) Select vehicle type (sedan, SUV, pickup, etc.) Upload photos/videos of the issue Choose destination (Home / Workshop / Custom location) Upfront pricing estimate (pricing engine) Request sent to nearest driver with acceptance timer Automatic re‑assignment if driver doesn’t respond Full order lifecycle with timestamps Live driver tracking + accurate ETA In‑app chat/call Payment methods: Cash UAE payment gateway (PayTabs / Checkout / Stripe) Ratings + complaints + dispute system (before/after photos) Coupons/discounts + surge/night fees + waiting time Order history Multi‑language (Arabic/English) General settings B) Driver App Features OTP login Upload required documents (license, vehicle registration, photos) Driver status (Available / Busy / Offline) Receive job requests with countdown timer Accept/Reject job Navigate to customer Start/End job + upload before/after photos Earnings summary (daily/weekly) Trip history In‑app chat/call Ratings Multi‑language support C) Admin Dashboard Features Driver management (approval, suspension, documents) Customer management Live order monitoring on map Pricing management (base fare, per km, peak, night, waiting time) Zone/area management Coupon management Complaints & disputes management Financial & operational reports Logs & audit trails Role‑based access control (RBAC) System settings 4) Non‑Functional Requirements (Mandatory) Performance API response time < 300ms Smooth real‑time tracking No lag on mid‑range devices Scalability Support up to 5,000 drivers and 50,000 monthly orders Ability to add new cities/services easily Reliability Monitoring, logging, and daily backups Error alerts and system health checks Security & Privacy RBAC for all admin roles Rate limiting Device integrity checks (AppCheck or equivalent) Encryption of sensitive data Minimal PII storage Secure API rules and access control Data Retention Auto‑cleanup of old tracking data Retain order and pricing history Full audit logs for all actions 5) Suggested Technical Stack (Developers may propose alternatives with justification) Mobile Flutter (preferred) or Native (with justification) Backend Laravel / Node.js / Django Must include API + Business Logic layers Realtime WebSockets OR Firebase Realtime OR Redis Streams (Developer must justify choice) Database SQL (MySQL/PostgreSQL) for orders, pricing, drivers Optional NoSQL for tracking/events Admin Panel React / Next.js / Laravel Nova Maps Google Maps + Directions API Notifications Firebase Cloud Messaging (FCM) Storage AWS S3 / Google Cloud Storage / Firebase Storage 6) DevOps / Infrastructure Requirements Hosting on AWS or GCP Environments: Dev + Staging + Production CI/CD using GitHub Actions Secrets management (AWS Secrets Manager / GCP Secret Manager) Auto‑scaling for API and realtime services Monitoring (CloudWatch / Stackdriver / Sentry) Cost considerations: Google Maps usage SMS OTP Storage Compute Database scaling 7) Handover Requirements Full source code GitHub repository under client ownership Transfer of cloud accounts (Firebase/AWS/GCP) Transfer of App Store / Play Store accounts Complete documentation: Deployment guide Environment setup DB schema API documentation Build files + TestFlight + Internal testing setup 8) What Developers Must Include in Their Proposal (Mandatory) Links to similar published projects Proposed architecture Tracking + ETA strategy Pricing + dispatch logic Security & RBAC approach Whether store publishing is included Estimated Google Maps cost Estimated SMS OTP cost Payment gateway integration plan Timeline estimate Team size & roles QA/testing plan DevOps plan Mandatory Technical Questions for Developers (20 Questions) What architecture will you use and why? How will you implement real‑time tracking without delays? How will you prevent multiple drivers from accepting the same job? How will you handle connection loss and reconnection? How will you build the pricing engine? How will you build the dispatch logic? How will you detect fake GPS or manipulated location data? What is your security plan (rate limits, RBAC, encryption)? What is your testing strategy? What is your DevOps plan? How will you monitor system health? How will you handle backups and recovery? How will you scale the system as drivers increase? How will you scale as orders increase? How will you handle errors and exceptions? What is your data retention strategy? Is store publishing included in your price? What are the expected Google Maps costs? What are the expected SMS OTP costs? Do you have similar projects? Provide links.