"We want to build an app." It's one of the things we hear most often. And our first response is always the same: why? Not to put you off, but because the answer to that question determines whether the investment is worth it, or whether there's a far cheaper solution that would do exactly the same job.
A mobile app isn't a shopfront
If your goal is to showcase your services, share content or let customers get in touch, a well-designed website does the job, and does it better. Mobile apps come with a high cost of acquisition: users have to find you on a store, download the app, and create an account. For a simple shopfront, that journey is far too long.
The real reasons to build an app
A mobile app makes sense when your product needs features the web can't offer satisfactorily:
- Offline use: the user needs to be able to use the app without an internet connection
- Hardware access: camera, GPS, sensors, Bluetooth, features native to the device
- Push notifications: you need to prompt your users to come back at specific moments
- Very frequent use: the user opens the app several times a day
The question to ask above all others
Imagine your app exists. Now imagine the same thing exists as a website accessed through a smartphone's browser. For your target user, what real difference does it make? If the answer is "not much", you probably don't need a native app.
A mobile app is a commitment, for you and for your users. It's only justified when it does something a website can't do just as well.
Maybe start with a PWA
A Progressive Web App (PWA) is a website that behaves like an app: it installs on the home screen, works offline, and can send notifications. It's often the right first step, you validate your concept at a fraction of the cost, and you can always move to a native app later if demand justifies it.
There's no wrong answer, only premature ones. Take the time to understand how your users actually behave before you decide. And if you're not sure, start small.