7 years building for constraint: Lessons from emerging market tech

In global technology conversations, scalability is almost always framed as a backend challenge. How do systems handle millions of concurrent users? How do databases scale horizontally? How do services remain available under peak load? These are important questions. But they assume something that most of the world’s next billion internet users do not have: ideal […]

In global technology conversations, scalability is almost always framed as a backend challenge. How do systems handle millions of concurrent users? How do databases scale horizontally? How do services remain available under peak load? These are important questions. But they assume something that most of the world’s next billion internet users do not have: ideal conditions.

Across Africa, South Asia, and parts of Latin America, the next wave of digital growth is not constrained by ambition or demand. It is constrained by the devices people use, the networks they rely on, and the economic trade-offs they make every time they go online. According to the International Telecommunication Union, over 2.6 billion people globally remain offline, with the majority concentrated in developing regions. The GSMA estimates that Sub-Saharan Africa alone will add hundreds of millions of new mobile internet users by the end of this decade. There are already over 700 million mobile subscriptions across Sub-Saharan Africa (GSMA, 2023), and in several African countries, 1GB of mobile data costs more than 5% of average monthly income (Alliance for Affordable Internet, 2023).

These users will not arrive under ideal conditions. And that is where the real lessons in scalability begin.

I know this because I have spent the past seven years building for exactly these conditions. As the Founder and CEO of Ocean Trends Digital Limited, I have designed and shipped multiple software platforms across fintech, social commerce, loan management, and utility management. Every one of them was built for users who operate on low-end devices, intermittent connectivity, and tight data budgets. The engineering decisions I make every day are shaped not by what is theoretically optimal, but by what actually works when the network drops, the device runs out of memory, and the user has already paid more than they should have for the data to load my application.

 

The Frontlines of Scale Are Not in the Cloud

From the outside, building scalable systems appears to be a server-side challenge. Distributed architectures, microservices, and auto-scaling infrastructure are seen as the primary tools for growth. And they are important. But in emerging markets, the first point of failure is rarely the server. It is the user environment.

The Alliance for Affordable Internet reports that in several African countries, 1GB of mobile data can cost more than 5% of average monthly income, far exceeding international affordability benchmarks. Data from the World Bank shows that broadband access remains deeply uneven, particularly in rural communities. Low-end Android devices with limited memory and processing power remain the dominant hardware. Intermittent or slow network connectivity is the norm, not the exception.

In this context, an application that assumes constant connectivity or high device performance is not just inefficient. It is unusable. And unusable software does not scale, regardless of how elegant its backend architecture might be.

I learned this lesson early when building EarnIT, our social commerce and fintech platform. The first version of the application loaded beautifully on the devices my engineering team used for testing. It was sluggish and unreliable on the devices our actual users owned. The gap between our test environment and our users’ reality was the first and most important engineering problem I had to solve. Not database optimisation. Not API throughput. Device performance and network resilience.

 

What the Frontlines Reveal About Real Scalability

Working within constrained environments for seven years has exposed a fundamental truth: scalability is not about how systems perform under ideal conditions. It is about how they behave under constraint. This is where many otherwise well-engineered systems fail when introduced into emerging markets. They are built for environments that do not exist locally.

The lessons from the frontlines are consistent across every sector I have worked in, from fintech to loan management to utility management. Accessibility determines adoption: an application that cannot load quickly on a low-end device will never reach scale, regardless of its backend capabilities. Reliability builds trust faster than features: users prioritise systems that work consistently over those that offer advanced functionality but fail intermittently. Cost-awareness shapes behaviour: every megabyte consumed has a real economic implication for the user, and data efficiency is not an optimisation exercise but a survival requirement. And offline capability is not optional: systems must function, even partially, without a constant network connection, using queuing, local caching, and sync-on-reconnect as foundational architecture rather than edge-case handling.

Each of these principles has directly shaped how I build products at Ocean Trends Digital. When I designed the wallet system for EarnIT, I had to ensure that a user who initiates a transaction during a connectivity gap does not lose their money or receive a confusing error. The system queues the transaction locally, validates it when connectivity returns, and provides the user with a clear status update at every stage. That is not a feature I added for convenience. It is a survival mechanism for a platform operating in an environment where network interruptions happen multiple times per day.

What appears in analytics dashboards as ‘poor retention’ is often a reflection of poor alignment between product design and user context. Scalability is not just a technical failure. It is a design failure.

 

The Hidden Cost of Ignoring Context

One of the most common mistakes made by companies expanding into emerging markets is assuming that what worked in developed markets will translate directly. It rarely does.

Applications built with assumptions of persistent high-speed connectivity, high device performance, and always-on background processes often experience high uninstall rates and low engagement when deployed in constrained environments. What appears in analytics dashboards as “poor retention” is often a reflection of poor alignment between product design and user context.

I have seen this pattern from the other direction. International SaaS products that enter the Nigerian market with minimal localisation consistently underperform relative to locally-built alternatives that were designed for the environment from the outset. The international product may have superior feature sets, better documentation, and stronger brand recognition. But if it consumes too much data, crashes on low-memory devices, or fails silently when the network drops, users will abandon it for the local alternative that simply works.

 

