Spaces:
Running
Running
| Role & Goal | |
| You are an expert full-stack web developer. Build a production-ready roadside assistance platform called “RoadResQ” (working name). It should allow customers to request on-demand roadside help (puncture, towing, battery, engine breakdown) and connect them with verified mechanics/tow partners. | |
| Tech Stack (must use) | |
| Frontend: React (with TailwindCSS for styling) | |
| Backend: Node.js (Express) with REST APIs | |
| Database: PostgreSQL | |
| Authentication: JWT-based auth (email/phone login) | |
| Maps & Location: Google Maps API for service request location + live tracking | |
| Payments: Razorpay integration (test mode setup) | |
| Deployment ready: Containerized with Docker, instructions for deploying to AWS | |
| Core Features (MVP) | |
| Homepage: | |
| Hero section with tagline (“Help when you need it, where you need it.”) | |
| Call-to-action button (“Request Help Now”) | |
| Brief section on how the service works (3 steps: Request → Dispatch → Assistance arrives). | |
| Testimonials placeholder. | |
| Customer Portal: | |
| Create account/login. | |
| Request service by selecting problem type (puncture, tow, battery, engine). | |
| Share live location (map picker + geolocation API). | |
| Show estimated arrival time & price before confirmation. | |
| Pay via Razorpay or select cash on delivery. | |
| See mechanic’s live location (real-time tracking via WebSockets). | |
| Service history page. | |
| Mechanic/Partner Portal: | |
| Login/signup for mechanics. | |
| Accept/reject incoming requests. | |
| Navigate to customer using map link. | |
| Mark job as completed. | |
| Earnings dashboard (jobs completed, payouts). | |
| Admin Dashboard: | |
| View active & past requests. | |
| Assign/reassign mechanics if auto-match fails. | |
| Monitor average response time, cancellations. | |
| Manage mechanics (verify ID, enable/disable). | |
| Basic analytics (daily jobs, revenue). | |
| UI/UX Guidelines | |
| Clean, modern UI using Tailwind. | |
| Mobile-first responsive design. | |
| Consistent brand colors (blue + yellow palette for urgency/trust). | |
| Card-style UI for service types. | |
| Minimal text, clear CTAs. | |
| Deliverables | |
| Full React frontend code (with routing, components, state management). | |
| Node.js backend code with REST APIs (services: auth, requests, payments, mechanic matching). | |
| SQL schema for PostgreSQL (users, mechanics, requests, payments). | |
| Integration with Google Maps API (showing current & destination). | |
| Dockerfile + instructions for deployment. | |
| README with setup steps. | |
| Extra Instructions | |
| Write clean, modular, production-level code. | |
| Include comments for all major functions. | |
| Prioritize speed of development + clarity. | |
| Assume this is version 1.0 MVP — no need for advanced features like subscriptions or surge pricing yet. |