Building web platforms that perform well across Nairobi, Dar es Salaam, and Kampala requires a fundamentally different set of assumptions than shipping to users in London or San Francisco. Network conditions vary block by block, most traffic arrives on mid-range Android devices, and payment flows depend on carrier-based APIs that behave nothing like Stripe.
Mobile-first is not optional
Over 85% of web traffic in the region arrives on mobile devices. Our initial payload budget is 150KB compressed. We achieve this by aggressively code-splitting, serving AVIF images with fallbacks, and deferring JavaScript that is not critical to the first interaction. Server-side rendering is essential — not for SEO theatre, but because a 3G connection in Mombasa cannot afford a client-side rendering waterfall.
// Edge middleware for regional routing
export function middleware(request: NextRequest) {
const country = request.geo?.country ?? 'KE';
const region = ['KE', 'TZ', 'UG'].includes(country)
? 'east-africa'
: 'global';
request.headers.set('x-region', region);
return NextResponse.next({ headers: request.headers });
}Payment integration realities
M-Pesa's Daraja API is asynchronous by nature — you initiate an STK push, then wait for a callback. This means your checkout flow must handle a pending state that can last 30 seconds or more. We use a webhook receiver backed by a durable queue, with exponential backoff for callback failures. The user sees a real-time status update via server-sent events rather than polling.
The most reliable payment systems in this region are the ones that assume every network request might fail and design around that assumption from day one.