Lessons From Building Across Multiple Sectors

At Ocean Trends Digital, I have built platforms spanning fintech, social commerce, loan management, and utility management. Each sector has its own technical requirements and user expectations, but the constraint-driven engineering principles remain constant across all of them.

In fintech, the defining challenge is transaction reliability under network uncertainty. When a user sends money through EarnIT and the payment provider’s API returns a timeout rather than a clear success or failure, the system has to make a decision. Does it retry? Does it mark the transaction as pending? Does it alert the user? Getting this wrong means either the user loses money or the platform absorbs a financial loss. I built a reconciliation engine that continuously compares our internal ledger against payment provider records, identifies discrepancies, and resolves them automatically where possible. That engine exists because the network environment demanded it.

In loan management, the challenge centres on financial data integrity and auditability. Our platform, Bimzukash, handles loan application processing, credit assessment, disbursement tracking, repayment scheduling, and default management. Every financial transaction must be recorded with absolute precision, because a discrepancy in a borrower’s ledger is not just a data error. It is a trust-destroying event that can lose a customer permanently. The system uses the same multi-ledger architecture I developed for EarnIT, ensuring that every credit, debit, and adjustment is traceable through a complete audit trail.

In utility management, through BimzuWater, the challenge shifts to data integrity across distributed operations. Water production and distribution businesses need accurate billing, inventory tracking, and maintenance records. When field operators enter data from locations with poor connectivity, the system has to validate entries locally, prevent duplicates, and reconcile once connectivity is restored.

 

Infrastructure Is Not Just Digital

Another key lesson from the frontlines is that infrastructure in emerging markets extends beyond software. In financial services, for example, agent networks often play a more critical role than mobile applications. Research from the CGAP (Consultative Group to Assist the Poor) shows that agent-assisted models significantly increase adoption and trust in digital financial services, particularly among first-time users.

Platforms that succeed in emerging markets are those that bridge the gap between digital systems and physical access points. This hybrid approach, combining digital efficiency with physical reach, is essential for true scalability in contexts where digital literacy is still developing and trust in purely digital transactions is limited.

This is something I have observed directly through EarnIT. Users who receive their first payout successfully, quickly, and without friction are dramatically more likely to trust the platform with subsequent transactions. The engineering behind that first payout, the automated queue, the provider failover, the real-time status updates, is invisible to the user. But it is the moment that earns their trust. And in emerging markets, trust is not a marketing outcome. It is an engineering outcome.

 

Engineering for Resilience, Not Perfection

In high-resource environments, engineering often prioritises optimisation and feature expansion. In emerging markets, the priority shifts to resilience. This means building systems that function under poor network conditions, recover gracefully from failures, minimise data usage and device strain, and provide clear, simple user experiences that do not assume prior digital literacy.

Resilience is what allows systems to remain usable when conditions are far from ideal. And in many emerging markets, those conditions are not edge cases. They are the norm.

At Ocean Trends Digital, resilience is not a quality we add at the end of development. It is the foundation on which every product is built. When I design a new system, the first questions I ask are not about features or user interface. They are about failure modes. What happens when the network drops mid-transaction? What happens when the payment provider returns an ambiguous response? What happens when the user’s device runs out of memory while processing a critical operation? The answers to these questions determine the architecture before a single feature is planned.

 

What This Means for the Next Billion Users

The next decade of digital growth will not be driven by users upgrading to better devices or faster networks overnight. It will be driven by systems that work effectively within existing constraints. According to the GSMA, Sub-Saharan Africa’s mobile internet penetration is expected to reach 40% by 2025, up from roughly 28% in 2021. That growth represents hundreds of millions of new users, and the vast majority of them will arrive on low-end devices with intermittent connectivity and tight data budgets.

I have spent seven years building products for emerging market constraints at Ocean Trends Digital. Three live platforms, each engineered for resilience over perfection, accessibility over features.

The builders who will capture this market are not the ones with the most features or the most funding. They are the ones whose engineering is calibrated to real conditions rather than ideal ones. They are the ones who treat resilience as a core architectural principle rather than an afterthought. They are the ones who understand that, in emerging markets, your infrastructure is your product.

Emerging markets are not edge cases. They are the future majority. And the lessons from building for them are not niche technical insights. They are the blueprint for the next generation of globally scalable technology.

I have spent seven years learning these lessons by building products that real people depend on. The engineering instincts that emerge from this work, the obsession with reliability over features, with resilience over perfection, with trust over growth, are not just applicable to African markets. They are applicable everywhere that technology meets real-world constraint. And that, increasingly, is everywhere.

True scalability is not measured by how systems perform at their peak, but by how reliably they serve users at their most constrained. The builders who understand this will define the next decade of global technology.

Damilare Ajiboye is the Founder and CEO of Ocean Trends Digital Limited, a product-led technology company building scalable software solutions across fintech, social commerce, loan management, and utility management. He is based in London, United Kingdom.