Building for multilingual African audiences

One user, several languages, one session

In Rwanda alone, a single user might read Kinyarwanda at home, French at church, and English at work — sometimes switching between them within the same conversation. Products designed around a single default locale miss how naturally people here move between languages.

That means language switching needs to be cheap and visible, not buried three menus deep in a settings screen. It also means copy has to be written to translate cleanly — short sentences, concrete verbs, minimal idiom — rather than adapted awkwardly after the fact.

Tone matters as much as translation

A literal translation can still feel foreign if the tone doesn't match how people actually communicate — more formal in some contexts, warmer and more personal in others. On church and ministry sites we've built, the register of the language matters as much as its accuracy: a stiff, corporate tone reads as untrustworthy in a context where community trust is everything.

Structural decisions, not just strings

Multilingual support isn't only a translation table. Layouts need to accommodate text that expands or contracts across languages, forms need labels that don't assume Latin-only input, and content models need a 'no translation yet' state that degrades gracefully instead of showing broken placeholders.