phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

2-in-1 Carpooling Platform (Short + Long Distance)

  • Posted:
  • Proposals: 66
  • Remote
  • #4486116
  • OPPORTUNITY
  • Expired
Armaghan A.Ali S.Techthoth S.Aurel H.Michael A. + 61 others have already sent a proposal.
  • 11

Description

Experience Level: Expert
Develop a hybrid 2-in-1 carpooling platform (iOS, Android, Web, Backend) combining long-distance scheduled trips and short-distance on-demand rides with a global toggle. Features: real-time GPS tracking, 3D vehicle animation, driver/passenger KYC, vehicle auto-recognition, wallets with automated 65/35 split, booking flows, cancellation rules, ratings/loyalty, admin CMS, payment gateways, policy pages, scalable microservices, secure auth, and deployment-ready deliverables including API docs, QA, and integrations. Ratings visible on driver profile
• Feedback system mandatory

⸻

9. Driver Profile Display

Before booking, passengers must see:
• Vehicle details (plate, model)
• Available seats
• Total trips completed
• Ratings & reviews
• Past feedback

⸻

10. Notifications System
• Push notifications (Firebase/APNs)
• Real-time alerts:
• Booking confirmation
• Driver arrival
• Trip start/end
• Payment updates

⸻

11. Integration Requirements

⸻

11.1 Website Integration
• Sync with existing:
• Driver forms
• Passenger database
• Shared backend APIs

⸻

11.2 Admin CMS

Super Admin must:
• Manage users (drivers/passengers)
• Monitor transactions
• Control payouts
• Handle disputes
• View analytics

⸻

11.3 Payment Gateway Integration
• Stripe / PayPal / Local gateways
• Must work across:
• Mobile apps
• Website

⸻

12. Policy & Compliance Pages

Integrate:
• Privacy Policy
• User Policy
• Cancellation Policy
• Dispute Resolution
• Complaint Forms

⸻

13. Technical Requirements

⸻

Frontend
• Flutter / React Native (preferred for cross-platform)
• Smooth UI/UX (Uber-like experience)

⸻

Backend
• Node.js / Django / Laravel
• RESTful APIs
• Scalable microservices architecture

⸻

Database
• PostgreSQL / MySQL
• Real-time DB (Firebase optional)

⸻

Maps & Location
• Google Maps API / Mapbox
• Real-time GPS tracking

⸻

14. Security Requirements
• KYC verification
• Data encryption (SSL)
• Secure authentication (JWT / OAuth)
• Fraud detection system

⸻

15. Deliverables

Developer must provide:
• Fully functional iOS & Android apps
• Admin dashboard (CMS)
• Backend API documentation
• Integrated website system
• Testing & QA
• Deployment support

⸻

16. Expected Outcome

A fully integrated hybrid ride-sharing ecosystem that:
• Works like BlaBlaCar + Uber in one app
• Allows mode switching
• Provides real-time tracking + structured trip booking
• Ensures automated revenue split & wallet system

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Asad C.

    -/ How do you want the intercity (scheduled, seat-based trips) and intracity (on-demand rides) to coexist at a system level should they operate as two distinct modules with separate logic, or share a unified pool of drivers and bookings, and how exactly should the global toggle affect driver availability and passenger experience in real time?

    -/ For the booking flow, can you clarify how detailed you want each mode to be for example, should intercity rides follow a structured seat selection and schedule-based reservation system (with fixed pricing and availability), while intracity rides rely on real-time driver matching and dynamic pricing, and how should cancellations, rescheduling, and seat reallocation be handled in both cases?

    -/ Regarding the wallet and automated 65/35 revenue split, how should the transaction lifecycle work should funds be held in escrow until trip completion, when exactly should the split be triggered, and how do you want to handle edge cases like partial refunds, cancellations, or disputes where the split may need to be reversed or adjusted?

    -/ For payment gateway integration, are you aiming for a centralized payment layer that abstracts Stripe, PayPal, and local gateways into one system, and should the wallet support additional features like top-ups, promo credits, loyalty rewards, and multi-currency handling across mobile and web?

    -/ In terms of driver onboarding and verification (KYC + vehicle recognition), do you want a fully automated flow using OCR/AI for document validation and number plate recognition, or should there be a manual admin approval layer, and what level of verification is required before a driver can start accepting rides?