Riderly - Rider App
Riderly - Rider App
Riderly - Rider App
PRODUCT NAME
PRODUCT NAME
RIDERLY
RIDERLY
RIDERLY
PROJECT MODE
PROJECT MODE
Personal Project
Personal Project
Personal Project
PLATFORM
PLATFORM
Mobile App
Mobile App
Mobile App
TARGET AUDIENCE
TARGET AUDIENCE
Riders
Riders
Riders
ROLE
ROLE
Product Designer
Product Designer
Product Designer
TIMELINE
TIMELINE
3 Weeks
3 Weeks
3 Weeks
Designing a delivery experience for riders to earn smarter, not just work harder
Overview
When I started exploring the logistics space, I realized that most delivery platforms are designed around completing orders, not around the people actually doing the work. Riders are expected to move fast, make quick decisions, and handle multiple deliveries. Yet the tools they use rarely support how they actually think or operate.
When I started thinking about the rider side of logistics, I didn’t want to design another “delivery app.” I wanted to understand what it actually feels like to be on the road, making decisions in real time.
Riders aren’t just completing tasks, they’re constantly making trade-offs. Every job they accept affects how much they earn, how much time they spend, and how stressful their day becomes.
When I started exploring the logistics space, I realized that most delivery platforms are designed around completing orders, not around the people actually doing the work. Riders are expected to move fast, make quick decisions, and handle multiple deliveries. Yet the tools they use rarely support how they actually think or operate.
When I started thinking about the rider side of logistics, I didn’t want to design another “delivery app.” I wanted to understand what it actually feels like to be on the road, making decisions in real time.
Riders aren’t just completing tasks, they’re constantly making trade-offs. Every job they accept affects how much they earn, how much time they spend, and how stressful their day becomes.
eventrite is a mobile-first ticketing platform that enables users to discover events, purchase secure digital tickets, and manage them seamlessly within a single ecosystem.
Riderly is a mobile-first, delivery experience for riders handling logistics to deliver faster, handle multiple deliveries, make smart decisons and earn.
Riderly is a mobile-first, delivery experience for riders handling logistics to deliver faster, handle multiple deliveries, make smart decisons and earn.
Problem Statement
Most systems simply notify riders of a job and expect them to accept or decline within seconds. But that decision is critical—it determines how much they earn, how much time they spend, and how stressful the next hour becomes.
One rider, Tunde, explained it in a way that stuck with me. He said, “I just accept and hope it’s worth it. Sometimes it’s not.” That “hope” is a design failure.
I also noticed that when riders handled multiple deliveries, they were left to figure out the best route themselves. This created unnecessary mental effort and wasted time.
Most systems simply notify riders of a job and expect them to accept or decline within seconds. But that decision is critical—it determines how much they earn, how much time they spend, and how stressful the next hour becomes.
One rider, Tunde, explained it in a way that stuck with me. He said, “I just accept and hope it’s worth it. Sometimes it’s not.” That “hope” is a design failure.
I also noticed that when riders handled multiple deliveries, they were left to figure out the best route themselves. This created unnecessary mental effort and wasted time.
Riders often make delivery decisions with little to no context, leading to inefficient routes, lower earnings, and increased cognitive stress.
Riders often make delivery decisions with little to no context, leading to inefficient routes, lower earnings, and increased cognitive stress.
MY ROLE
This was a personal project where I took full ownership of the rider experience as a Product Designer. I was responsible for definining the rider-side problem, conducting user research, designing flows and interactions patterns and also structuring the overall experience.
This was a personal project where I took full ownership of the rider experience as a Product Designer. I was responsible for definining the rider-side problem, conducting user research, designing flows and interactions patterns and also structuring the overall experience.
MY APPROACH
To ground my decisions, I spoke with a small group of riders and simulated realistic delivery scenarios.
To ground my decisions, I spoke with a small group of riders and simulated realistic delivery scenarios.
Tunde (32, dispatch rider) shared:
“If I know I’m going far, I should at least know the money is worth it.”
“If I know I’m going far, I should at least know the money is worth it.”
From these conversations, I identified two key gaps:
Lack of decision transparency before accepting jobs
Lack of system support during multi-delivery execution
I also mapped out a typical rider journey and noticed how often they had to pause and think, which is dangerous in a fast-moving environment.
From these conversations, I identified two key gaps:
Lack of decision transparency before accepting jobs
Lack of system support during multi-delivery execution
I also mapped out a typical rider journey and noticed how often they had to pause and think, which is dangerous in a fast-moving environment.
User Stories — What riders actually need
To guide my design decisions, I framed a few key user stories:
To guide my design decisions, I framed a few key user stories:
As a rider, I want to see clear earnings and time estimates before accepting a job, so I can make better decisions.
As a rider, I want to see clear earnings and time estimates before accepting a job, so I can make better decisions.
As a rider, I want to complete deliveries with minimal interaction, so I can stay focused on the road.
As a rider, I want to complete deliveries with minimal interaction, so I can stay focused on the road.
At this stage, I asked myself:
Structuring User Needs Across the Experience
To maintain consistency with my earlier approach, I mapped user stories across the three key phases I had already defined:
Discovery
Purchase
Ownership (post-purchase experience)
This ensured that I wasn’t just solving isolated problems, but designing a complete end-to-end experience.
“What does the user actually need to achieve at each stage of this experience?”
Challenges — Designing for motion and pressure
One of the hardest parts of this project was designing for low-attention usage. Riders are not sitting comfortably scrolling through an app they are: Navigating traffic, holding their phone with one hand, making split-second decisions. This meant I had to rethink traditional mobile design patterns.
Another challenge was balancing information vs speed. Riders needed more context, but too much information would slow them down. I had to carefully prioritize what mattered most in each moment.
One of the hardest parts of this project was designing for low-attention usage. Riders are not sitting comfortably scrolling through an app they are: Navigating traffic, holding their phone with one hand, making split-second decisions. This meant I had to rethink traditional mobile design patterns.
Another challenge was balancing information vs speed. Riders needed more context, but too much information would slow them down. I had to carefully prioritize what mattered most in each moment.
SOLUTIONS (UI DESIGNS)
Instead of designing a simple task flow, I designed the rider app as a real-time decision assistant.
Instead of designing a simple task flow, I designed the rider app as a real-time decision assistant.
Designed the home screen as a real-time decision dashboard
This is the first screen riders interact with when they open the app, and more importantly, it’s where they make some of their most critical decisions—whether to accept a job or not. So I designed it to surface only the most relevant information upfront: earnings, distance, estimated time, and contextual indicators like demand or batching opportunities. Rather than forcing riders to tap into multiple screens to understand a job, I made sure they could evaluate everything at a glance.
This approach reduces friction significantly. Riders spend less time thinking and more time acting, which ultimately leads to faster decision-making and better earning opportunities.
This is the first screen riders interact with when they open the app, and more importantly, it’s where they make some of their most critical decisions—whether to accept a job or not. So I designed it to surface only the most relevant information upfront: earnings, distance, estimated time, and contextual indicators like demand or batching opportunities. Rather than forcing riders to tap into multiple screens to understand a job, I made sure they could evaluate everything at a glance.
This approach reduces friction significantly. Riders spend less time thinking and more time acting, which ultimately leads to faster decision-making and better earning opportunities.
Structured the orders screen for clarity and continuity
I designed the Orders screen to act as a central source of truth for all delivery activity, both ongoing and completed. Riders often need to reference past deliveries either to confirm details, track earnings, or resolve disputes. So instead of treating orders as temporary items that disappear after completion, I structured them into clear states: active, completed, and sometimes failed or cancelled.
Each order is presented with just enough detail to be useful without overwhelming the rider. This includes delivery locations, earnings, and status indicators. The intention here was to provide continuity and transparency. Riders can always understand what they’ve done, what they’re currently doing, and what’s coming next. This reduces confusion, especially during busy periods when they’re handling multiple deliveries.
I designed the Orders screen to act as a central source of truth for all delivery activity, both ongoing and completed. Riders often need to reference past deliveries either to confirm details, track earnings, or resolve disputes. So instead of treating orders as temporary items that disappear after completion, I structured them into clear states: active, completed, and sometimes failed or cancelled.
Each order is presented with just enough detail to be useful without overwhelming the rider. This includes delivery locations, earnings, and status indicators. The intention here was to provide continuity and transparency. Riders can always understand what they’ve done, what they’re currently doing, and what’s coming next. This reduces confusion, especially during busy periods when they’re handling multiple deliveries.
Gamified earnings, milestones, and rewards
One of the more strategic decisions I made was to introduce a gamified layer to earnings and rewards. From my research, I noticed that riders are highly motivated by daily performance, how much they’ve earned, how many deliveries they’ve completed, and whether they’ve hit certain targets. So instead of presenting earnings as static numbers, I designed a system that actively encourages progress and consistency.
This includes; Daily and weekly milestones, Streaks for consistent activity and Bonus rewards for hitting targets.
The purpose here wasn’t just to “make it fun,” but to drive behavior in a meaningful way. By visualizing progress and rewarding consistency, riders are more likely to stay engaged and motivated throughout the day. It also gives them a sense of achievement beyond just completing tasks. They’re not just delivering orders—they’re progressing toward goals.
One of the more strategic decisions I made was to introduce a gamified layer to earnings and rewards. From my research, I noticed that riders are highly motivated by daily performance, how much they’ve earned, how many deliveries they’ve completed, and whether they’ve hit certain targets. So instead of presenting earnings as static numbers, I designed a system that actively encourages progress and consistency.
This includes; Daily and weekly milestones, Streaks for consistent activity and Bonus rewards for hitting targets.
The purpose here wasn’t just to “make it fun,” but to drive behavior in a meaningful way. By visualizing progress and rewarding consistency, riders are more likely to stay engaged and motivated throughout the day. It also gives them a sense of achievement beyond just completing tasks. They’re not just delivering orders—they’re progressing toward goals.
Introduced metrics, insights, and performance indicators
Beyond earnings, I wanted riders to understand how they’re performing, not just how much they’re making.This includes; Daily and weekly milestones, Streaks for consistent activity and Bonus rewards for hitting targets. So I designed a dedicated space for metrics and performance insights, including: Completion Rate, Average Delivery Time, Ratings, Earnings Over Time.
The reason for this was simple: visibility drives improvement. When riders can clearly see their performance, they become more aware of their habits and can adjust accordingly. For example, a rider might realize they’re declining too many jobs or taking longer routes than necessary.
This transforms the app from a passive tool into something more reflective—a system that not only supports work but also helps riders improve over time.
Beyond earnings, I wanted riders to understand how they’re performing, not just how much they’re making.This includes; Daily and weekly milestones, Streaks for consistent activity and Bonus rewards for hitting targets. So I designed a dedicated space for metrics and performance insights, including: Completion Rate, Average Delivery Time, Ratings, Earnings Over Time.
The reason for this was simple: visibility drives improvement. When riders can clearly see their performance, they become more aware of their habits and can adjust accordingly. For example, a rider might realize they’re declining too many jobs or taking longer routes than necessary.
This transforms the app from a passive tool into something more reflective—a system that not only supports work but also helps riders improve over time.
Results & Impacts
Instead of designing an app that simply tells riders what to do, I designed a system that helps them make better decisions, supports them during execution, reflects their perfomance over time. My focus was ongiving riders more control, more context and less cognitive load. The result is an experience that feels less like a tool and more like a work companion—one that actively helps riders succeed, not just complete tasks.
Instead of designing an app that simply tells riders what to do, I designed a system that helps them make better decisions, supports them during execution, reflects their perfomance over time. My focus was ongiving riders more control, more context and less cognitive load. The result is an experience that feels less like a tool and more like a work companion—one that actively helps riders succeed, not just complete tasks.
Conclusion
This project reminded me that good design isn’t about making things look clean—it’s about making real-world tasks easier to perform. In this case, the biggest improvement came from helping riders make better decisions, faster.
This project reminded me that good design isn’t about making things look clean—it’s about making real-world tasks easier to perform. In this case, the biggest improvement came from helping riders make better decisions, faster.
Next Steps
If I were to continue this project, I’d explore voice-assisted interactions for hands-free use, predictive job recommendations, deeper performance insights.
If I were to continue this project, I’d explore voice-assisted interactions for hands-free use, predictive job recommendations, deeper performance insights.
2023
Mobile App
In Progress
Recruitly
Mobile-first AI-powered gamified experience job applicants.
2023
Mobile App
Eventrite
Mobile-first ticketing platform that enables users to discover events, purchase secure digital tickets.
2023
Web App
Eventrite - webapp
Web-based event creation and management platform for organizers to plan, launch, and actively manage events in real-time.
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts
Let's connect
UX DESIGN
PRODUCT DESIGN
UI DESIGN
Designs
Contacts