“Mobile-first” has become a phrase that appears in every proposal and means almost nothing. For a Nigerian business, it should mean something specific: your product works well on the phone your customer actually owns, on the network they actually have, at the moment they actually need it.
Test on the right phone
Most design reviews happen on new laptops and flagship phones. Most of your customers are not using either. Keep a mid-range Android device in the office and make it the device that signs off every release.
Treat data like money
When customers pay for every megabyte, a heavy page isn’t just slow. It is expensive. Set a page-weight budget before design starts and hold every release to it.
- Serve images in modern formats (AVIF or WebP) at the size they are displayed
- Load fonts sparingly: one variable font can replace four static files
- Question every script: analytics, chat widgets and trackers add up quickly
- Lazy-load anything below the first screen
Design for interruption
Calls come in, networks drop, batteries die. Long forms should save progress. Payments should be safe to retry. A user returning after an interruption should land where they left off, not at the start.
Make the next step obvious
Small screens punish ambiguity. Each screen should have one clear primary action, placed where a thumb can reach it, labelled with exactly what will happen.
Measure what users experience
Lab scores are a starting point. Real-user metrics (how fast pages load on your customers’ devices) are the truth. Collect them, review them monthly and treat regressions as bugs.
None of this is glamorous. All of it compounds. A product that respects its users’ phones and data earns their trust in a way no animation ever will.