When a mobile app pays off for a company

An app, or a mobile website? The first question

"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.

When a mobile website or PWA is enough

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.

• Responsive website — works on every device, gets indexed by Google, nothing to install.
• PWA (progressive web app) — a website you can "add to home screen", works offline and handles push notifications on most devices.
• One codebase — you maintain one thing instead of a website plus two apps.

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.

When a native or cross-platform app pays off

A real app starts to make sense when people use it regularly and when you need more than a browser can offer. Typical triggers:

• Frequent use — people open the app daily or weekly, an icon on the home screen has value.
• Offline mode — a worker must function without signal and the data syncs later.
• Hardware access — camera for scanning codes, background GPS, NFC, Bluetooth, biometrics.
• Reliable notifications — push you can rely on as a communication channel.

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.

Typical cases where an app makes sense

Instead of general talk, it is better to look at situations where an app genuinely pays off:

• Loyalty programme — an app with a card, points and personalised offers keeps a customer closer than email. A push notification about a promotion has a far higher open rate than a newsletter.
• Field workers — technicians, installers, delivery or sales reps need an app that works offline, loads the job, photographs a document, captures a signature and syncs everything to the system.
• Orders and reservations — regular ordering (hospitality, wholesale, B2B stock replenishment) is exactly the case where a returning customer appreciates a fast app with history and favourite items.
• Internal company tools — approvals, attendance, field records that must be at hand on a phone.

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.

Costs and maintenance to count on

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.

• Two platforms — even with cross-platform, the app has to be tested and published for both iOS and Android, each with its own rules.
• Stores — Apple and Google developer accounts are paid annually and every update goes through approval.
• OS updates — new versions of iOS and Android come out every year and the app needs ongoing maintenance so it does not break.
• Backend — the server, database, integrations and security that power the app run and cost regardless of how many screens the app has.

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.

What an app must have for people to use it

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:

• Clear value on every open — the user must know why they are opening it and get it quickly.
• Speed and reliability — a slow app that crashes or takes long to load ends up uninstalled.
• Easy sign-in — biometrics or sign-in via an existing account instead of filling out forms.
• Meaningful notifications — relevant and not annoying; spam is the fastest route to muted notifications and uninstalls.
• Security and privacy — data protection and compliance, especially if the app collects location or personal data.

How to decide well

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.