Building an app nobody asked for vs one people actually need

A lot of app ideas start the same way - "wouldn't it be cool if we had an app for this." And sometimes that's true. But just as often, the honest answer is that the business problem could be solved with a slightly better website, or a WhatsApp flow, or nothing more complicated than a form, and the app is really just something the founder wanted to point to and say "we have an app."

The apps that actually get used tend to start from a much less exciting place - a specific, repeated pain point that a phone genuinely solves better than anything else. Patients who need to book a slot and get a reminder without calling the clinic. A delivery rider who needs offline access because signal drops mid-route. Someone standing in a store trying to scan a code and check stock instantly. Those are real reasons for an app to exist, because the phone is doing something a browser tab or a phone call can't do as well.

Before we start actually designing anything, this is usually the first conversation - not "what should the app look like," but "why does this need to be an app at all, and what's the one thing it has to do really well." It's a slightly deflating question to ask a client who's excited about their idea, but it saves months of building something nobody opens twice.

If you're sitting on an app idea, it's worth being honest with yourself about which category it falls into before writing a single line of code. Most good apps do one thing well and stay out of the way otherwise. That's the standard we hold our own app design and development to - not "can we build this," but "should this exist as an app in the first place."