What goes wrong
What goes wrong with mobile app projects?
The most expensive app mistake is building the wrong kind — going native when a progressive web app would have done the job for far less. The second is having no plan for getting it installed. Most failed apps work correctly and are simply never used.
Building native when a PWA would do
This is the costliest error because it is made at the start, silently, and cannot be undone without rebuilding. "We need an app" turns into two native codebases and store review cycles, when the requirement was something people could open on their phone and use quickly.
Ask what the app must do that a website on a phone cannot. If the honest answer is "nothing, we just want it to feel like an app," you want a progressive web app.
No plan for installs
An app is not a website. Nobody stumbles onto it. Every single user has to decide to install it, which is a far higher bar than clicking a link, and app stores are not a discovery channel for small businesses.
If you cannot describe, concretely, how the first thousand people will hear about the app and why they would install rather than use your website, the build is premature. This kills more apps than any technical problem.
Nothing worth opening twice
Installs are the first hurdle; the second is retention. An app that duplicates your website gives nobody a reason to keep it. The ones that survive do something the web cannot: saved preferences, order history one tap away, notifications that are genuinely useful, loyalty that accrues.
Decide what the second visit is for before building the first.
Abandonment after launch
Apps decay in a way websites do not. Operating systems update annually and change requirements. Store policies shift. An app nobody has touched in two years is often broken, delisted, or both — and by then the original developer has moved on and the accounts are in their name rather than yours.
Two protections: budget for maintenance from the start, and make sure the developer accounts and code are registered to your business.
Common questions
- Why do most business apps fail?
- Not for technical reasons. They fail because nobody installs them, or because there is no reason to open them twice. Distribution and retention are the hard parts; building is the easy part.
- What happens if we stop paying for maintenance?
- The app keeps working until an OS update or store policy change breaks it, which typically happens within a year or two. Because the accounts are in your name, you can hand maintenance to anyone — but somebody has to do it.
More on mobile app development
Want this looked at for your business?
Tell us where you are trying to get to. If the honest answer is that you do not need us, we will say so.