When is an app worth building?
"We need an app" is how a lot of first conversations start. About half the time it's true. The other half, an app is an expensive way to learn that customers didn't want to download anything.
Here's the bar we make every app idea clear before we write a line of code — including our own.
The bar an app has to clear
An app asks a lot from a user: a download, storage space, a home-screen slot, and trust. In return it must offer something a website can't — otherwise the website wins by being one tap away with nothing to install.
So the question is never 'would an app be nice?' It's: what does this idea need that only a phone can give?
Good reasons to build an app
Daily or weekly use — the person returns as a habit, not as a one-off. Deep phone features — camera, photo library, offline work, notifications that people actually want. Speed of access — open, do the thing, done, no browser in between.
Our app Tilo clears that bar: Instagram creators plan their feed layout every week, it works directly with the photo library, and it's useful without a network. That's an app-shaped problem.
Bad reasons to build an app
Prestige ('serious companies have apps'), copying a competitor, or wanting a place on customers' phones for marketing. If the honest usage pattern is once a month, users will delete it — and app stores, reviews and updates will cost you attention that a website never asks for.
In India especially, many customer flows that founders imagine as apps — enquiries, bookings, order updates — are better served by a fast website plus WhatsApp, where your customers already spend their day.
Web first, app store second
Our own product Mudra runs this playbook: it launched as a web app because email signatures and document signing happen at desks, in browsers. If usage ever proves people need it on their phones daily, a mobile app becomes an informed investment instead of a guess.
When an app is the right call, we build it once in Flutter and ship to both iOS and Android — same codebase, same design care, half the maintenance.
Questions we hear a lot
Should I build for iOS or Android first?
In India, Android dominates by volume, but the honest answer is both at once: we build with Flutter, so one codebase ships to iOS and Android together without doubling the cost.
How long does a mobile app take to build?
A focused single-purpose app takes roughly six to twelve weeks to a first release, depending on scope. Anything with accounts, payments or backend workflows runs longer — which is exactly why we pressure-test the idea before building.
Do I need an app if my customers are on WhatsApp?
Often not. Enquiries, bookings, reminders and support all work beautifully as a fast website plus WhatsApp flows. Build an app when the product itself is the tool — not just the channel.
Have something worth building?
Tell us what you're trying to make happen. We'll reply with a plan, not a brochure.
Start a project