Designing technology truly adapted to Senegal

When we talk about digital transformation in Africa, one reflex often comes up: take a model that works in the United States, Europe or Asia, translate it into French, adapt it slightly to the local context, and then try to deploy it.

This approach may work in some cases.

But it quickly reaches its limits.

Because a technology is never independent of its environment. It is the product of assumptions about infrastructure, income, habits, behaviors, means of payment, literacy levels, trust, regulations, and uses.

An application designed in San Francisco implicitly assumes that the user has a permanent internet connection, a relatively powerful smartphone, a bank account or payment card, an email address, is literate, and is able to navigate a digital interface independently.

These assumptions are not necessarily valid in Senegal.

The question is therefore not:

How can a technology designed elsewhere be adapted for Senegal?

The question should be:

If this technology were to be invented today in Senegal, based on Senegalese realities, what would it look like?

This difference in perspective is fundamental.

1. Start with the field before starting with the technology.

Digital transformation is too often approached in the wrong order.

We begin with:

Technology → application → problem finding.

We should start by:

Reality → problem → behaviors → constraints → opportunity → solution → technology.

• Before developing an application for a merchant, for example, you need to understand how that merchant actually works.
• How does he take his orders?
• How does he keep track of his accounts?
• How does he manage his debtor clients?
• How does he pay his suppliers?
• How does he receive his payments?
• What does it do when the internet isn't working?
• Who does he trust?
• What does it do when it doesn't understand an interface?

These questions are far more important than the initial choice between React Native, Flutter, or another technology.

Technology must bethe consequence of the problem, not the starting point.

2. Design a frugal architecture.

The word "frugal" should not be understood as "poor technology".

Frugal architecture is architecture thatintelligently uses available resources and minimizes unnecessary dependencies.

It is particularly relevant in a context where connectivity, device power and data cost can vary greatly.

Offline-first: consider the network as an intermittent resource

In many Western systems, the application is designed according to the following paradigm:

Internet access is available. If the internet goes down, the system is down.

In a Senegalese context, it may be more relevant to reverse this logic:

The system must function even when the network is unavailable.

Architecture can therefore prioritize:

• stockage local ;
• embedded SQLite;
• IndexedDB ;
• WEIGHT;
• delayed synchronization;
• differential synchronization;
• optimistic management of states;
• conflict resolution;
• CRDT when the use case justifies it.

The user must be able to continue their work.

Synchronization becomes a secondary operation, performed when connectivity becomes available again.

This change appears to be technical.

In reality, it completely transforms the user experience.

3. Bandwidth must be considered as a design constraint.

In an environment where mobile data represents a real cost to the user, unnecessarily downloading several tens or hundreds of megabytes to use an application is a poor architectural decision.

An application designed for Senegal should ask itself:

How much does it cost my user to use my application?

Therefore, priority should be given to:

• lightweight payloads;
• compression ;
• cache local ;
• differential synchronization;
• optimized images;
• asset limitation;
• progressive loading;
• reduced bundles;
• efficient APIs;
• compact formats when relevant.

Performance is therefore not solely a matter of user experience.

It becomes a question of economic accessibility.

4. The smartphone should not be the only point of entry.

It would also be dangerous to confuse:

digitalisation = application smartphone.

Senegal has a much larger technological ecosystem.

A truly inclusive architecture can combine:

Smartphone + lightweight web + PWA + USSD + SMS + voice + human agent.

The user should not be required to have the most modern terminal to access an essential function.

For certain critical operations, USSD or SMS may be more relevant than a sophisticated application.

For others, voice may be the best interface.

The principle is simple:

The channel should adapt to the user, not the other way around.

5. Moving from "mobile-first" to "human-first".

Even the concept of mobile-first deserves to be superseded.

The real question should be:

Human-first: how does this person wish to accomplish this task?

Sometimes, the answer will be an app.

Sometimes it will be WhatsApp.

Sometimes, a voicemail.

Sometimes, a phone call.

Sometimes, a field agent equipped with an application.

And sometimes a combination of all these elements.

This is particularly important in sectors where trust plays a major role.

6. Voice and national languages ​​can become a technological interface.

A technology can be technically excellent and remain inaccessible if its interface constitutes a barrier.

A text-only interface in French requires a certain level of linguistic and digital proficiency.

For some people, a voice interface can be much more natural.

Artificial intelligence opens up a particularly interesting possibility here.

Imagine being able to ask verbally:

« How much did I sell today? »

and receive the answer immediately.

Or save:

« Moussa bought three bags of rice from me and he still owes me 25,000 francs. »

AI could transform this interaction into structured data.

This opens up considerable opportunities for:

• informal trade;
• agriculture ;
• education ;
• services publics ;
• micro-enterprises;
• finance ;
• health ;
• administrative management.

But for this revolution to be truly inclusive, systems will gradually need to better understand national languages, accents, language mixtures, and local expressions.

African AI must not only speak French. It must understand Africa.

7. Design for the real economy, not just for the formal economy.

This is probably one of the areas where copying and pasting foreign models is most problematic.

