Someone on your team says it, or a customer does: “We should have an app.” Your competitor has one, your mobile website feels clumsy next to it, and a proper app on people’s phones sounds like the grown-up next step. The question of app vs mobile website usually lands on the owner’s desk as a feeling rather than a decision, and a quote from a developer follows soon after.
We see two common mistakes. One is building an app because the website is disappointing, when the website is what needs the work. The other is refusing an app because “nobody downloads apps”, when the business is exactly the kind that customers open every week. The difference comes down to a handful of things you can check yourself before spending anything.
Why businesses start asking for an app
The mobile website is slow or awkward. Pages load slowly, forms are hard to fill on a phone, the menu hides what people need. This feels like “we need an app”, but an app does nothing for the new customer who arrives from search or an ad on that same website. The sign: complaints and drop-offs are about the site itself, not about missing features.
Customers come back often and repeat the same action. Re-ordering, booking the next appointment, checking a balance, tracking a delivery. When a customer does this weekly, typing your address and logging in every time is real friction, and an icon on the home screen removes it. The sign: your regulars are a large part of the business and they do the same few things.
The job needs the phone itself. Scanning with the camera, knowing where the customer is, working in a warehouse or on a site without a signal, reminders at the right moment. A browser can do some of this, but a native app does it more reliably. The sign: the feature you want is impossible or unreliable in your current site.
Someone else has one. A competitor’s app creates pressure, but it says nothing about whether their customers use it. The sign: the case for the app is about image, not about a task your customers do.
App vs mobile website: how to tell which one you need
Give this an evening, with your analytics and your phone.
- Open your website on your own phone as a new customer would. Search for your business, tap through to the main action (buy, book, enquire) and finish it. Note every moment you had to zoom, wait or retype. If this is painful, the answer for now is the site, not an app.
- Check how often customers come back. In your analytics, booking system or CRM, look at how many visits or orders come from returning customers and how often they return. Frequent, repeated use is the strongest case for an app; occasional use is the strongest case against.
- List what customers do when they return. If it is the same few actions, an app can make those one tap. If every visit is different browsing, a website serves it well.
- Write down the features you want that the site cannot do. Be specific: camera, location, offline, notifications, payments with a stored card. Then check whether a progressive web app, which is a website that can be installed on the home screen, could already cover them on your customers’ phones.
- Ask a few regular customers. Not “would you like an app?”, which everyone answers yes to, but “what do you do with us that is annoying on your phone?” The answers tell you what the app would be for.
If the site fails step one, fix it first. If customers return often, repeat the same actions and need something only the phone does, an app has a real job.
The fix, in order
- Make the mobile website good. Speed, a clear main action, forms that work with a thumb, saved details for returning customers. We explained the usual causes of a slow site and how to find them in why your website is slow and what it costs you. In our website projects the mobile version is designed first, because that is where most people meet the business.
- Add app-like features to the site. Customer accounts, saved orders, one-click repeat, email or text reminders. This tests whether customers actually want the shortcuts before you build them into an app.
- Try a progressive web app. Let customers install the site to their home screen and, where the phone allows it, receive notifications. If few people install it even when prompted at the right moment, a store app is unlikely to fare much better.
- Build the app around one job. When the case is clear, start with the action your regulars repeat most, not a copy of the whole website. Our approach to mobile app development starts with that single flow, a clickable prototype tested on real customers, and only then design and code.
- Plan for life after launch. An app needs store accounts, updates for new versions of iOS and Android, a backend that keeps working and someone who reads the reviews. Budget and ownership for this belong in the decision, not after it.
- Give customers a reason to install. A link on receipts and confirmation emails, a mention at the counter, a benefit that exists only in the app. An app nobody hears about stays in the store.
What to measure
- Mobile conversion on the website: the share of phone visitors who complete the main action, before and after the fixes, checked monthly.
- Returning customers and how often they return, from analytics or your CRM; this is the number the app is meant to grow.
- Installs of the web app or the store app relative to active customers, not in absolute terms.
- Active users of the app over time, checked after a few months: an app that customers install and stop opening has not found its job yet.
Where we come in
We start with the question, not the build: who comes back, what they do and what the phone must do that the site cannot. Sometimes the honest answer is a better mobile website, sometimes it is an app with one clear job, and often it is the first now and the second later. If you want us to look at your case, the brief is the easiest way to start.