Shipbubble · 2024
Shippa: Shipbubble's fleet app
Rider-facing app for Shipbubble's delivery fleet: assignment through proof of delivery, cash-on-delivery collection by transfer or card, and wallet payouts, on the same design system as the merchant web app and buyer mobile app.
- Role
- Product Designer
- Platform
- iOS, Android
- Timeline
- 2024
- Team
- Product manager, engineering
- End-to-end rider app design
- Order and COD payment flows
- Wallet and payout design
- Design QA

Context
Shipbubble’s web app gets a merchant’s shipment to the right courier. Shippa is the other half: the app the courier’s own riders use to actually run the delivery, from the moment a pickup lands on their phone to the moment cash is in their wallet. I designed it on the same team as Shipbubble’s web and buyer mobile work, on the same component library.
The job, end to end
A rider’s day comes down to three things that all have to hold up: get assigned the right pickup and delivery, prove the delivery happened, and get paid, including cash collected on a merchant’s behalf. Shippa is built around that sequence rather than around a features list.
Home shows what the day looks like at a glance: an online toggle, assigned, completed and pending pickups for the period, and the wallet balance one tap from being withdrawn. A rider can also log an order themselves, capturing the customer’s details, the cash-on-delivery amount, the delivery fee and the seller’s bank details, for jobs that come in outside the normal dispatch.


A new assignment arrives as a request, pickup and delivery address, and whether it is a cash-on-delivery order, that the rider accepts or declines before it becomes a job. Accepted jobs carry everything needed to run them: pickup and delivery contacts with one-tap calling, the package manifest with weight and quantity, the COD amount to collect and from whom, and any handling notes.


Completing a delivery takes a photo as proof and a PIN read back from the customer, so “delivered” is something the receiving customer confirmed, not just something the rider clicked.


Not every delivery goes through. A rider who cannot complete one picks a reason, customer unreachable, cancelled, address not found, rather than leaving the job stuck with no record of why.

Getting paid for cash collected
Cash-on-delivery is where trust gets tested. The COD list tracks every order by payment state, pending or collected, with a “request payment” action that pushes the customer to pay by transfer or card instead of handing over cash. A transfer shows the exact amount, account and reference to pay against, and every order carries a payment timeline, pending, collected, settled, so a disputed payment is not a phone call, it is a record.




Wallet and payout
Everything a rider earns, deliveries and COD collected, lands in one wallet with a running transaction history. Withdrawing is a choice of amount and a bank transfer out, confirmed by an OTP, so a payout is never one tap away from a mistake.



Outcome
Shippa is live on Shipbubble’s fleet, running the same order-to-payout loop across assignment, proof of delivery, COD collection and wallet payouts, on the design system shared with the web and buyer apps. Firm numbers, riders active, COD collected through transfer and card versus cash, delivery completion time, are still early. I hold them as targets rather than confirmed results, with firm figures to follow once there is a stable stretch to report.