People often say they want an app when what they need is a website that works well on a phone. Both have a place. This guide helps you decide which one solves your problem, and what an app involves once it is built.
When a mobile-friendly website is enough
- Customers visit once or twice to find information or make an enquiry
- You want to be found on Google, which an app does not help with
- You do not need features that only an installed app can use
- You want to launch quickly and update often
When an app is worth it
- People use it often, for bookings, orders, loyalty or tracking
- It needs push notifications, the camera, location or the ability to work offline
- Staff use it in the field, for example to capture jobs or deliveries
- It is the product itself, not a way to promote something else
One app for iPhone and Android
A cross-platform approach builds both versions from one codebase, which lowers the cost and keeps them in step. Some features may need extra work on each phone. Ask which approach is proposed and why.
What an app involves after it is built
- Developer accounts with Apple and Google, which should be in your own name
- Review by the app stores before an update goes live
- Updates when new phone versions are released
- Hosting and support for the system behind the app
- A plan to tell customers it exists
A good way to start
Build a small first version that does one job well, put it in the hands of real users and improve it from what you learn. A smaller first version costs less, and you find out sooner whether people use it.