It is a strange thing for an app studio to say, but a lot of businesses do not need an app. They need a faster website, a better booking tool or a cleaner checkout. The ones that do need an app tend to get a great deal out of it, and the difference between the two groups is usually easy to see once you ask the right questions.
This is the test we walk through on intro calls, before anyone talks about features or price.
The home screen test
A phone's home screen is the most selective shelf in the world. People keep a small number of apps they open regularly and ignore the rest. Before anything else, ask: would your customers open this more than once a month, without being reminded?
If the honest answer is no, a well-built mobile website will usually serve them better: there is nothing to install, it works from a link and search engines can find it. If the answer is yes, because they book, order, track, play, learn or manage something with you regularly, an app starts to make sense.
Good reasons to build your own app
Repeat use
Anything people do weekly or daily (reordering, booking, checking progress, a daily game or lesson) is where an app shines. One tap from the home screen beats finding a bookmark and logging in again.
Things only the phone can do
Push notifications, the camera, location, offline use, Apple Pay and Google Pay, widgets, haptics and background audio are all either impossible or noticeably worse in a browser. If your idea depends on one of them, that is a strong signal.
A direct line to your customers
On a marketplace or a social platform, the platform owns the relationship. In your own app, the customer is yours: you choose when to send a notification, what the experience looks like and what data you collect, within the privacy rules you set and the stores enforce.
The app is the product
If what you are selling is software itself (a game, a tool, a subscription service), the question answers itself. The decision then is only about how to build it well.
What owning your app actually gives you
There are plenty of ways to get something app-shaped without building it: template app builders, no-code tools, white-label products, a page inside someone else's platform. They are quick and cheap at the start, and for some businesses they are the right answer. The trade-off shows up later.
- You decide the roadmap. With a template you get the features its vendor decided to build. With your own app, the next feature is the one your customers need.
- Your costs do not grow with someone else's pricing. Per-user or per-feature fees that are small at launch can become your largest bill as you grow.
- The experience can be yours. Your brand, your flows and your details, rather than the same screens a hundred other businesses use.
- The code and the data are an asset. A custom app, its design system and its user base belong to your company. That matters to customers, to partners and to anyone who might one day invest in or buy the business.
Ownership has to be real, though. Whoever builds it, make sure the app is published under your Apple and Google developer accounts, and that the source code and design files are handed over to you.
When not to build an app (yet)
- You have not proven people want it. If a landing page, a form or a manual version of the service cannot attract interest, an app will not fix that.
- The use is occasional. A once-a-year purchase or a one-off enquiry belongs on the web.
- Nobody will look after it. Apps need updates as iOS and Android change every year. If there is no budget or owner for that, the app will slowly break.
- Discovery is the goal. People find businesses through search, and search finds websites. An app keeps customers; it rarely finds new ones on its own.
A useful middle step is a fast, mobile-first web app. It can later become the foundation for store apps, especially if it is built with the same tools.
The costs people forget
Beyond the build itself, plan for these from day one:
- Store accounts. The Apple Developer Program is a yearly membership (99 USD a year at the time of writing). A Google Play developer account has a one-time registration fee (25 USD).
- Store commission. If you sell digital goods or subscriptions inside the app, Apple and Google take a share. Both offer a reduced 15% rate on the first million dollars of yearly revenue to qualifying developers.
- Hosting and services. The backend, database, push notifications, analytics and crash reporting each have a monthly cost that grows with usage.
- Maintenance. Every year brings new OS versions, new devices and new store requirements. Budget a steady amount of time to keep the app current.
A five-question checklist
- Will customers use it regularly without being chased?
- Does it need something only a phone does well?
- Have you seen real demand for the service it offers?
- Is there a budget and an owner for the year after launch?
- Will owning it be worth more than renting a tool that does part of the job?
Three or more confident yeses and an app is very likely worth building. Fewer, and start with the web, a prototype or an existing tool, then come back when the numbers say so.
If you are not sure where you land, that is exactly what our thirty-minute intro call is for. We will tell you if an app is the wrong move, and if it is the right one, our guide to choosing who builds it is the next thing to read.