Choosing between a mobile website vs mobile app can feel like a big, costly bet. For most goals, start with a responsive website, and build an app only when you need device features or a constant presence.
This page is part of a wider guide to mobile website development, which covers the basics of building for phones.
| Item | Value |
|---|---|
| Global browser use covered by browsers that support PWA functionality | 90% (as of April 2019) |
| Users who abandon a mobile site that takes more than three seconds to load | 53% (Google data, March 2016) |
| Data saved by Twitter Lite, a PWA | up to 70% |
| Rise in conversions at Alibaba.com after moving its mobile site to a PWA | 76% |
| Increase in shopper sessions at MakeMyTrip after launching a PWA | 160% |
These figures come from the GOV.UK Service Manual and a Think with Google report on progressive web apps. Figures can change, so check the source before you rely on them.
When a responsive mobile website is enough
The GOV.UK Service Manual says a responsive website is usually the best way to make a service work on whatever device or browser people choose, as set out in its guidance on mobile approaches. It is written for government services, but the reasoning is useful for any project weighing the same trade-offs.
Compared with native apps, the manual says responsive websites:
- do not require anyone to download anything, so they are easier to find and use and save on the user’s data allowance;
- are usually easier and less expensive to develop, maintain and iterate, because they do not need different versions for different operating systems;
- make it easier to measure how the service is used than measuring an app after it has been downloaded.
A website is also where people tend to arrive first. Think with Google’s July 2017 report notes that most users typically land on your website first, so a weak mobile site costs you the very first impression.
When a native app earns its place
The same manual says an app may be the right solution in some circumstances. It gives three examples:
- the service only works if it has a persistent presence on the user’s device, such as some apps that help people live a healthier lifestyle;
- the service needs to interface with specific features of the user’s device;
- the user needs to collect and store data but will not have consistent internet access.
Security can also tip the balance. According to the GOV.UK Service Manual, encrypting offline user data is easier and more secure in a native app. The manual also warns that a native app should work the same way on a variety of operating systems, such as Android and iOS, which adds ongoing work.
Cost is the other side of the ledger. A Smashing Magazine article from December 2018 describes building a dedicated native app as something that can become an incredibly costly gamble if users do not take to it.
Where progressive web apps fit in
Between the two sits a middle route. Progressive web apps are websites that use modern browser features to behave like apps, and our guide to progressive web apps goes deeper on how they work.
The GOV.UK Service Manual says the user experience of a PWA on a handset is almost identical to a native app. Unlike native apps, though, PWAs have a single codebase that works on the web like any normal website. Users can reach these native features through the browser:
- offline mode and push notifications;
- Bluetooth and speech recognition;
- file access and geolocation;
- camera and sound recording, and device motion.
Support is broad: the manual says the browsers that support PWA functionality equate to 90% of global browser use as of April 2019. It also lists drawbacks, such as storage on a device being a limiting factor, so it recommends weighing a PWA case by case. You can read more in its section on progressive web apps.
Company-reported results show why the approach gets attention. Think with Google’s July 2017 report says Twitter Lite saves up to 70% on data and loads 30% faster. It also says Alibaba.com saw a 76% rise in conversions, and MakeMyTrip saw a 160% increase in shopper sessions. These are single-company outcomes, so treat them as examples rather than promises.
What the numbers say about speed and usage
Speed matters on any route. Google data from March 2016, cited in the Think with Google report, says 53% of users abandon a mobile site if it takes more than three seconds to load. That is why mobile page speed optimization belongs in the plan whether you build a site, a PWA or an app.

App usage is also concentrated. comScore figures cited by Smashing Magazine in December 2018 put roughly 70% to 80% of all time spent in mobile apps in four categories: entertainment, social media, instant messaging and games. If your idea sits outside those, winning attention in an app store may be harder than it looks.
The same article reports Google data showing the Infobae PWA with a 5% bounce rate, against 51% on its mobile web experience. It also notes that retailer Crabtree & Evelyn has the funds to build a native app counterpart to its website but chose not to. Again, these are individual cases and not a rule.
How do you choose for your goal?
Work through these steps in order. Stop at the first one that settles the question.
- Find out who your users are, which platforms they use and what kind of connectivity they have. The GOV.UK Service Manual lists these among the things to know before developing a PWA.
- List the device features you truly need. If you need persistent presence, encrypted offline data or deep device access, a native app becomes a serious option.
- If the need is mostly content, forms, booking or checkout, start with a responsive site.
- If you want app-like touches such as offline use or push notifications without separate builds, test a PWA first.
- Add a native app later if your data shows loyal users who would benefit.
That last step matches Think with Google’s suggestion that a PWA and a native app can work in tandem. Retailers, it says, can use a native app to engage loyal users who are more likely to install one, and a PWA to reach new users. The report describes this as a way to prompt PWA users to download the app later.
Frequently asked questions
Is a mobile website cheaper than a mobile app?
Show answer
Usually, yes. The GOV.UK Service Manual says responsive websites are usually easier and less expensive to develop, maintain and iterate, because they do not need different versions for different operating systems.
Can a mobile website work offline?
Show answer
A plain website generally needs a connection, but a PWA can use offline mode. The GOV.UK Service Manual lists offline mode among the native features users can reach through the browser with a PWA.
Do you need both a website and an app?
Show answer
Not necessarily. Think with Google says PWAs do not necessarily have to replace native apps and can work in tandem with them, but a single well-built site or PWA can be enough for many goals.
Will PWAs replace native apps?
Show answer
One Smashing Magazine author answered “Yes, but not for everyone” in an article dated December 2018. That is an opinion rather than a settled outcome, and the GOV.UK Service Manual still describes cases where a native app fits better.



