All projects

YENKO – MOBILE APP

Send, track and pay for deliveries across Ghana, with a courier app built from the same parts.

Client
Yenko Logistics
Service provided
Mobile app – Customer & courier apps
Duration
4 weeks
Year
2025
Tools
Figma
Platform
iOS & Android
View prototype
Yenko – Mobile app: Send, track and pay for deliveries across West Africa

BACKGROUND & CONTEXT

  • Booking a delivery in Ghana meant phoning around, guessing the price and losing sight of the package once it left.
  • Riders and drivers took jobs informally, with no way to show they were verified or to track what they had earned.
  • Payment is mixed: Mobile Money, cash and, increasingly, in-app wallets, often on patchy mobile data.

TARGET USERS

  • Senders: individuals and small businesses, deciding on price, arrival time and whether they can trust the rider

  • Couriers: motorbike riders, car and truck drivers, deciding whether a job is worth the distance and the payout

  • Recipients (indirectly): waiting at the other end, wanting a time and a phone number, not a mystery

THE GOAL

Make booking, paying for and tracking a delivery one visible flow for the sender, and give couriers a way to get verified, take jobs and get paid.

MY PROCESS

  1. Domain research
  2. Role mapping (customer vs courier)
  3. User flows
  4. Wireframes
  5. UI & component library
  6. Prototype

KEY DECISIONS

  1. Package size chosen by what the item is, mapped to a vehicle: motorbike up to 10 kg, car 10–100 kg, truck 100 kg+
  2. Pick your rider with price, ETA, rating and plate visible, plus a 'Find another' escape hatch
  3. Three ways to pay that match local habits: Yenko Wallet, Mobile Money confirmed by USSD prompt, or cash
  4. Tracking lives in a bottom sheet over the map, with a four-step status and call and chat one tap away
  5. Courier jobs arrive as one decision: payout and distance first, then Accept or Decline

THE SOLUTION

  • Booking: pickup, drop-off, package size and fragility, then a matched rider with a visible price.
  • Paying: wallet, Mobile Money (approved on the phone's own USSD prompt) or cash, with clear success and failure states.
  • Tracking: a live route with four stages, from 'Rider is on the way to pickup' to 'Delivery complete', plus chat, in-app and offline voice calls.
  • Courier app: a five-step sign-up (account details, password, ID, licence and selfie, vehicle documents, wallet PIN), an online/offline toggle, job requests and an earnings dashboard.

KEY FEATURES

  1. Package-to-vehicle booking
  2. Rider choice with price & ETA
  3. Wallet, MoMo & cash checkout
  4. Live tracking with 4 stages
  5. Courier document checks in 2 steps
  6. Earnings & Yenko Wallet

DESIGN SYSTEM & ACCESSIBILITY

  • One component library and type scale (Poppins, 10–18 px) shared by both apps; only the navigation bar changes by role.
  • Every status chip carries a written label, so progress never depends on colour alone.
  • Known gaps for the next round: the amber accent (#FFAD00) and grey #909090 fall below 4.5:1 on white for small text, and the icon-only tab bar needs labels.
View gallery (10 images)Hide gallery
Three proto-personas: a small-business sender, a motorbike rider and an occasional sender(opens full size in a new tab)
Proto-personas. One sends daily, one delivers for a living, one sends twice a year and needs it to be obvious.
Flow diagram of the customer booking journey and the courier job journey(opens full size in a new tab)
Both journeys meet at one moment: the courier accepts and the customer sees it.
Three phone screens: send a package with size options, choosing a rider on a map, and checkout(opens full size in a new tab)
Size by what the item is, a rider you can see, then pay: three screens from tap to booked.
Phone screens showing the Mobile Money USSD confirmation and the live tracking sheet(opens full size in a new tab)
Mobile Money is confirmed on the phone's own USSD prompt; tracking keeps the rider one tap away.
Courier sign-up role switch and document verification screen(opens full size in a new tab)
One sign-up, two roles. Couriers then verify in short steps rather than one long form.
Courier home with today's earnings, a delivery request pop-up and the finances screen(opens full size in a new tab)
Courier tools: money and distance first, then a running total of what the day has earned.
Table of key interface copy and why each line matters(opens full size in a new tab)
Plain words where people hesitate: size, payment and status.
Contrast checks of Yenko's palette: blue passes, amber and grey fail for small text(opens full size in a new tab)
The blue carries the interface comfortably; the amber accent and grey captions are the next fixes.
Yenko colour tokens and Poppins type scale(opens full size in a new tab)
One small set of tokens powers both apps and the admin dashboard.
Rating screen, customer home and onboarding(opens full size in a new tab)
Ratings go both ways, and the empty home state still tells you what to do next.

BY THE NUMBERS

Screens from tap to booked
3
Apps, customer and courier, from one set of parts
2
Ways to pay, Mobile Money included
3

OUTCOME

  • A prototype-ready, two-sided product that covers a delivery end to end: sign-up, booking, paying, tracking, rating and payout.
  • Two-way ratings: senders rate the courier and couriers rate the customer.
  • The same parts also power the Yenko admin dashboard, so operations sees the same statuses the customer sees.

What I learned

Designing the courier side first exposed edge cases the customer flow was hiding, like what happens when a rider goes offline mid-job.

View prototype