"We Need an App" — Do You, Though?
It's one of the most common requests we hear, and one where honest advice matters most: most businesses asking for an app actually need a fast mobile website. Some genuinely need an app. Confusing the two burns serious money in both directions.
Here's how to tell which one you are.
The Uncomfortable App-Store Math
Before falling in love with an icon on the home screen, know the funnel:
- The average user installs zero new apps in a typical month
- Asking someone to download an app to interact with your business adds a step where most prospects quit
- Of those who install, average 30-day retention hovers around 5–10%
An app is a commitment your customer makes to you. Most customers aren't ready for commitment — they want answers, prices, and a way to order, right now, with zero installation.
When a Mobile-First Website Wins
A modern mobile site loads in a second, works on every device, needs no install, and every improvement ships instantly to all users. It's the right answer when your goals are:
- Being found. Websites are searchable; apps are invisible to Google.
- Informing and converting. Services, pricing, portfolio, booking, ordering — all excellent in the browser.
- Reaching occasional customers. Anyone who interacts with you weekly or less will not keep your app.
- Budget efficiency. One codebase, one deployment, no app-store review cycles, no forced updates.
Progressive Web App techniques close most remaining gaps: home-screen icons, offline support, even push notifications on Android. For 80% of small and mid-sized businesses, a fast mobile-first website is the complete answer.
When a Real App Is Worth It
Apps earn their cost in specific situations:
- Daily-use products. Your users return constantly — field teams, members, drivers, patients tracking something. Frequency justifies the install.
- Deep device integration. Continuous GPS, camera-heavy workflows, offline-first field operation, hardware connections.
- Push as a core channel. iOS push notifications still effectively require a native app, and for some businesses that channel is the business.
- Logged-in experiences with stored context. When the user's whole relationship with you lives inside the product — think internal tools your staff opens 30 times a day.
Notice the pattern: apps serve existing, frequent relationships. Websites create new ones. That's why the strongest setups pair a public website for acquisition with an app for the loyal core.
The Cost Question — Changed by React Native
The old objection to apps was building everything twice: one team for iOS, one for Android. Cross-platform frameworks ended that. With React Native, one codebase ships to both stores — roughly 60–70% of the old cost — and shares logic with your web application if you have one.
That's how we build mobile apps: React Native, one team, both platforms, with the web stack and the app speaking the same language.
A Decision Shortcut
Answer two questions:
- Will a typical customer use this weekly or more?
- Does it need device capabilities a browser can't provide?
Two yeses: build the app. Two noes: build the mobile-first site and spend the difference on marketing. One yes: start with the website, add the app when usage data — not optimism — justifies it.
Unsure which side you land on? Walk us through the use case and we'll tell you straight — including when the cheaper answer is the right one.