Prototype only: this demo saves data on this device/browser. It does not connect separate passengers' and riders' phones or process payments. Demo rider profiles are fictional.

Request a bike

Choose your pickup and destination. A rider must offer a fare, and you must accept that exact amount before the trip can start.

Your name or nickname (optional)

Pickup point

Destination

Pickup details (optional)

I can pay the rider directly in cash after the ride (payment is between us).

Available eligible riders

Only approved, online, available riders with an active trial/subscription should receive requests. This local demo uses sample profiles.

Create a ride request to see demo riders.

My current ride

No active ride selected.

Rider workspace

Demo mode: select a sample rider to review an incoming request and offer a fare. In the real service, riders must be verified by the admin.

Rider profile

Incoming request

No pending request for this rider.

Subscription status

Mobile-money payment reference (manual verification demo)

V1 does not take or verify payments automatically. Do not enter PINs or passwords.

Trip status

Passenger pickup code (demo)

Pilot dashboard

Demo dashboard only — not secured. Do not use this page for real customer data or production administration.

Rider management

Landmarks / stations

Keep pickup points familiar and editable. Verify spelling, exact meeting points, and whether each is a landmark or motorcycle station before public launch.

Add a pickup/destination point

Recent ride records

Metrics help evaluate request volume, successful trips, fare acceptance, cancellations and trial-to-paid conversion. A real backend must log timestamps and dispatch results across devices.

What V1 contains

Passenger pickup/destination selection from an editable Kumba landmark list.
Sample rider availability and eligibility rules.
Rider-proposed fare with explicit passenger accept/decline.
Trip status, pickup code, cancellation and local trip log.
30-day trial/subscription status and manual payment-reference submission.
Basic pilot metrics and JSON export.

Important limits

All data is stored locally in this browser; it is not shared between devices.
Sample riders are fictional and must not be presented as real/verified people.
No GPS dispatch, live notifications, authentication, backend database or automatic mobile-money integration.
Admin page is a demo and has no access control.

Recommended next build step

Connect the passenger and rider screens through a shared API/database, add secure rider/admin accounts, and implement server-side dispatch eligibility and subscription checks before any public pilot.

Built as a low-cost, installable-web-app starting point for testing the agreed-fare flow.