Designing Digital Products for Africa During a Pandemic: Lessons from the Frontlines

By Oluwabukunmi Victor Babatunde

The notifications started around 2 AM on March 30th. Our product’s server load had tripled overnight. Users who normally accessed our platform during business hours were suddenly online at all times. Nigeria’s first COVID-19 lockdown had begun, and the digital transformation that should have taken five years was happening in five days.

As a product designer working in Lagos, I have a front-row seat to Africa’s forced digital acceleration. What I’m witnessing challenges everything I thought I knew about building technology for African markets and is revealing critical lessons that will shape how we design digital products long after this pandemic ends.

The Bandwidth Reality Nobody Designed For
The first product failure came within days of the lockdown. A promising edtech platform launched with beautiful HD video lessons, perfectly optimised for broadband internet. They were offline within a week.
The problem wasn’t their technology. It was their assumptions.

Nigerian internet users consume data like people in water-scarce regions consume water: carefully, strategically, and aware that it might run out. Now that millions of students suddenly need online education, families are facing impossible choices. Do we use our limited data for video lessons, or do we preserve it for the father’s remote work meetings that pay the bills?

Products designed in London or San Francisco assume bandwidth is essentially free. In Lagos, Accra, or Nairobi, bandwidth is a budgeted resource. Right now, this isn’t a minor inconvenience; it’s the difference between products that work and products that fail.

The platforms that are succeeding understand this instinctively. They’re offering downloadable content. They’re compressing aggressively. They’re providing text alternatives to video. They’re letting users control exactly how much data they consume. These aren’t features; they’re fundamental design decisions that are determining survival

When “Mobile-First” Isn’t Enough
Before COVID-19, “mobile-first design” was already the mantra in African tech. But the pandemic is revealing that we’ve been thinking about mobile wrong.
Most designers interpret “mobile-first” as “make sure it works on phones.” What we’re missing is understanding which phones, which operating systems, which versions, and under which conditions.

Over the past three months, I’ve watched families share a single smartphone among four children, trying to access school lessons. I’m seeing essential workers access work platforms on phones that are three, four, sometimes five years old, running Android versions that developers stopped supporting years ago. I’m observing people in areas with unreliable electricity carefully ration their phone’s battery life, forced to choose which apps are worth the power consumption.

Products designed with the latest iPhone or flagship Samsung in mind simply aren’t working for these users. The successful ones are the ones achieving massive adoption right now—they are being designed for the Nokia 3310 and are delighted when users have something better.

This means aggressive optimisation: smaller app sizes, minimal background processes, offline-first functionality, and interfaces that work without the fancy animations that drain batteries. It means testing on actual devices people own, not the devices designers wish they owned.

The USSD Renaissance
Perhaps the most surprising development I’m witnessing is the resurgence of USSD—Unstructured Supplementary Service Data, the text-based menu system accessed by dialling shortcodes like *123#.
Three months ago, USSD felt like legacy technology. Apps were the future; USSD was for people who hadn’t caught up yet. COVID-19 is reversing this perception overnight.

Now that data is expensive and unreliable, USSD is becoming an essential infrastructure. Banks, utilities, and service providers that maintained USSD channels as afterthoughts are suddenly finding them carrying the majority of their traffic. Small businesses that never considered USSD are hurriedly launching *XXX# codes for orders and payments.

The lesson isn’t that apps are wrong. It’s that assuming everyone can or will use apps is wrong. The products that are serving Africa best right now are offering multiple interfaces: a sophisticated app for users with reliable data, a simplified app for those with limited connectivity, a mobile web version for those who don’t want to install anything, and a USSD option for when all else fails.

This redundancy seems inefficient to designers trained in Silicon Valley minimalism. But in markets where connectivity is unreliable, redundancy isn’t a waste, it’s reliability.

The Voice Interface Nobody Expected
Another unexpected pattern is emerging: voice. Not voice assistants or AI-powered voice interfaces, but something simpler—WhatsApp voice notes.
Over the past few months, I’ve been watching customer service teams pivot entirely to voice notes. Text support tickets are dropping while voice note enquiries are exploding. Why? Because many users, particularly older users suddenly forced online, are finding it faster to speak than to type, especially in local languages where phone keyboards are clumsy.

Smart products are adapting. They’re training support teams to handle voice enquiries efficiently. They’re recognising that in markets with multiple languages and varying literacy levels, voice is often the most natural interface, even when sophisticated alternatives exist.

This isn’t about implementing Alexa or Google Assistant. It’s about recognising that people communicate naturally through voice, and forcing them to type when they’d rather speak creates unnecessary friction.

Designing for Intermittent Everything
The pandemic is making visible what has always been true: in much of Africa, connectivity, electricity, and device availability are intermittent resources, not constant utilities.
The products that are thriving are designing for this intermittency from the ground up:

