Rideshare current limitations

This page lists gaps visible in current source. It is not a regulatory or operational checklist. Ride-for-hire rules, driver licensing, insurance, and consumer protection depend on your jurisdiction and are outside this repository.

Dispatch and routing

Dispatch is manual. Fleet operations mode is off or manual; there is no automatic matching, batching, or surge pricing.
Route distance and duration are estimates from labels. There is no geocoding, map display, live ETA, or turn-by-turn navigation.
Location tracking is limited to coarse, expiring LocationEvent rows submitted through recordTripLocation.

Payments and settlement

Only the manual payment adapter is installed. It records obligations and does not charge cards, capture funds, or issue refunds.
Payout exists in the schema, but no mutation or page creates payouts. The code states that no payout or revenue journal is posted until a reviewed allocation policy and settlement workflow exist.
There are no payment webhooks.

Riders

Guest riders can book, track, and cancel with their request proof, but cannot rate a trip, open a support case, report a safety issue, or message the driver. Those mutations require a signed-in participant.
Rider signup is one global switch, not per fleet. It opens when any active fleet sets rider accounts to open, or when PUBLIC_SIGNUPS_ALLOWED is true. A new rider account is a plain User; no RiderProfile is created at signup.
The storefront has no saved places, payment methods, or in-app payment step. Payment is recorded by operators on the trip.

Drivers and compliance

Compliance documents store kind, issuer, masked reference, and dates. There is no file upload for documents and no external verification.
Identity and background-check provider connections have no working adapters. Eligibility decisions are operator reviews recorded as PolicyEvaluation rows.
The software does not license drivers or vehicles, verify insurance, or establish that a fleet may operate a ride-for-hire service.

Notifications

The only notification adapter writes to the console and is disabled in production. Riders and drivers do not receive SMS, push, or email trip updates.

No certification

The repository does not provide PCI, privacy, accessibility, or transportation-regulator certification. Tests, type checks, and builds show only the behavior they exercise.