Hephi Studios · On-demand logistics
Picka Rider App
Designing the app that keeps Picka’s promise of speed: one rider, one delivery, one clear next step.

- Company
- Picka, built at Hephi Studios
- My Role
- Lead Product Designer
- Team
- Me and Cynthia on design, at Hephi Studios
- Platform
- Mobile rider app, alongside the Picka business dashboard
- Read Time
- 4 min
Results at a glance
- 2connected products: the business dashboard that creates deliveries and the rider app that completes them
- Dec 2026Picka begins operations
01 · Problem
Picka promises on-demand delivery at scale. Businesses book on the dashboard, but every promise of speed is kept or broken by the rider on the road.
02 · Insight
A rider is moving, often one-handed, with a package. The app has to answer one question at every moment: what do I do next?
03 · What I did
Designed the rider app end to end: verification with Nigerian IDs, going online, accepting jobs with the price up front, one clear step per stage of a delivery, proof of drop-off, and getting paid.
04 · Result
The app is designed and prototyped end to end, and Picka begins operations in December 2026.
01 — The problem
Speed is decided on the road.
Picka is built on one idea: on-demand delivery at scale. Businesses use the Picka dashboard to book a single delivery or a bulk run, pay, and track every package on a map.
But a booking is only a promise. Whether it arrives fast depends on a rider seeing the job, accepting it, finding the pickup, reaching the drop-off and proving it was delivered. The rider app is where that promise is kept or broken.
02 — Context
A studio project that became a company.
Picka began as a logistics product we were building at Hephi Studios. Along the way the project changed hands and changed name, and Hephi chose to keep building it as its own company. Operations begin in December 2026.
That made it more than a client brief: we were designing a product we would have to run.
03 — My role
Lead designer across both sides of a delivery.
I led product design for Picka at Hephi, with Cynthia, across the business dashboard and the rider app.
The live route at the top of this page and the prototype near the end are coded from the Figma screens, not recorded.
04 — The insight
One rider, one delivery, one next step.
A rider uses the app on the move: on a bike, often one-handed, with a package and a customer waiting. Every screen had to make the next action obvious and big enough to hit, and nothing else could compete with it.
05 — Trust first
Verified before the first job.
Riders carry other people’s packages and get paid into a bank account, so trust starts before the first order. Verification uses the IDs riders actually have: an NIN slip, a voter’s card or a driver’s licence, then a selfie to match it, a transaction PIN and biometrics.
Waiting is designed too. “Sit tight, we’re reviewing your info” and “We’re still verifying your account” tell a rider where they stand instead of leaving them guessing. Sign-up asks for the phone number riders use on WhatsApp, since that is where updates actually reach them.
06 — Taking a job
Go online, see the price, decide.
Riders choose when they work: a single slide takes them online. New orders then slide up over the map with what a rider needs to decide in a glance: who, how far, how long, and what it pays. Accept or decline, and swipe up to see every order waiting.
07 — The delivery
Every stage has one primary action.
A delivery moves through fixed stages, and the sheet at the bottom of the map only ever offers the next one:
- Pending pickup: call the sender, then Confirm Pickup.
- Start Trip: the route to the drop-off appears.
- In transit: the recipient, their number and the confirmation code, then Confirm Dropoff.
- The way out is always there too: Pickup Failed and Dropoff Failed sit beside the main action, so a rider is never stuck when something goes wrong.
08 — Proof of delivery
A code that only the recipient has.
A delivery is only complete when the rider confirms it with the recipient’s confirmation code. It protects the business and the customer from false drop-offs, and it protects the rider from disputes, with no paperwork.
Every order keeps its status afterwards, from Pending Pickup and In transit to Successful, Failed or Returned, along with the customer’s rating.
09 — Getting paid
Earnings you can see, and withdraw.
Get Paid Instantly is one of the three promises in onboarding, so earnings are a whole tab, not a menu item. Each completed delivery shows what it earned, the balance is always visible, and withdrawing to a bank takes an amount, a saved account and the transaction PIN.
10 — Iteration
What version one taught us.
The first version of the rider app is still in the file, marked redundant. Comparing it with the final shows what changed:
- One PIN length everywhere. Version one asked for a 4-digit current PIN and a 6-digit new one; the final uses 4 digits throughout.
- Pickup moved into the main flow. Separate order and customer screens with a Confirm Package Pickup button became one step in the home sheet.
11 — Prototype
One job, start to finish.
The whole loop a rider repeats all day: go online, accept, pick up, ride, drop off with the code, get paid and withdraw. Each step is one tap or one slide. Pick any step to jump to it.
12 — Results
Designed, and ready to ride.
Where the work stands:
| Products designed | Business dashboard and rider app |
|---|---|
| Operations begin | December 2026 |
Picka has not launched yet, so there are no delivery numbers to report.



