We build our products — POKOTO, Cue Hard-Breaks and WATHACI Connect — for the conditions our users actually work in: shared devices, prepaid data, unstable power and mobile money as the default way value moves. Those constraints improved the products.
Assume the network will fail
A user in Chipata or Mongu on a prepaid bundle should not lose a completed task to a dropped connection. We treat capture and sync as separate concerns: record locally, queue, reconcile, and make the sync state visible so the user knows what is safe.
The same discipline applies to page weight. Every asset added is data a user paid for out of pocket, so we budget bytes as deliberately as we budget features.
Mobile money is the primary rail
Card penetration in Zambia remains thin, while MTN, Airtel and Zamtel wallets are ubiquitous. Designing mobile money as the first-class path — not a secondary tab — changes flows considerably: you must handle USSD prompt delays, user timeouts, partial confirmations and reconciliation against provider references.
Webhook-driven confirmation with idempotent handling and a clear pending state is not an optimisation here; without it, users pay and see nothing, and support absorbs the cost.
Design for shared devices and mixed literacy
One phone often serves a household or a whole market stall. That argues for short sessions, explicit sign-out, minimal sensitive data cached on device, and receipts delivered over SMS or WhatsApp rather than assuming the user will return to the app.
Language and iconography matter too. Plain English with local phrasing, generous tap targets, and confirmation screens that restate what will happen in money terms reduce support load far more than visual polish does.
Build for the regulator you will meet
Zambian products that touch payments, personal data or communications operate inside a real framework: the Data Protection Act No. 3 of 2021, the Cyber Security and Cyber Crimes Act, Bank of Zambia payment systems oversight and ZICTA licensing. Data minimisation, retention limits, audit logging and breach procedures should be present in the first release.
Ship with a support and training plan
The difference between adoption and abandonment in this market is usually human. A local number that answers, onboarding done in person for the first cohort, short video guides sized for mobile data, and an issue path that closes the loop keep a product alive after launch week.
Key takeaways
- Offline tolerance and byte budgets are core features, not refinements.
- Treat mobile money as the primary payment rail, with idempotent webhook confirmation.
- Shared devices demand short sessions and out-of-app receipts.
- Local, reachable support is what converts a launch into adoption.