Mobile Application Development #7 in Kinshasa: Android, iOS & Mobile Money | Blog

# Mobile Application Development in Kinshasa: Android, iOS & Mobile Money

Summary: in the DRC, a mobile app should be built for Android first — it runs on more than 84% of phones in Kinshasa and Lubumbashi alike — and only becomes genuinely useful to a business once it natively supports Airtel Money, M-Pesa, and Orange Money from version one, since those three operators alone account for over 34 million active mobile money subscriptions nationwide.

Most people bringing a project to Kinshasa show up with the same question: "Android or iOS?" That's the wrong question to start with. The real question on this specific market is: "how will my app move money in and out of my users' phones?" The technology stack follows naturally once that's answered.

Android dominates by a wide margin, iOS stays a profitable niche

According to StatCounter, Android accounts for 84.24% of mobile operating systems used in the Democratic Republic of Congo (July 2026), against 15.7% for iOS. That dominance comes down to affordable handset brands like Tecno, Infinix, and itel (all under the Transsion group), which cover most of the sub-$100 smartphone market across the continent.

In practice, for any consumer-facing app — delivery, transport, e-commerce, financial services — Android isn't an option, it's the mandatory starting point. Skipping optimization for entry-level devices (limited RAM, small storage, older Android versions) means excluding a meaningful share of Congolese users right from launch.

That said, iOS shouldn't be dismissed. The remaining 15.7% often maps to a professional clientele, the diaspora, and higher-income users — exactly the segment with the budget for a premium service, a subscription, or a B2B product. For a niche app aimed at executives, importers, or professionals, ignoring iOS can cost real revenue per user, even with lower volume.

The real technical challenge isn't the code — it's Mobile Money

A market fought over dollar by dollar

Mobile money is no longer a nice-to-have feature in the DRC — it's the country's payment infrastructure. In the fourth quarter of 2025, ARPTC (the Congolese telecom and postal regulator) counted 34.3 million active mobile money subscriptions, a 30.6% penetration rate of the population, with the sector generating close to $647.9 million in revenue.

The fight is essentially a three-way race:

Operator	Market share (transactions)	2025 revenue
M-Pesa (Vodacom)	43.77%	$207.1 million (+23%)
Airtel Money	41.30%	$194.8 million (+42%)
Orange Money	14.44%	—
Afrimoney	0.49%	—

Two takeaways for a founder here. First, none of the three operators has an overwhelming lead in transaction volume: an app that only supports M-Pesa leaves out a substantial share of the addressable market. Second, Orange Money is the one to watch on the subscriber side — its active subscriber base jumped over 50% in a single year (7.7 million active subscribers by the end of 2025), even though its transaction market share is still more modest.

Interoperability: regulation on paper vs. reality on the ground

The Banque Centrale du Congo (BCC) governs this market through several instructions: Instruction n°24 (issuance of electronic money and approval of electronic money establishments), Instruction n°42 (rules applicable to electronic payment systems), and Instruction n°58, which mandates interoperability of electronic payment systems through the national switch. On paper, a transfer between an Airtel Money account and an M-Pesa account should be seamless. In practice, the developer experience is still fragmented: each operator exposes its own API, with its own merchant credentials, its own callback formats, and its own validation timelines.

How to actually integrate Airtel Money, M-Pesa, and Orange Money

A local aggregator beats three separate integrations

Building and maintaining three separate integrations — one per operator — is technically possible, but it's a heavy undertaking: every national mobile money API has its own endpoints, and even Congolese M-Pesa isn't interchangeable with Kenyan or Tanzanian M-Pesa despite the shared brand name. In practice, many merchant apps in Kinshasa go through a local payment aggregator instead of three separate integrations — FlexPaie, launched in 2025, is one example of an active player in this space, bundling several mobile money operators and sometimes Visa/Mastercard behind a single technical integration. Opening a merchant account with an aggregator typically requires a proper business file; the exact documents required vary by aggregator and are worth confirming directly with the provider you choose.

The payment flow your users already know

Regardless of the operator, the payment journey follows a pattern Congolese users already know by heart: the app triggers a payment request, the user gets a notification or USSD push on their phone asking them to enter their operator PIN, and confirmation comes back to the app via callback. Getting this step right — handling confirmation delays, PIN failures, network timeouts — often matters more for final conversion than the design of the checkout screen itself.

Designing for a country where only one in three subscribers has mobile Internet

By the end of 2025, the DRC had 73.9 million active mobile subscriptions (a 65.9% penetration rate), but mobile Internet penetration was capped at 33%, according to ARPTC. Mobile Internet has nonetheless become the telecom sector's leading revenue driver (53.8% of the $2.394 billion total revenue in 2025, up from barely 14% in 2016) — the market is growing fast, but a large share of smartphone users are still working with an unstable connection, a limited data plan, or intermittent Wi-Fi access.

For an app targeting the Congolese market, that has concrete design implications, not just branding ones: a lean install size (aim for a light APK rather than a 150 MB bundle), a functional degraded mode for core screens when offline, aggressive caching, and systematic compression of images and network requests. An app that requires a permanent connection just to display a basic product catalog loses users before they even reach checkout.

The regulatory framework worth knowing before you launch

A common point of confusion among founders: integrating mobile money into an app doesn't mean becoming an electronic money establishment yourself. That role belongs to the operator (Vodacom, Airtel, Orange) or the licensed aggregator, which already holds BCC approval under Instruction n°24. A business that wants to accept mobile money payments in its app needs a proper merchant account and an administrative file (notably an RCCM registration), not its own banking license — unless it's actually aiming to become an electronic money issuer itself, which is a regulatory undertaking of an entirely different scale.

This is one area where a mobile app development team familiar with the Congolese market saves real time: knowing in advance which aggregator fits the expected transaction volume, what go-live timelines to expect with each operator, and how to structure the architecture so switching aggregators later doesn't mean rebuilding from scratch.

FAQ

Should I build an Android or iOS app first in the DRC?

Android, without hesitation, for any consumer-facing app — it covers more than 84% of phones in the country. iOS remains worth adding to reach a higher-budget professional or premium audience.

How do I integrate Airtel Money, M-Pesa, and Orange Money into one app?

The fastest route is going through a local payment aggregator (Flexpay, Ubpay, Serdipay, Maishapay, and others) that bundles all three operators behind a single API, rather than building and maintaining three separate integrations.

Does a business need approval from the Banque Centrale du Congo to accept mobile money in its app?

No, not in most cases. The electronic money establishment license (BCC Instruction n°24) applies to the operators and aggregators themselves. A business that simply wants to collect payments needs a proper merchant account with an up-to-date RCCM registration.

Why does my app need to work offline or in a degraded mode?

Because only 33% of mobile subscribers in the DRC have active mobile Internet access: a large share of users connect intermittently. An app that requires a constant connection for basic functions loses users before they even reach the payment step.