Zipo Ride-Hailing Platform Development

We are building Zipo, a UK ride-hailing platform using a subscription model (0% per-ride commission). We need two mobile apps (Driver App + Rider App) plus a lightweight Admin/Operator dashboard and backend.

1) Driver App (iOS + Android)

Onboarding: account creation, identity checks fields, PHV licence status fields, vehicle details, bank/payout details (collection only), consent to terms

Subscription payments: monthly fee (e.g., £79.99), recurring billing, invoices/receipts, failed payment handling, pause/cancel, restore

Availability toggle + shift/online status

Job feed: trip requests with upfront price, pickup/dropoff, distance/time estimate, accept/decline, countdown timer

Trip flow: navigate to pickup, “arrived”, “start trip”, “end trip”

Earnings: trip history, weekly/monthly summaries, subscription status, basic analytics

Ratings/feedback + support chat/ticket

Push notifications (job offers, payment, account status)

2) Rider App (iOS + Android)

Signup/login, profile, saved addresses

Book ride: pickup/dropoff, optional stops, notes, accessibility requests

Upfront fixed pricing (no surge), ETA estimates

Matching/dispatch status + driver details, live tracking during trip

Payments: card + Apple Pay/Google Pay (if feasible), receipts, trip history

Ratings, refunds request flow, support

3) Admin / Operator Dashboard (web)

Role-based access (Admin / Operator)

Driver management: approve/reject, view subscription status, documents status fields

Trip monitoring: live trips, cancellations, disputes

Pricing rules management (zones/time bands/simple fare table)

Basic reporting: active drivers, rides/day, revenue from subscriptions

Customer support tooling (tickets, user lookup)

Backend / Infrastructure

REST/GraphQL API, database, authentication, push notifications

Payment integration: Stripe (subscriptions + one-off payments), webhooks

Maps/geo: Google Maps or Mapbox (routing, ETA, geocoding)

Logging, error monitoring, GDPR considerations (UK/EU)

Deliverables

Production-ready apps (App Store + Google Play builds), source code in our GitHub, documentation, deployment guide, handover

Clean UI/UX (we can provide brand assets; you provide Figma if needed)

Preferred tech

Cross-platform: React Native or Flutter

Backend: Node.js/TypeScript, Python, or equivalent (open to recommendations)

Milestones

Architecture + clickable prototype (1–2 weeks)

MVP build: core booking + driver dispatch + subscriptions (6–8 weeks)

Beta + bug fixing + launch-ready (3–4 weeks)

Please include in your proposal:

Similar apps shipped (ride-hailing/marketplace preferred)

Recommended stack + timeline

Estimated cost by milestone

Team composition (PM/engineer/QA) and availability