# Interface Design for Low Digital-Literacy Users in DRC
Summary: In the DRC, an app or website designed for someone comfortable reading French and navigating menus locks out a real share of the market — the fix is recognizable icons, short flat flows instead of nested menus, voice or local-language support, and testing with actual users rather than the product team.
A market problem, not just an accessibility one
When a Congolese business or public agency commissions an app, the default is to copy the standards seen on Western apps: text-based menus, long forms, technical French vocabulary. The problem is that this default does not match a significant share of the actual end users in the DRC.
The country had roughly 34.7 million internet users at the end of 2025, an internet penetration rate of 30.5% according to DataReportal, and the regulator ARPTC measured mobile internet penetration at 33% at the same date (ARPTC). In other words, more than two-thirds of the Congolese population is still offline, and among those who are online, many are only just discovering the smartphone — whose cost remains a major barrier to adoption.
On top of that sits literacy itself. According to UNESCO Institute for Statistics data published by the World Bank, the adult (15+) literacy rate in the DRC was 68.5% in 2023, with a sharp gender gap: 85.4% for men versus 53.8% for women (World Bank / UNESCO UIS). In September 2023, the Ministry of Social Affairs put the number of illiterate Congolese at around 23 million (Forum des As). Someone who can read a bit of French is often still uncomfortable with technical vocabulary, a nested menu structure, or a form to fill out unassisted. Digital literacy — knowing how to navigate an interface, read an icon, recover from an input error — is a distinct barrier from literacy itself, and it's the one an interface designer actually has to solve.
The GSMA Mobile Gender Gap Report 2025, covering low- and middle-income countries as a whole, lists literacy and digital skills among the top barriers to mobile internet adoption for people who are aware of it — alongside handset affordability.
What makes an interface unusable for someone who isn't comfortable with it
Microsoft Research's work on mobile interfaces for novice and low-literacy users is blunt on one point: purely text-based interfaces — electronic forms, SMS, standard USSD menus — are often unusable by first-time low-literacy users (Medhi et al.). The specific failure points identified are:
- Hierarchical menus (submenu inside submenu) require memorizing an abstract path — users lose track by the second level.
- Soft keys ("press 2 to continue") assume a number can be mapped to an invisible action.
- Non-numeric input fields (name, address, reason for request) create heavy friction if spelling or typing is a struggle.
- Specialized vocabulary ("validate," "sync," "settings") stays opaque to anyone unfamiliar with digital tools, all the more so if they mostly speak Lingala or Swahili day to day.
These are exactly the components found in a poorly designed banking USSD app or a sign-up form copied from a European template. The study, run with 90 low-literacy participants in India, Kenya, the Philippines, and South Africa, concludes that text interfaces (forms, SMS, USSD) are unusable by first-time low-literacy users and error-prone even for literate novices.
What actually works: research-backed principles
A peer-reviewed study published in the Proceedings of the ACM on Human-Computer Interaction lays out concrete guidelines for smartphone apps that are inclusive of low-literate users (ACM): prioritize clear graphical cues, voice annotations, and local-language support, and avoid complex navigation and input.
Researchers who spent more than 700 hours in the field with 570 low-literacy participants across India, the Philippines, and South Africa established design principles combining voice, video, and graphics; their evaluations showed these non-textual designs were strongly preferred over standard text interfaces and that first-time, non-literate users could navigate them meaningfully (Microsoft Research). In Medhi et al.'s study, for mobile banking, task completion was highest with a graphical interface (Medhi et al.).
Translated into design principles for a product aimed at the Congolese market, that looks like this:
| Principle | Concrete application in DRC |
|---|---|
| Icons before text | Action buttons shown as a pictogram (a banknote for "pay," a phone for "call") rather than a label alone |
| Flat flow, not hierarchical | 1–2 screens maximum between the home screen and the action, no nested submenus |
| Audio and short video | A "listen" button that reads the instruction aloud in French, Lingala, or Swahili |
| Local language by default | A visible language selector on the very first screen, not buried in settings |
| Strong visual confirmation | Immediate feedback (color, sound, animation) after every successful or failed action |
| Tolerance for error | No form that blocks everything because a single field was filled in wrong |
The mobile money case: DRC already has part of the answer
The DRC offers a real-world example of what works, through mobile money. At end-2025, ARPTC counted 34.3 million active mobile money subscriptions, including 15.4 million at M-Pesa (Vodacom), 11.1 million at Airtel Money, and 7.7 million at Orange Money (ARPTC) — roughly as many as there are mobile internet subscriptions. These services rely heavily on USSD menus (for example *501# at Airtel Money for transfers to other operators), which work on any phone without data: that's a large part of their success with people who have no smartphone or data plan.
That's an important signal for any Congolese business building an app: the market isn't waiting to be taught to read technical French — it's waiting to be spoken to in a language and format it already understands.
The business case behind inclusive design
This isn't just an ethics or accessibility question — it's a measurable growth lever. According to a GSMA report, targeted policy and infrastructure reforms could add 9.7 million more unique mobile internet users and CDF 9.8 trillion to GDP by 2029. Part of that growth only materializes if the interfaces of digital services — banking, e-commerce, government, health — are actually usable by people who are new to smartphones, not just by the 30% who are already online and comfortable with written text.
For a business trying to reach that market — a fintech, an e-commerce platform, or an agency digitizing a public service — designing for the low digital-literacy user from the start isn't a "nice to have" bolted on at the end of a project. It's an interface architecture decision made before the first mockup screen, backed by user testing in the field rather than with the product team. That's the approach our UI/UX design service follows: starting from the real usage patterns of the intended users rather than an imported template.
FAQ
Does an interface for low digital-literacy users have to remove all text?
No. The point is to never make text the only way to understand an action: every button or critical step should have a visual (icon, color, position) or audio cue that works even if the text isn't read or understood.
Is French enough for an app aimed at the general Congolese public?
Not always. With adult literacy at 68.5% in 2023 (53.8% among women) and four national languages (Lingala, Swahili, Kikongo, Tshiluba), adding at least one local language — ideally with audio support — widens the share of users likely to complete an action unassisted.
Should a business use a native app or USSD to reach low-literacy users in DRC?
It depends on network coverage in the target area and the device profile. USSD remains relevant where mobile internet is unreliable or absent (33% mobile internet penetration nationally at end-2025, per ARPTC), but it inherits the same hierarchical-menu limitations described above — so it needs the same short flows and simple vocabulary, not a generic spec ported over as-is.
How can a business tell if an interface is actually usable by this audience without a big research budget?
Testing with 5 to 8 representative users (not colleagues or tech-savvy friends), observed completing a real task unassisted, usually surfaces the major blockers well before a formal usability audit becomes necessary.
Sources
- DataReportal — Digital 2026: Democratic Republic of the Congo
- ARPTC — Mobile market observatory Q4 2025
- World Bank (UNESCO UIS data) — Adult literacy rate, DRC
- Forum des As — DRC: More than 23 million Congolese remain illiterate
- GSMA — Mobile Gender Gap Report 2025 (press release)
- GSMA — Digital Reforms Could Connect 9.7 Million More Congolese and Add CDF 9.8 Trillion to GDP by 2029 in DRC
- Microsoft Research — Designing Mobile Interfaces for Novice and Low-Literacy Users (Medhi et al.)
- Microsoft Research — UIs for Low-Literate Users
- ACM — Actionable UI Design Guidelines for Smartphone Applications Inclusive of Low-Literate Users
- Airtel Money RDC — interoperability via *501# (X)