Taxi Service Clone Website Build
Budget: ₹600 – ₹1,500 INR
I want to recreate the ride-hailing experience online with two non-negotiable capabilities at launch: a seamless booking system and live driver tracking on an interactive map. Riders must be able to request a car three ways—directly on the site, inside a companion mobile app, or by phoning in so an operator can place the order on their behalf. Every booking, no matter the channel, should feed the same back-office dashboard for dispatchers.
The interface needs to feel modern and sleek: crisp typography, generous white space, smooth animations, and a colour palette that instantly says “tech-forward transport” rather than “traditional taxi”. Think Uber-style clarity but with our branding.
Key deliverables
• Responsive website with account creation, ride-request flow, ETA display, and trip history
• Real-time driver location updates powered by WebSockets or a comparable push technology
• Unified API endpoints so the upcoming iOS/Android apps and the call-centre panel hit the same backend
• Operator console where staff can enter phone bookings, assign drivers, or override routes when needed
• Basic admin area for fare rules, driver onboarding, and service-area polygons
Acceptance criteria
1. A rider can move from login to confirmed booking in under 30 seconds on both desktop and mobile browsers.
2. Driver icons update on the map with a latency below two seconds under normal network conditions.
3. All three booking channels display the same price, ETA, and driver once a trip is confirmed.
Source code, database schema, and deployment instructions (Docker or similar) complete the hand-off so my team can maintain and scale from there.
The interface needs to feel modern and sleek: crisp typography, generous white space, smooth animations, and a colour palette that instantly says “tech-forward transport” rather than “traditional taxi”. Think Uber-style clarity but with our branding.
Key deliverables
• Responsive website with account creation, ride-request flow, ETA display, and trip history
• Real-time driver location updates powered by WebSockets or a comparable push technology
• Unified API endpoints so the upcoming iOS/Android apps and the call-centre panel hit the same backend
• Operator console where staff can enter phone bookings, assign drivers, or override routes when needed
• Basic admin area for fare rules, driver onboarding, and service-area polygons
Acceptance criteria
1. A rider can move from login to confirmed booking in under 30 seconds on both desktop and mobile browsers.
2. Driver icons update on the map with a latency below two seconds under normal network conditions.
3. All three booking channels display the same price, ETA, and driver once a trip is confirmed.
Source code, database schema, and deployment instructions (Docker or similar) complete the hand-off so my team can maintain and scale from there.