Kamel Ride

This was a 48-hour recruiter design exercise. I focused on the core ride discovery, rider profile, and coordination experience rather than a full product system.

Students need a ride-sharing experience that feels safer than informal group chats, especially when deciding who to ride with and how to coordinate details quickly.

Kamel Ride is intended for students looking for a shared ride and students offering seats on a trip. Both groups need enough information about the other person and the journey to decide whether to travel together. Their goals are to find a suitable ride, assess trust, and coordinate pickup details with less back-and-forth.

Within the 48-hour exercise, trust and coordination were the central design priorities. Profiles, shared interests, and direct communication address the uncertainty of arranging a ride with another student. A next step would be to ask students what information and verification they need before agreeing to a ride.

I prioritized profiles, shared interests, and direct communication because trust and coordination are the highest-risk moments in a student ride-sharing flow.

The core screen sequence moves from ride discovery to a rider profile and then to direct communication. The wireframe structure prioritizes the information needed to judge a potential match before coordinating the trip. With more time, iterations would explore clearer pickup arrangements, ride confirmation, and how the flow should respond when plans change.

Select an image to view it larger. The full prototype lives in Figma.

With more time, I would explore verification, pickup handoff details, and edge cases like cancellations, recurring rides, and accessibility needs.