Designing for African users: practical principles that matter

Good design for Lagos is different from good design for London. Here is what to keep in mind.

Design is not universal. What works for users in San Francisco or London may not work for users in Lagos, Port Harcourt, or Abuja.

Start with performance. Your beautiful animation means nothing if the page takes ten seconds to load on 3G. Optimize images. Minimize requests.

Design for low-end devices. Test on phones that cost ₦30,000 to ₦50,000. Make sure your touch targets are large enough. Make sure your text is readable.

Think about language and literacy. Not everyone is comfortable in English. Use clear, simple language. Support local languages where it matters.

At CEA, we teach design as a practice of empathy. Before you open Figma, understand who you are designing for.

Connectivity shapes everything downstream. Users move between strong Wi-Fi, throttled mobile data and dead zones, often within one session. Design for graceful degradation: skeleton screens instead of spinners, optimistic UI that assumes success and reconciles later, clear offline indicators, and the ability to queue actions. Data-consciousness matters equally — a screen showing a user's data usage, or letting them choose image quality, builds loyalty that glossy design cannot buy.

Payment UX is where many products silently leak users. Card entry flows fail constantly here — OTPs time out, cards get declined for reasons unrelated to funds, and international card restrictions catch people out. Offer alternatives: pay-with-bank-transfer, USSD fallbacks, wallet top-ups at agents. Design error states that explain what actually happened ('your bank declined this — try another card or pay by transfer') rather than a generic red toast. Every failed payment you prevent is revenue retained.

Trust signals carry unusual weight because online fraud is a lived experience, not an abstract risk. Show real photos of real locations, human names with faces for support contacts, verifiable phone numbers and addresses, and social proof from recognisable Nigerian names or institutions. Display prices in naira prominently; hidden pricing triggers suspicion. And make cancellation or contact trivially easy to find — paradoxically, visible exit routes increase willingness to commit, because they signal the opposite of a scam.

Language and iconography deserve more nuance than 'translate to Pidgin'. Most Nigerian users read English comfortably but process it as a second or third language: favour short sentences, concrete verbs, avoid idiom and sarcasm in microcopy. Icons need local validation — a mailbox icon means little where post is rare; use familiar metaphors instead. Where literacy is genuinely mixed (products for market traders, elderly users), pair text with imagery, support voice notes as input, and consider voice-first interfaces entirely.

Finally, test with actual users, not your team. Five sessions watching real users in their own environment — a shop, a bus stop, their home network — will destroy more assumptions than any analytics dashboard. Recruit participants who match your audience's devices and networks, not designers with flagship phones. Watch where they hesitate, what they ignore, when they ask 'is this safe?'. Empathy in design is not a mood board; it is the discipline of being wrong in front of real people before your product pays for it in churn.