← Back to selected work

Zap Logistics

A web app connecting businesses and customers to delivery agents — onboarding, dispatch, wallet and history in one place.

Role
Product design
Stack
Product designUI/UXUser flows

Background

ZAP is a mobility and logistics company. Its core focus, among others, is connecting business owners and customers to delivery agents through a web application.

The problem

Businesses pay a real cost finding delivery agents who are both reliable and available. The methods they fall back on — calls, chats, informal networks — leave coordination to chance, and there is no single place where a business and an agent can find each other and agree on a job.

The approach

ZAP set out to build an interface simple enough that businesses, customers and delivery agents could all meet on it without being taught how.

I studied how Uber, Bolt, Gokada and Max.ng handle the same problem, then prioritised features down to what a first version actually needed and drew the user flows — as much to give the team a shared picture as to design against.

Prioritised features, mapped as flows
User flow diagrams for the Zap delivery journey

Onboarding

Basic details only — name, email, phone number, password — or one tap with Google. The number is verified by OTP, and the account is active immediately after. Nothing is asked for that the first delivery does not need.

Zap sign-up screen beside the OTP number verification screen

Home

The home screen stays deliberately plain. Sending a package, receiving one, and managing a profile are the three things people come for, so those are the three things it offers.

Zap home screen: choose to send or receive, then set pickup and delivery locations on the map

Send & receive

One flow covers both directions. You pick the vehicle the job needs — bike, car, tricycle, van, truck — see the estimate before committing, fill in the receiver, and then watch the assigned driver close on the pickup point with an ETA and a way to call them.

Shipment details with vehicle choice and receiver's info, and the live screen showing the assigned driver approaching

Wallet

Balance, saved cards and transaction history in one place, with top-up and card management alongside. Two ways to pay means a delivery never stalls on a payment method.

Wallet balance and saved cards, and the card detail screen

History

Every delivery, filterable by state, each opening into its full record: route, distance, duration, what it cost and how it was paid, with a receipt to download and a way to report a problem. A business can answer its own questions without contacting support.

History list of past deliveries, and a delivery's detail with route, distance, duration and receipt

Referral

Points for both sides of an invite, at a stated rate — 100 points to NGN 100 — with the three steps spelled out and the link one tap from WhatsApp, X or Facebook. The incentive only works if the maths is visible.

Referrals screen: points earned, referral steps, and the share link

Design approach

User-centricity, simplicity, ease of navigation. One colour palette and one type scale hold the identity together; white space does the work of keeping a logistics app from feeling like a spreadsheet; clear icons and predictable layouts carry the rest.

Key takeaways

The hard part was never the feature list. It was making one interface that three different kinds of user — business, customer, agent — could navigate without instruction. What got me there was what I already understood about interface design from previous products, applied to a domain where every extra step costs someone a delivery.