Two apps
Rider and driver journeys designed as one connected system.
All Case Studies
Case Study 04 / Harvey
Building a ride-hailing product that keeps both sides of the trip moving.
A two-sided product that keeps the rider, driver and operations team moving in the same direction.
Harvey needed a product that could make a ride feel clear from both directions. Afro-Intelligent shaped the Rider and Driver experiences around the same trip states, then connected route search, fare negotiation, approval, matching and private active-trip chat into one release-ready platform.
Rider + Driver platformSouth Africa
Realtime decisions
Matching, negotiation and trip states stay current.
Private coordination
Matched riders and drivers can chat when the trip is active.
Admin visibility
Operations can review trip activity and chat context.
The product problem
A ride is a shared process.
Harvey needed to make a ride legible to everyone involved. A rider needs to set a route, understand the fare and know whether a driver is on the way. A driver needs a focused workspace for availability, trip decisions and live status. The operations team needs enough visibility to support the platform.
The work was therefore about more than individual screens. It was about connecting the moments between request, negotiation, approval, matching and the live trip.
One product. Two mobile roles. A shared trip state.
Rider experience
The rider journey stays calm when the trip gets complex.
The rider side was shaped around clear decisions: where are you going, what fare makes sense, what is happening now and what should you do next?
Set the route
Pickup, destination and recent places are clear before the ride begins.
Negotiate with confidence
The suggested fare, rider offer and response state stay visible in one focused flow.
Know what happens next
Trip approval and driver matching give the rider a clear status instead of a dead end.
Driver experience
The driver side turns demand into a workable shift.
Driver screens need to be fast to read, easy to act on and dependable in motion. Harvey keeps availability, opportunities, fare context and trip state close together.
Choose availability
Drivers can control when they are ready to receive trip opportunities.
Review the opportunity
Demand, trip state and fare decisions are presented without unnecessary noise.
Stay connected
Matched-trip chat gives the rider and driver a private channel when coordination matters.
The connected system
The important states are shared.
Harvey coordinates a trip through a sequence of states that both sides can understand. When the rider negotiates, the driver needs the offer. When a trip is approved, the rider needs reassurance. When the trip is active, both people need a direct way to coordinate.
Pickup and destination
Fare suggestion
Rider offer
Driver response
Trip approval
Driver matching
Active-trip chat
Admin context
A trip has a rhythm.
The interface makes that rhythm visible so people are not left guessing whether the request is waiting, being negotiated, approved or already in motion.
Visual proof
Product details that carry the experience.
The strongest product work often lives in the transitions: a search result that stays above the keyboard, a fare offer that is easy to compare, a status that removes uncertainty and a chat channel that appears only when it is relevant.
Route setup
The rider starts with a clear pickup and destination flow.
Fare negotiation
Suggested fare, offer and response state stay together.
Trip approved
The rider sees that matching has started and what happens next.
Account entry
A focused account flow keeps first use approachable.
Admin and platform confidence
A mobile product still needs an operational view.
Private trip chat
Rider-driver conversation is available to the matched parties during an active trip, keeping the channel relevant and private.
Admin context
The admin trips view can show chat counts and a latest-message preview so support is not separated from the trip record.
Existing endpoints preserved
The new experience was added around the existing booking and contact paths, protecting the workflows that already worked.
Why it matters
This is a product, not a set of screens.
Harvey demonstrates how Afro-Intelligent works when the challenge is operational. We started with the moments where a ride can become confusing, then shaped two role-specific experiences around the same underlying trip.
The result is a stronger foundation for rider trust, driver action and admin support. It can keep evolving without losing the clarity of the first release.
01
Clarity
Every state has a visible next step.
02
Coordination
Both sides understand the same trip.
03
Confidence
Operations can see enough to support it.
The outcome
A clearer platform for every side of the trip.
Harvey now has a clearer two-sided product story: riders can request and follow a trip while drivers can manage availability and act on demand.
The release includes a focused fare negotiation flow, trip approval and matched Rider-to-Driver chat for active-trip coordination.
The admin trips experience includes useful chat context, giving operations a better view of what is happening around a trip.
Rider and Driver Android release packages were prepared without removing the existing booking and contact workflows.