An app in a store sounds serious, but it costs more and is harder to reach. When a good website is enough, when an app is necessary and what sits in between.
First, a question about the customer
Before the word “app” comes up, ask yourself how often your customer will use it. An app has to be found in a store, downloaded, installed and not deleted during a clean-up of the phone. Someone will do that for a tool they use every week. For a restaurant menu or a price list of services, probably not.
When a website is enough
- The customer needs to find out who you are, what you offer and what it costs.
- They are to book an appointment, send an enquiry or buy a product.
- They use it from time to time, not every day.
- They are supposed to find you on Google. A search engine won’t show an app the way it shows a website.
When you need an app
An app makes sense when you need something that the browser can’t do, or can do only partly.
- Working in the background, without opening anything. Dyżur checks the schedule every half minute and switches call forwarding by itself. A website can’t do that, because it has no access to such phone functions.
- Access to hardware: vibration in a set rhythm, sensors, Bluetooth, NFC, phone calls.
- Working without internet for a long time.
- Daily use, where an icon on the screen saves time. Breath of the Bald guides a breathing session with vibrations, so you can practise with your eyes closed.
Something in between: a web app
Between a website and an app there is a third way: a web app, that is a website you can add to your phone’s home screen and use like an ordinary app (a PWA). It opens without the browser bar, can work partly offline and can send notifications. You build it once for all phones and computers, without going through an app store.
There are limits too: access to phone features is narrower than in an app installed from a store, and on iPhone some capabilities, such as notifications, work only after the site is added to the home screen. For a customer panel, a schedule or a booking system, though, it is often the best compromise.
What costs more than it seems
- Two platforms. Android and iPhone have separate requirements, tests and releases. Shared code, as in Flutter, helps a great deal, but it doesn’t excuse you from testing on both.
- The stores. A Google Play developer account is a one-off fee, Apple charges a fee every year, and every version goes through a review that can take anywhere from a few hours to a few days.
- New system versions. Every year Android and iOS change the rules, for example for background work or permissions, and the app has to be adjusted to them.
Key takeaway
A website is enough when the customer is to find out, ask or buy. An app is needed when it has to work in the background, use the phone or be used every day. In between is the web app, often the most sensible choice.