In short
An app pays off when at least one of three things is true: your users come back regularly and you want to be able to reach them. The application needs something from the device that the browser cannot get at. Or it has to work dependably without a connection. If none of these applies, a good website is almost always the better investment.
- Regular return
- Push and the home screen
- Device access
- Camera, GPS, sensors
- Usable without a connection
- Local data
-
People come once and then not again for a long time
An app has to be installed. That effort only pays off if regular use follows it. For anything needed twice a year, the installation is the hurdle where you lose the people who were interested.
-
The content should be found on Google
No search engine finds what sits inside an app. If visibility in search is part of the business, the content belongs on the web, regardless of whether there is also an app.
-
There are no users yet to retain
Push notifications and a place on the home screen are retention tools. They help you keep the users you have, not win the first ones.
-
A channel that arrives
Push notifications land on the lock screen, with no inbox and no algorithm in between. It is the only channel you own once someone has agreed to it. It is correspondingly easy to burn.
-
Access to the device
Camera, location, Bluetooth, motion sensors, biometric sign-in. The browser opens up a section of that, and the browser vendor decides which section. If your project depends on it, the question is settled.
-
Dependable without a connection
Not just cached content, but working without a connection and syncing later. For anything that happens on a factory floor, out in the field or on a train, that is the actual reason for an app.
-
A place people come back to
An icon on the home screen is a claim on attention that a browser address does not have. That only works as long as the app actually gets used.
-
Young companies with a digital product
When the product is the app itself, it comes down to speed: a lean first version, real users, real feedback. Three core features that add up to something whole beat twelve that are half finished.
-
Operators of an existing platform
The app is not a new product here, it is a second way into what already runs. It pays off when people come back regularly and when it does something the browser cannot. Rebuilding the website a second time gets you nothing.
-
Service providers with customer contact
Appointments, messages, documents and invoices in one place. The benefit is measurable on both sides: fewer queries for you, less waiting for your customers.
-
Companies with work away from a desk
Time tracking, training, inspection records, reports from the field. Internal apps look simple and rarely are, because they have to connect to existing systems. In return the benefit is measurable immediately.
- 01
The first scope is too large
The most common cause. A feature list from a workshop almost always contains a part you can only judge after launch. Build all of it first and you have the most expensive version before the first piece of feedback arrives.
- 02
Nobody is assigned to run it
Apple and Google change their requirements every year. An app with nobody responsible and no budget for it disappears from the store after twelve to eighteen months, not with a bang but through a missed deadline.
- 03
The app is the website with rounded corners
If there is nothing in it the browser could not also do, there is no reason to install. The installation is then pure friction with nothing in return.
- 04
There is no plan for how people find out about it
In the App Store, only people already looking for an app like yours will find you. Nothing happens there on its own. Work out before launch where your first thousand users are coming from.
Do I really need an app?
Test it against three questions: do people come back regularly? Does the application need something from the device the browser cannot give? Does it have to work without a connection? If none of them is answered yes, a good website is usually the better investment.
What is a hybrid app and why does it come up here?
In hybrid or cross-platform development, one codebase produces an app for both iOS and Android. That is the norm today, because it halves effort and maintenance without users noticing the difference.
Is my idea even feasible?
Almost always yes, technically. The more interesting question is what the smallest slice is that shows whether the idea holds. That is exactly what we work out in the first conversation, and sometimes the result is that no app is needed yet.
How long does it take to build?
A narrow, focused first version takes six to eight weeks. Mid-sized projects ten to fourteen, larger ones sixteen to twenty-four. What drives the timeline is rarely the technology, it is the number of decisions still open.
What does it cost?
Modest projects start at around €12,000, mid-sized ones at €25,000, demanding ones at €45,000. The breakdown by cost driver is on the costs page.
What happens after launch?
Operation and maintenance, permanently: bug fixing, monitoring, yearly adjustments to new system versions. Maintenance packages start at €300 a month. This item belongs in the plan from the beginning.
Which technologies do you work with?
React Native and Expo, with TypeScript across app, backend and web. That choice is as much a staffing decision as a technical one: one language across the whole stack is something you can hire for over years.