Does Your Business Need An App, Or A Better Website?

A customer checking your services before making an enquiry has a different need from a trade buyer who reorders the same products every week. One wants a quick answer. The other may benefit from a tool they return to.

That is the useful starting point when deciding whether your business needs an app. The question is not whether an app looks more impressive. It is whether it makes a worthwhile task easier than the alternatives.

Start With A Job People Need To Do

Describe the problem before listing features.

“Customers keep calling to check their order status” is a clearer brief than “we need an app”. So is “our field team needs to record work where the internet connection is unreliable”.

Then ask who has the problem, how often it happens and what they use today. Watch the current process if you can. A confusing form, missing information or a slow internal response may need fixing before a new piece of software will help.

If visitors mainly want to compare services, see your work and contact you, a well-designed website is a sensible starting point.

Match The Format To The Task

These options can overlap, but the distinction helps you discuss a brief:

• A website helps people find information and take a next step without first installing anything. It may also handle enquiries, purchases or bookings.
• A web application runs in a browser and supports ongoing tasks, such as customer accounts, repeat orders or staff approvals.
• An installed mobile app is worth considering when people have a regular reason to use it and its phone-specific experience adds something useful.

A login, loyalty programme or booking form does not, by itself, settle the decision. First establish what the customer must do and what would make that task easier.

A distributor, for example, might need a straightforward browser-based ordering portal. Whether an installed app adds value depends on how buyers actually place orders, not simply how many products the distributor sells.

Check Offline And Phone Features Carefully

Be specific about any requirement that seems to demand an app. Does “offline” mean reading a saved document, recording a delivery or accepting an order? Those are different jobs.

Some browser-based applications can be installed and designed to support offline work. MDN explains these progressive web apps, often called PWAs. They are an option to assess, not a promise that every website already works offline.

Device features and browser support vary. Google's web-app capability guidance stresses checking support rather than assuming every device behaves alike.

Ask for a demonstration on the actual phones your customers or staff use. Test permissions, a dropped connection and what happens when saved work is sent later. Neither a browser nor an installed app removes the need to design those situations properly.

Give People A Reason To Come Back

An app that is useful once is a harder proposition than one that solves a recurring problem.

Consider how people will discover it, whether they need to install it and what they gain by signing in. Avoid asking for an account before showing information that could be public.

For existing customers, useful reasons to return might include repeating an order or managing an ongoing service. A second copy of your company brochure gives them much less to do.

Keep a clear route for people who have not installed the app. New prospects should still be able to understand your business and contact you through the website.

Plan For Life After Launch

Compare the ongoing responsibilities as well as the initial build.

Who will answer support questions, manage accounts and keep product or service information current? Who maintains connections to your other systems? What happens when a customer changes phones or loses access?

For an app distributed through app stores, include store-account ownership and the release process in that discussion. For a website or web application, include hosting, browser testing, security updates and support.

Ask for a written breakdown of what is included and what is charged separately. Neither option is maintenance-free, and “the app is finished” should not leave your team with an unsupported service.

Test The Smallest Useful Version

Before committing to a large feature list, test the main journey with the people who will use it.

A clickable prototype can reveal confusing steps. A working trial can help check a critical device feature or a connection to an existing system. Choose the test that answers the biggest uncertainty.

Look for practical evidence: can people finish the task, where do they need help, and does the proposed process remove the problem you started with?

You may find that improving the website is enough. You may confirm a need for a customer portal or an installed app. Either is a useful answer when it comes from the work people need to do.

Planning a new website or customer portal? Discuss the project with us.