Intermittent connectivity: They’re syncing aggressively when online, working fully when offline, and handling the transition between states gracefully. Users can start a task on unreliable connectivity, lose their connection entirely, continue working, and have everything sync seamlessly when connectivity returns.

Intermittent power: They’re minimizing battery drain, warning users before performing power-intensive operations, and saving progress constantly so a dead battery doesn’t mean lost work.

Intermittent device access: They’re making it easy to use the same account on multiple devices, recognising that people often share devices or switch between borrowed phones.

These aren’t features that can be added later. They’re architectural decisions that need to be baked into products from conception.

The Cultural Context That Code Can’t Capture
But perhaps the deepest lesson emerging from these months goes beyond technical design. It’s about cultural context.
Digital products that are succeeding right now understand that technology doesn’t exist in a vacuum. A beautifully designed telemedicine app is useless if it doesn’t account for the fact that many Africans trust traditional healers as much as or more than Western medicine. A sophisticated e-learning platform is failing if it assumes nuclear families with dedicated study spaces when the reality is extended families in shared compounds.

The most successful products are demonstrating cultural intelligence: they understand family dynamics, trusted authority figures, communication norms, and privacy expectations that differ significantly from Western assumptions.

For instance, payment platforms that allow group contributions and bill splitting aren’t just convenient; they’re aligning with communal financial practices. Education platforms that enable offline content sharing are recognising that African students have always learned collaboratively, sharing notes and helping each other rather than studying in isolation.

What This Means for Africa’s Digital Future
As we continue navigating this pandemic, and we still have months ahead of us, there’s a temptation to view these adaptations as temporary measures for a temporary crisis. This would be a mistake.
COVID-19 hasn’t created the challenges African digital products face. It’s revealing them. Bandwidth scarcity, device diversity, intermittent connectivity, and cultural context have always been the reality of African markets. The pandemic is simply making them impossible to ignore.

The products succeeding right now will continue succeeding after the pandemic because they’re being designed for Africa’s actual conditions, not idealised versions of them. They’re recognising that constraints aren’t obstacles to work around, they’re the design brief.

Moving forward, the question for anyone building digital products for African markets shouldn’t be “How do we make our Western solution work in Africa?” It should be “How do we design specifically for African realities from day one?”

This means:

● Starting with the minimum viable connection, not the ideal one
● Designing for the oldest device in significant use, not the newest one
● Assuming intermittency in everything: power, connectivity, device access
● Building multiple interface options: app, mobile web, USSD, voice
● Understanding cultural context as deeply as technical architecture
● Testing with real users in real conditions, not lab simulations
Lessons for Designers
For my fellow designers building for African markets, these past few months have taught us that empathy isn’t enough. We can’t truly understand our users’ reality by reading about it or conducting occasional field studies. We need to design with constant awareness of:
The infrastructure we take for granted might not exist. That beautiful animation requires processing power and battery life that someone might not have. That video tutorial consumes data that someone can’t afford. That cloud-sync feature assumes connectivity that someone lacks.

The device in our hand isn’t the device in theirs. Test on the phones people actually own, running the operating systems they actually use, under the conditions they actually experience.

The solution that works elsewhere might not work here. Africa doesn’t need African versions of Western products. It needs products designed from scratch for African realities.

Constraints force creativity. The need to work on limited bandwidth, old devices, and intermittent connectivity doesn’t limit innovation; it focuses it. Some of the most elegant solutions I’m seeing are emerging from designing for constraints.

Looking Ahead
We don’t know how long this pandemic will last or what the world will look like when it ends. But we do know that the digital products being built right now are revealing a fundamental truth: Africa doesn’t have a technology problem. It has a design problem.
We have the creativity, the engineering talent, and the entrepreneurial drive. What we’ve often lacked is design thinking that starts with African reality rather than trying to retrofit African markets into Western assumptions.

The pandemic is forcing a reckoning with this reality. Products that ignore it are failing. Products that embrace it are succeeding, often spectacularly.

As we build Africa’s digital future, both during this crisis and after, we can’t forget these lessons. The designers who will shape the next decade of African technology won’t be those who build the most sophisticated products. They’ll be those who build products that actually work, for the people who actually need them, under the conditions that actually exist.

COVID-19 isn’t teaching us anything new. It’s just making visible what some of us have always known: Africa doesn’t need pity or simplified versions of Western technology. It needs technology designed specifically for the African reality, not despite the constraints, but because of them.

The question isn’t whether we can build for Africa. It’s whether we’re willing to design differently than we’ve been taught. These past few months have proven that when we do, remarkable things become possible.

And we’re only just getting started.

Oluwabukunmi Victor Babatunde is a product designer and AI implementation specialist based in Lagos, Nigeria. He focuses on building digital products for African markets, with expertise in user-centred design and technology adaptation for emerging economies.