A large part of Senegal's economic activity operates through mechanisms that do not correspond to the classic Western business model.

There are:

• informal trade;
• cash payments;
• Mobile Money ;
• credit between individuals;
• tontines ;
• family networks;
• intermediaries;
• informal suppliers;
• joint and several guarantee;
• multiple activities of the same entrepreneur.

It would therefore be dangerous to design a product based on the assumption:

business = registered company + bank account + credit card + monthly subscription + electronic invoice.

The local model can be very different.

Appropriate technology mustto gradually digitize existing realities, rather than asking the user to immediately change their operating mode.

8. Mobile Money should be an architectural component, not a feature added at the end.

In many Western products, payment is designed around:

Credit card → Stripe → subscription.

This model cannot be considered universal.

In Senegal, the financial architecture must natively integrate the realities of Mobile Money and agent networks.

This means, in particular, thinking about:

• micro-transactions ;
• transactional payments;
• webhooks ;
• idempotence ;
• asynchronous reconciliation;
• management of failed transactions;
• installment payments;
• refunds;
• financial reconciliation.

Technology must be designed around theuser's actual cash flow.

9. Trust must become a feature of the system.

There is another dimension often absent from Western architectures: the relational dimension.

In many African contexts, trust is not simply about:

« I have accepted the general terms and conditions of use. »

It could come from:

• the person who recommended the service to me;
• the agent I know;
• the merchant's reputation;
• my community;
• my professional network;
• someone who can explain how it works.

This means that the human network can become a component of the architecture.

A platform can therefore be:

Software + AI + agent network + community + reputation mechanisms.

10. The "Phygital" model: not opposing digital and human

Digitalization does not necessarily mean eliminating intermediaries.

In certain contexts, the correct model is:

Digital + Physical = Phygital.

An agent can:

• assist with registration;
• explain the service;
• perform the onboarding;
• to support the user;
• resolve exceptions;
• to perform certain operations;
• to become a trusted intermediary.

Technology automates what needs to be automated.

Human intervention occurs where trust, judgment, or guidance are needed.

This is often more realistic than a "100% digital self-service" model.

11. Digital sovereignty does not mean building everything yourself.

Another pitfall must also be avoided.

Building a Senegalese technology does not mean recreating:

• operating systems;
• databases;
• the clouds;
• les frameworks ;
• the fundamental models of AI;
• Internet protocols.

Digital sovereignty does not meaneverything produced locally.

It means rather:

Knowing what is strategic, mastering what needs to be mastered, controlling one's data and being able to evolve one's system without totally depending on a supplier or foreign infrastructure.

This notably involves considering:

• open source ;
• portability;
• open standards;
• reversibility;
• data governance;
• regional accommodation where relevant;
• security ;
• mastery of architectures.

The correct strategy is therefore:

Utilize the best of global technology + master strategic layers + build local applications that address local problems.

12. Comparison: imported model vs. contextualized model

13. Transforming Senegal's constraints into competitive advantages

This may be where the greatest opportunity lies.

We tend to view certain realities as handicaps:

• imperfect connectivity;
• informal economy;
• linguistic diversity;
• low purchasing power;
• heterogeneous infrastructures;
• importance of the human network;
• multiplicity of payment methods.

But each of these constraints can become a source of innovation.

This is a fundamental reversal of reasoning.

Instead of asking:

« How can we eliminate our constraints? »

The question is:

« How can we design technologies that become better precisely because they have to work within these constraints? »

14. Senegal can become a technological laboratory

The real objective should not be to build products "only for Senegal".

It should be about building technologiesborn in Senegal but capable of addressing broader African problems.

The process could be:

Enlarge

This approach can produce something much more interesting than a simple local adaptation of a foreign product:

a technology designed from the ground up for emerging markets.

15. A new design philosophy: African-Native Technology

We need a change of mindset.

For a long time, technological innovation followed a relatively simple model:

Silicon Valley → Europe → Africa

Africa was often considered an adoption market.

But another model is possible:

African realities → innovation → technology → African market → global market

Some solutions designed to work in constrained environments can even become extremely relevant elsewhere.

An application capable of operating with low bandwidth, multiple languages, split payments, and intermittent connectivity can find markets far beyond Senegal.

Local constraints can therefore become a global advantage.

Conclusion: Do not build a miniature version of the Western world

The real issue is not to build a Senegalese version of an American application.

It is about building something different.

A technology that includes:

• how Senegalese people live;
• how they work;
• how they pay;
• how they communicate;
• how they trust;
• how they learn;
• how they use their phone;
• how they interact with the administration;
• how the informal economy actually works;
• and how local infrastructure works.

Technology must start from this reality.

Offline-first. Mobile-first, but above all, human-first. Voice-first when it makes sense. Multilingual. Mobile Money native. Phygital. Frugal. Resilient. Sovereign. And designed to evolve.

Senegal does not need to copy Silicon Valley.

He can learn from Silicon Valley, Europe, Asia and the rest of the world — while developing his own way of designing technology.

And perhaps that's where the real opportunity lies:

No longer just adapting technology to Senegal. Designing, from Senegal, technologies adapted to African realities.