How to decide whether you need a mobile app

Find a concrete reason to use it

Wanting your own app is a starting point. A useful brief describes the task it will help someone complete. A customer might manage regular bookings, a club member might use membership benefits, or a technician might record a customer visit. Ask what that person does today, what causes difficulty and why they would use the new solution.

Having your brand on a phone is not enough. A useful app has a clear place in its user's everyday routine.

Describe one complete journey

Choose the most important activity and describe a few steps. A technician opens an assigned job, adds a note and photograph, confirms completion and passes the result to a colleague. This helps identify the main screens and the work required within the business. A disconnected list of buttons rarely explains both.

Include cases where something is missing or goes wrong: no connection, incomplete information or an accidental action. The design needs to address these too.

Review this journey with someone who actually does the work. Check whether any steps are missing or unnecessarily repeated.

Check what people need on their phones

Explain whether fieldwork, taking photographs, notifications or repeated use are important. For each need, describe the situation it helps with. Specific capabilities and limitations can then be checked during design. If people only occasionally look for basic information, a clear website is also worth considering. The format should follow the task and the people completing it.

Consider the work behind the app

A customer screen may depend on someone adding offers, confirming bookings or managing employee access. List who will do this and which existing systems they use. Consider whether different users should see different information. Technical requirements can then follow actual permissions and working practices.

Establish where information comes from and who corrects mistakes. Even a small app needs clear responsibility for its data.

Define the first version and ongoing care

For the first version, choose a core journey that gives users a complete result. Prioritise other ideas by need. Agree which users and phones the solution is intended for, how people will get access and who will handle future changes. Finishing development does not establish an operating or support plan. In the proposal, distinguish building the app, introducing it to users and looking after it afterwards.

Prepare for the first conversation

Explain who will use the app, which task they should complete and how they handle it today. Include the main journey, available materials and systems the app should connect with. You do not need to choose a technology beforehand. If you are unsure about the right format, describe the need and leave room to compare the options.