A mobile app is not the answer to every problem — and often a cheaper mobile website or PWA is enough. Here are the criteria, costs and typical cases that tell you when an app truly pays off for your company.
"We want an app" is one of the most common requests companies come to us with. Almost always it first needs to be translated into a business question: what exactly should that app deliver, and to whom. A mobile app is just one of the tools — and not always the cheapest or fastest one. In many cases the same problem is solved by a well-built mobile website or a PWA at a fraction of the cost and without the hassle of the Apple and Google stores.
The decision therefore does not start with iOS versus Android, but with what you expect from the solution. If you need a customer to find you, read your offer and place an order, a website usually does the job. If you need something people use repeatedly, offline, with notifications or with access to the phone's hardware, a real app starts to make sense.
A large share of companies do not actually need an app — they need a website that works well on a phone. If your goal is presentation, a catalogue, an order form or content people open occasionally, a native app is needless overhead. Nobody will install an app for a single order a year.
A PWA is a sensible middle step for companies that want an "app-like" experience without the cost of two native apps and without store approvals. Its limits are where you need deep hardware access or a presence in the App Store and Google Play for credibility.
A real app starts to make sense when people use it regularly and when you need more than a browser can offer. Typical triggers:
When it comes to technology, it is rarely about pure native for each platform separately anymore. Cross-platform frameworks (Flutter, React Native) build both iOS and Android from a single codebase, which significantly saves cost and maintenance. Pure native makes sense for games, demanding graphics or where the last few percent of performance matter. For a typical business app, cross-platform is usually the most sensible choice.
Instead of general talk, it is better to look at situations where an app genuinely pays off:
In most of these cases the app does not stand alone — it is only a mobile window into a larger system. An ordering app needs stock and prices behind it, a field app needs jobs and invoicing. That is why a mobile app is almost always handled together with a web portal or application that manages the data.
The most commonly underestimated number with an app is not the cost of development, but the cost of the app's life after launch. An app is not a one-off project — it is a living product that requires attention for as long as you use it.
That is why it pays to treat an app as an investment over years, not as a one-off expense. The same logic applies to any custom software — when such an investment pays off and how to reduce the risk we discuss in the article When custom development pays off.
An installed but unused app is a lost investment. To stay on the phone's home screen, an app has to meet a few non-negotiable things:
Before you dive into development, it pays to answer one question honestly: why an app and not a website. If the answer is "so that we are in the store" or "because competitors have one", you probably just need a good mobile website or a PWA. If it is "people will use it daily, offline, with notifications and access to the phone", you are well on your way to an app.
We are happy to help you decide without pushing you into a more expensive solution than you need. We will look at your case, tell you whether a website is enough or whether a mobile application pays off, and propose a step-by-step approach. Get in touch for a no-obligation consultation.
If it is about presentation, a catalogue or the occasional order, a responsive website or PWA usually suffices. A native app makes sense for frequent use, offline mode, notifications or access to the phone's hardware.
Count on maintenance over years: paid Apple and Google developer accounts, ongoing updates for new iOS and Android versions, and running the backend. Maintenance is often underestimated, yet it is part of every living app.
For a typical business app, cross-platform (Flutter, React Native) is usually the most sensible — one codebase for both iOS and Android saves cost and maintenance. Pure native makes sense for games and demanding graphics.
Get in touch and within a few days you'll have a proposed solution and a timeline. No commitments, no fluff.
