OBP Solutions
Request Quote

Before you commission a mobile app: six questions to answer first

An app is a big commitment. These questions help you decide if you need one, and what it should do.

Not every business needs an app, and the ones that do rarely need everything on their first wish list. An app can be a great investment or an expensive distraction, and the difference is usually decided before any code is written. Six questions will tell you where you stand.

1. What problem does it solve?

Write it in one sentence. If you cannot, the idea needs more work. A good app removes a specific frustration, for your customers or your own team.

2. Could a mobile friendly website do it?

For many ideas a website is faster and cheaper, and it works on every phone without anyone installing anything. Apps earn their place with offline use, notifications or device features such as the camera.

3. Who will use it, on what phones?

Know whether your users are on Android, iPhone or both, and how good their internet is. In many places data is costly and connections drop, so an app that works offline can matter more than one with fancy screens.

4. What is the smallest useful version?

Launch with the one or two features that matter, then grow from real feedback. Every extra feature adds cost, time and more to maintain.

5. How will it connect to your other systems?

Orders, customer records and payments may need to talk to the app, for example mobile money such as MTN MoMo or Airtel Money. This is often the hardest part of the project, so plan it early.

6. Who will look after it?

Apps need updates when phones and stores change. Plan for that from the start, including who pays for it and who answers users when something goes wrong.

Android, iPhone or both

If you must choose one to start, pick the one most of your users have. Building for both costs more, but a single codebase can serve both when the app is simple enough. Ask your developer which approach suits your case.

Common mistakes

The most common mistakes are building too much at once, skipping a test with real users, and forgetting running costs such as app store fees, hosting and updates.

If you would like help answering these, we are happy to talk it through before any work begins.

More insights

Want help with this?

Tell us what you are trying to achieve and we will reply within 24 hours with clear, practical advice.