Web App or Mobile App? What Your Business Should Build First

Almost every founder I talk to in Nairobi asks the same question: "Should I build an app or a website first?" The answer that saves the most money is almost always the same — but not for the reason you'd think.

Start with a web app. Usually.

• One build, every device. A responsive web app works on Android, iOS and desktop from a single codebase. Native apps mean two builds — or Flutter, which still costs more than web.
• No store approvals. Deploy today, iterate tonight. App Store review cycles slow early-stage iteration to a crawl.
• Kenyan reality: your users find you through Google and WhatsApp links — not the Play Store. A link opens a web app instantly; an app install loses half of them.
• Cheaper to change. You'll pivot at least twice in year one. Web pivots are cheap; native rebuilds aren't.

When mobile first actually wins

• You need device hardware — GPS tracking, camera workflows, Bluetooth, USSD-adjacent flows, offline-first field work.
• Push notifications are core — delivery updates, ride-hailing, time-sensitive alerts where SMS costs more than push.
• Daily-habit products — if retention depends on sitting on someone's home screen, mobile earns its keep.

The pattern that works

Most of my projects follow this path: web platform first → prove the model → Flutter app when retention demands it. FungaDeal and Alutamax both started web-first; the apps came after the revenue proved the need.

And if you build the web app on a proper API from day one, the mobile app later is mostly a front-end — not a rebuild.