"Should we build an app?" usually means "should we build a *mobile* app?" — and it is the most expensive question a young business answers, because the first build spends your most precious capital: the money you have before revenue proves anything. Having built both kinds for years (and mobile apps alongside), here is the framework we actually use with clients.
The one question that settles most cases
Does your user need this in their pocket, or at a desk-shaped moment? People use phones for high-frequency, short-burst, on-the-go tasks: checking, messaging, scanning, tracking. They use browsers for considered tasks: comparing, configuring, filling forms, managing data, paying invoices. Match the platform to the moment, not to fashion. A booking system for your clients? Web first — they book once a month from a link. A daily-use tool for your field staff scanning deliveries? Mobile first, no question.
The quiet advantages of starting with web
A web app has three under-appreciated edges for a first build. Distribution: a link works everywhere instantly — no app store review, no "please download our app" friction, and every update reaches everyone immediately. Discoverability: web pages rank on Google; app store search is a lottery by comparison — our own Ectto platform earns its traffic entirely through web pages ranking for what people search. Cost of change: early products change weekly as you learn; shipping weekly to the web is trivial, shipping weekly through app review is friction.
When mobile genuinely must come first
Mobile-first is right when the product depends on the device itself: camera or barcode scanning at the core of the workflow; offline field use where connectivity is unreliable; push notifications as the engagement engine; or background location. It is also right when your users live in an ecosystem where the app store *is* the trust signal — consumer products in some markets simply feel more legitimate installed.
The budget math, roughly
For the same feature set, expect a mobile app to cost 1.5–2× the equivalent web app once store publishing, device testing and platform quirks are counted — our cost estimator shows the gap live as you toggle platforms. The good news: they are not enemies. A well-architected web app shares its entire backend with a later mobile app, so building web-first rarely wastes a dirham of the backend investment.
Our honest default
Unless the device is the product, start with a responsive web app, learn from real users, then add mobile where the data says pockets matter. It is the cheaper mistake in both directions. If you want a second opinion on your specific case, describe it to us — we will answer with a recommendation, not a pitch, and if you build with us the quote comes escrow-protected either way.