Building for Nigerian users: what global tutorials don't cover

Global product advice assumes a world that doesn't exist here. Building for Nigerian users taught me a different set of first principles — not worse, just realer.

The realities that reshape everything

Data is paid for by the megabyte. A 4MB JavaScript bundle isn't a performance nicety — it's someone's airtime. Every image, every script, every re-render has a price a user feels directly. My performance budget isn't from a Lighthouse score; it's from empathy plus arithmetic.

Payments have their own rails. Cards fail differently here. Bank transfers, USSD, and agent networks carry real volume. A product that only accepts global card payments excludes most of its potential market on day one.

Connectivity is intermittent. Offline isn't an edge case; it's Tuesday afternoon. Queue writes, cache reads, and make the app tell the truth about what's synced.

Trust is won locally. Unknown products face real scepticism — and users are right to be sceptical. Real names, real faces, local support, transparent pricing. Every trust signal I've added converted better than any growth hack.

What it gives back

These constraints produce products that are lean, resilient, and honest — qualities that help everywhere. Building here isn't a handicap. It's an education in what software actually costs.