Beyond Translation
When most teams think of localisation, they think of translation. Swap text strings between languages. Done.
Building for Nigeria's market taught us that localisation is a much deeper problem. Language is only the beginning.
Language Complexity
Nigeria has three major languages (Hausa, Yoruba, Igbo) and over 500 minor ones. For a government application targeting national reach, the practical languages for full localisation are English, Hausa, Yoruba, and Igbo.
What most teams don't account for: right-to-left layouts are not the only text direction challenge. Yoruba has an extensive diacritic system that some fonts render poorly. Hausa has Arabic-script variants used in northern states. Testing with native speakers, not just translation files, is non-negotiable.
Literacy and Digital Literacy
Text-based interfaces assume literacy. In some target demographics for government services, literacy is not universal. For these users, voice-based navigation, icon-first interfaces, and audio prompts are not nice-to-haves — they're requirements.
We've implemented voice input (using the device's native speech recognition) for form fields in field data collection applications. The transcript is editable, so literate users can correct it.
Number Formats
Standard number formatting assumptions fail in Nigeria. The separator conventions (period vs. comma for thousands and decimals) are not universally consistent across English-speaking Nigerian contexts. Currency display must show the Naira symbol (₦) correctly in all contexts.
Date formats also vary. "DD/MM/YYYY" is the predominant format, but enterprise users with Western software exposure expect "MM/DD/YYYY." Provide explicit format guidance in date pickers.
Connectivity and Data Costs
Content that works fine on a high-bandwidth connection can be economically inaccessible when data is expensive. A government app that loads 5MB of assets on launch is not serving users on pay-as-you-go data plans.
We measure and budget asset sizes as a first-class engineering concern. A reasonable target for initial load on a government citizen app is under 500KB before any user content.
Feature Phone Consideration
Despite smartphone penetration growth, a significant portion of Nigeria's population — particularly in rural areas and among older demographics — uses feature phones. For applications targeting universal reach, a USSD fallback or SMS-based interface is worth considering for critical functions.
Practical Recommendations
- Hire native language testers. Machine translation produces grammatically correct text that reads unnaturally. Native speakers catch this.
- Test on sub-₦50,000 devices. This is the price range of the majority of smartphones in Nigeria.
- Test on slow connections. Throttle to 2G in your browser dev tools and simulate packet loss.
- Design for thumb reach on small screens. Budget Android devices skew smaller than iOS flagships.
- Don't assume always-on location. GPS is power-hungry. Location-based features should degrade gracefully.
