Website or web app: how to choose?

You’ve got a project. You know what you want to do. And then comes THE question that brings everything to a standstill: ‘Should we build a website or an app?’

If you’ve ever asked this question to those around you, you’ve probably received a range of opinions, from the most indecisive to the most precise from those in the know. That’s to be expected: most people (and even some service providers) reduce digital solutions to two binary choices – a website or an app – when in reality there’s a third option, one that’s far more common than you might think: the web app.

There is no single ‘best’ answer. There is only one right answer that will suit your project. To find it, you first need to understand what really sets these three solutions apart.

What is a website?

Let’s start with the basics: the website. It is, first and foremost, a space where you can view information (news, articles, information about a brand, etc.), but where you remain purely passive: you simply browse and read without logging in. You look for some content and then leave.

This is typically the case with Bow;, the website we designed for the violinist Marion Devaud: a minimalist site with a refined aesthetic and a clear objective – to introduce the artist and make visitors want to find out more. The two-page showcase website serves as both a business card and a digital portfolio, with no data being entered by the visitor.

What is a web application?

A web application is a website that takes action: users no longer simply browse passively, but interact with data, track their progress, complete tasks…

Why is this format winning over more and more businesses?

Ease of implementation: You don’t need any knowledge of native app development – the app is ‘just’ a slightly more advanced website. It’s even possible to create software that can be accessed directly from a web browser: AI, CRM, social media… the list goes on!

Instant access: No store rules to follow, no approval or installation to wait for – simply share a link and the tool is ready to use in an instant. For an SME looking to get a tool into its users’ hands quickly, this is the perfect solution!

An update invisible to the user: Unlike a mobile app, where every change requires a new version to be released and approved by an app store, the web app is updated on the server side. The user always sees the latest version, without having to do anything.

A single technical platform for all devices: computers, tablets and smartphones. The web application adapts to the screen, eliminating the need to develop and maintain multiple versions in parallel. This often makes it possible to keep costs more reasonable than with an equivalent mobile app.

That said, this convenience comes at a price: without an internet connection, the web app loses most of its appeal. This is precisely where the native mobile app retains a decisive advantage, as we shall see shortly.

A quick technical note: whether it’s a website or a web application, both can be converted into a PWA (Progressive Web App): a version that can be installed directly onto the home screen, with partial offline functionality, without ever having to go through the App Store or Google Play.

And what about the mobile app in all this?

That’s often where articles on the subject stop: website versus web app, full stop. But in the reality of a project, there’s a third point of comparison missing: the mobile app that you download from an app store.

Why choose this option, rather than a web application, in some cases? It all comes down to a needs analysis: if the app is intended for mobile use or to utilise native features, then you need to opt for an app that goes beyond what a website can offer.

Our Transpo’matic app, which brings together Swiss public transport timetables, is not intended to be used on a computer but rather in everyday life, in just two seconds. It is possible to create a web version, but that won’t be its main use. The same logic applies, albeit in a different context, to Les Frères Brigands: these outdoor adventure games are often played far from any network coverage, in the countryside or mountains, using native features (geolocation, photos, etc.). It would be impossible to integrate these into a web app; the experience simply wouldn’t work.

The comparison table

To give you a clear overview at a glance, here’s how these three solutions compare on the criteria that really matter to an SME:

Criterion	Website	Web application	Mobile application
Development costs	Generally the most accessible	Medium to high, depending on the features	The highest overall
Visibility on Google	Very good (natural search engine optimisation)	Well, depending on the architecture chosen	Low to none (excluding blinds)
Internet connection required	Yes, continuously	Yes, except for the partial offline PWA variant	Not necessarily (offline use may be possible, depending on the app)
Downloadable	Depending on the device and browser	Often as an installable PWA or as a full-featured app	Yes, compulsory
Update frequency	Low to moderate	Continue, without user intervention	Depends on the approval of the app stores
Maintenance	Light	Moderate	More resource-intensive (versions, add-ons, operating systems)

This table shows general trends: every project has its own constraints, and that is precisely why we discuss them before making a decision.

How to decide: questions to ask yourself

You don’t need to be an expert to guide your thinking. Three questions are enough to narrow down your options:

Do my users need to interact with the content, or just view it?
If the answer is ‘just looking’, a website will most likely suffice. If they need to take action, interact with the site or follow a specific path — then we’re looking at an app.

Do they need offline access, or do they use it very frequently on a daily basis?
The more intensive the usage and the more important network autonomy becomes, the more a native mobile app becomes the preferred choice over a web-based solution.

Do my budget and timetable allow for a native solution, or would a lighter solution suffice?
A mobile app requires more time, validation and budget than a web app. If time is tight or the budget is limited, it’s worth checking first whether a simpler solution already meets the need.

The case where none of the three solutions is correct

What if, to be perfectly honest, none of these three options were actually necessary? It does happen, and we’d rather tell you that than sell you a bespoke solution you don’t need.

If you need a website up and running very quickly on a tight budget, we recommend using WordPress themes in particular, as these allow you to present your information effectively without necessarily needing to incorporate bespoke features. For a basic e-commerce site with no specific requirements, Shopify does the job very well. In such cases, a bespoke solution does not offer any real added value.

Conclusion

So, website, web app or mobile app? The answer to this question, which initially held everything up, is actually quite simple: there isn’t one that’s objectively better; it’s simply the one that suits your project, your users and your context.

To help you organise your thoughts before discussing them with us or the service provider of your choice, download our free specification document: it will help you clarify your requirements and enable us to guide you even more effectively during our initial discussion.