Quick answer: Most businesses should start with a fast, responsive mobile website, because it reaches anyone with a browser, can be found in search, and costs far less to build and maintain. A native mobile app makes sense when customers will use it often, when you need device features such as offline access, push notifications, the camera or background location, or when the app itself is the product. Many companies end up with both, but the website almost always comes first.
“Should we build an app?” is one of the most common questions we hear from business owners. Sometimes the answer is yes. More often, the real need is a mobile experience that works well, and a website can deliver that at a fraction of the cost. This guide explains the difference and gives you a simple way to decide.
What we mean by each option
Mobile website
A mobile website is a site that works well on phones and tablets. Today that usually means a responsive website: one site whose layout adapts to the screen size, so the same pages work on a desktop, a tablet and a phone. Visitors reach it through a browser such as Chrome or Safari, from a search result, a link or a typed address.
Native mobile app
A native app is software built for a specific platform, usually iOS and Android, and installed from the App Store or Google Play. It lives on the home screen, can work offline and has deeper access to the phone’s hardware and operating system.
The middle ground
There are options in between. Hybrid apps wrap web code in a native shell using tools such as Apache Cordova or Ionic. Frameworks such as React Native let developers write in JavaScript while producing native interfaces. And progressive web apps (PWAs) are websites that use newer browser features, such as service workers, to work offline, load quickly and send push notifications. Chrome on Android supports these features today. Safari on iOS does not yet support service workers, so on iPhones a PWA behaves like a normal fast website.
Reach and discovery
This is where websites win clearly.
- Search. Web pages can be found on Google and Bing. App content is mostly invisible to search unless you invest in app indexing.
- No install barrier. A link opens a website instantly. An app asks people to visit a store, download, wait and then open it. Every step loses people.
- Every device. A website works on iPhone, Android, Windows phones, tablets and desktops from one codebase.
- Sharing. Anyone can share a web page link on social media, email or chat. Sharing an app screen is clumsier.
Apps do have one discovery channel of their own, the app stores, but competition there is fierce and most people only install a handful of new apps a month, if any.
Engagement and features
This is where apps earn their place.
- Home screen presence. An installed app icon is a daily reminder of your brand.
- Push notifications. Apps can send timely messages, such as an order update or a reminder. Websites can now do this in Chrome and Firefox, but support is not universal.
- Offline use. Apps can store data and work without a connection. PWAs can do some of this in supporting browsers.
- Device features. Camera, GPS in the background, Bluetooth, Touch ID, contacts and the accelerometer are far easier to use from a native app.
- Speed and polish. A well built native app can feel smoother than a website, especially for complex, interactive screens.
If your customers will open your product several times a week, those benefits add up. If they visit once every few months, they mostly go unused.
Cost and maintenance
A responsive website is one project, one codebase and one place to update content. Your CMS lets staff edit pages without a developer.
A native app usually means two codebases (iOS and Android), developers with different skills, store approval processes and regular updates whenever Apple or Google release new operating system versions. You also still need a website, because people will search for you and you need somewhere to send them. The app often needs an API on the server so it can fetch and save data, which is another piece to build and maintain. If that sounds unfamiliar, our explainer on what an API is is a good starting point.
As a rough rule, a quality native app on both platforms costs several times more than a good responsive website, and ongoing costs are higher too. For a sense of what goes into website pricing, see our guide to website development cost.
When a mobile website is the right choice
Choose a website first if:
- Your main goal is to be found and to generate enquiries or sales
- Customers visit occasionally, for example to check prices, book a service or read information
- You publish content regularly and want it to rank in search
- Your budget is limited and you need to reach as many people as possible
- You want to change content often without app store releases
This covers most service businesses, professional firms, local shops, publishers and many online stores.
When a native app is worth it
Consider an app if:
- Customers use your service frequently, such as banking, ordering food, booking travel or tracking fitness
- You need offline access, for example field staff filling in forms where signal is poor
- Your product depends on device features such as the camera, background location or Bluetooth
- You run a loyalty programme where a home screen icon and notifications drive repeat visits
- The app is the product itself, such as a game or a tool people pay for
Even then, keep a strong mobile website for search, marketing and people who will not install.
Where progressive web apps fit
Progressive web apps are worth watching. A PWA starts as a normal website, so it is found in search and needs no install. In supporting browsers it can then be added to the home screen, work offline and send push notifications. For many businesses, that combination covers most of what they wanted from an app.
The limits are real for now. iPhone support for the key features is missing, and some device capabilities are still out of reach from the browser. But building your mobile site with fast loading, offline caching where possible and a clear app-like interface is a sensible step that does not lock you into anything. Our article on progressive web apps explains the technology in more detail.
A simple decision framework
Ask these questions in order:
- Do we have a fast, responsive website that converts well on phones? If not, fix that first. It helps every other channel.
- How often will a typical customer use this? If the answer is weekly or more, an app may pay off.
- Do we need device features a browser cannot provide? If yes, an app or hybrid app is likely needed.
- Can we afford to build and maintain two platforms properly? A neglected app with poor reviews hurts your brand.
- Could a PWA or web push notifications cover most of the need? If so, try that before committing to native.
Common mistakes
- Building an app because competitors have one. Check their reviews and ratings. Many company apps are barely used.
- Copying the website into an app. If the app does nothing the website cannot, people have no reason to install it.
- Forgetting the back end. Apps need an API, user accounts and data sync. Plan these early.
- Ignoring the mobile site once the app launches. Most new visitors will still arrive through the browser.
FAQ
Is a responsive website the same as a mobile website?
A responsive website adapts one set of pages to every screen size. Older “mobile sites” were separate versions on an m. subdomain. Responsive is the approach most businesses should use now.
Can a website send push notifications?
Yes, in Chrome and Firefox, using web push. Safari on desktop has its own system, and iPhones do not support web push yet.
Do apps help with SEO?
Not directly. Search traffic goes to web pages. Google can index app content with app indexing, but your website remains the main way to be found.
Should we build iOS or Android first?
Look at your website analytics to see which devices your visitors use, and start with the larger group.
Start with what customers need
The best mobile choice is the one that fits how your customers behave and what your business can maintain well. For most companies that is a fast mobile website first, with an app later if usage justifies it. If you want help planning either, see our custom development services.
