The Constraints That Shape Every Decision
Building mobile apps for African markets means optimizing for constraints most Western developers never face:
- Device diversity: Users run everything from entry-level Android phones with 1GB of RAM to flagships
- Slow networks: 3G is still common. 4G is spotty. WiFi is a luxury. A large APK on 3G is a long, expensive download.
- Expensive data: Mobile data is expensive relative to income across much of the continent. Every MB matters.
- Storage constraints: Users delete apps to save space. A bloated APK doesn't stand a chance.
Why Cross-Platform Makes Sense
Most of our clients need both iOS and Android apps. Building twice (Swift + Kotlin) roughly doubles cost and time. Cross-platform frameworks let us ship faster at lower cost while keeping performance close to native.
React Native vs Flutter: The Data
| Metric | React Native | Flutter |
|---|---|---|
| APK Size (Hello World) | 7-10 MB | 15-20 MB |
| Developer Availability (Africa) | High (JavaScript/React) | Low (Dart is rare) |
| Reuse with an existing React web codebase | High (shared React skills and logic) | Low (separate Dart codebase) |
| Native Module Ecosystem | Excellent | Good |
| Performance | Near-native | Near-native |
Why React Native Wins for Us
1. Smaller APK Size = More Downloads
In African markets, users are cautious about app size. When storage and data are scarce, download size is a real conversion factor. React Native's smaller baseline gives us more headroom for features.
2. JavaScript Talent Pool
Finding React Native developers in Zimbabwe, Nigeria, or Kenya is far easier than finding Flutter devs. Most African developers know JavaScript. Dart is niche. This matters for client handover and long-term maintenance.
3. Code Sharing with Web
Many of our projects pair a web dashboard with a mobile app. With React Native we share a large portion of the business logic, validation schemas, and API clients between them. With Flutter, we'd maintain all of that twice.
4. Mature Ecosystem
React Native has been production-ready since 2015. The ecosystem is massive:
- Native modules for every payment gateway (Paynow, Flutterwave, M-Pesa)
- Offline-first libraries (WatermelonDB, RxDB)
- Push notification support (FCM, OneSignal)
- Robust analytics (Sentry, Mixpanel)
React Native Performance Optimizations for Africa
1. Offline-First Architecture
We use Redux Persist + AsyncStorage to cache API responses locally. Users can browse products, view past orders, and even draft messages while offline. When they reconnect, changes sync in the background.
2. Image Optimization
We use react-native-fast-image with disk caching and WebP format. Product images are served at 3 resolutions (thumb, medium, full) and lazy-loaded. This sharply reduces data usage.
3. Bundle Splitting with Hermes
Hermes (Meta's JavaScript engine) noticeably improves startup time and memory usage on low-end Android devices. We enable Hermes on all projects now.
4. Native Modules for Performance-Critical Code
For CPU-intensive tasks (image compression, encryption), we write native modules in Java/Swift. React Native makes this easy with the JSI (JavaScript Interface) layer.
When We'd Choose Flutter
Flutter isn't wrong, it's just optimized for different constraints:
- Custom UI-heavy apps: Flutter's canvas-based rendering shines for complex animations (games, creative tools)
- Teams already using Dart: If your backend is Dart (rare), Flutter makes sense
- No web requirement: If you only need mobile, Flutter's performance edge matters more
The Honest Trade-Offs
React Native cons we live with:
- Occasional bridge performance bottlenecks (mitigated by Hermes + JSI)
- Dependency churn (React Native updates break things sometimes)
- Native module debugging can be painful (Xcode/Android Studio context switching)
The Bottom Line
React Native isn't perfect. We've debugged our share of native module crashes at 2AM. We've cursed at Xcode more times than we can count. We've rewritten components when React Native upgrades broke things.
But for African markets, where JavaScript talent is abundant, data is expensive, devices are diverse, and web+mobile convergence matters, it's the pragmatic choice. We ship React Native apps across fintech, healthcare, and e-commerce for African users. It works.
If you're building a mobile app for African users and wondering which framework to choose, talk to us. We've made the mistakes so you don't have to.
Tech Stack: React Native (Expo), Hermes, TypeScript, React Navigation, react-native-fast-image, Sentry