Web app

Rédigé par David Brulin, co-fondateur de Quai des Balises

Web app is an application that runs inside a web browser and is accessed through a URL, requiring no download or installation. It combines the reach of a website with the interactivity of software, letting users create, process and manage data directly online across desktop and mobile devices.

How a web app works

A web app is software delivered over HTTP/HTTPS and rendered in the browser. The user types a URL or follows a link; the server (and increasingly the browser itself, via JavaScript) handles logic, data and rendering. Unlike a static page, a web app is built around interaction: forms, dashboards, real-time updates, authenticated accounts and persistent data.

No installation: access is immediate through any modern browser, on any operating system.
Centralised updates: a single deployment on the server updates every user at once, with no app-store review.
Cross-platform by default: the same codebase serves Windows, macOS, Linux, Android and iOS.
Common architectures: server-rendered apps (e.g. a classic backend stack), single-page apps (SPA), and Progressive Web Apps (PWA) that can be installed to the home screen and work partly offline.

Typical examples include CRMs, ERPs, booking systems, internal business tools, online editors and SaaS platforms — anything that needs logic and data, not just content.

Web app vs website vs native app

The three terms are often confused. A website mainly presents information; a web app lets the user act on data inside the browser; a native app is installed on the device and compiled for a specific platform.

Criterion	Website	Web app	Native app
Primary purpose	Display content	Interact with data	Interact with data
Access	URL in browser	URL in browser	Install from app store
Installation	None	None (optional via PWA)	Required
Updates	Server-side, instant	Server-side, instant	Store review, user updates
Platform reach	All browsers	All browsers	Per OS (separate builds)
Device hardware access	Very limited	Partial (camera, GPS, notifications)	Full
Offline use	No	Limited (PWA caching)	Yes

In practice the line is a spectrum: a content site with a few interactive features sits between a website and a web app, and a PWA narrows the gap with native apps for many business use cases.

When to choose a web app

For most B2B and internal-tool projects, a web app is the pragmatic default because it removes deployment friction and reaches every user from one codebase. It is a strong fit when:

You need to reach users on any device without managing separate platform builds.
Fast, frequent updates matter and you want to avoid app-store review cycles.
The product is a business tool — CRM, ERP, dashboard, back-office or SaaS — where data and workflows dominate over device hardware.
Users access the tool from shared or managed workstations where installing software is impractical.

A native app becomes preferable when the product depends heavily on device hardware, full offline operation, or background processing. Many teams combine both: a web app as the core, plus a native or PWA layer for specific mobile scenarios. Accessibility standards such as WCAG (levels A, AA, AAA) apply to web apps just as they do to websites, and should be planned from the start.

Questions fréquentes

No. A website primarily presents content for reading, while a web app lets users actively work with data — submitting forms, managing accounts, editing records or running workflows in the browser. Both are accessed by URL, but a web app behaves like software, not a brochure. The distinction is functional rather than technical, and many products sit somewhere between the two.

No installation is required: a web app runs in the browser and is reached through a URL, on any operating system. A Progressive Web App (PWA) can optionally be added to the home screen and offer limited offline use, but this is a convenience, not a requirement. This zero-install access is one of the main reasons businesses choose web apps over native ones.

A native app is downloaded from an app store and built for a specific platform such as iOS or Android, giving it full access to device hardware and offline capabilities. A web app runs in any browser from a single codebase, updates instantly server-side, and needs no install, but has more limited hardware and offline access. The choice depends on hardware needs, offline requirements and reach.

Partially. A standard web app needs a network connection, but a Progressive Web App (PWA) can cache resources and data so that some features remain usable offline. Full offline operation comparable to a native app is harder to achieve and depends on the use case. For business tools that are mostly used online, PWA-level caching is often sufficient.

Need a custom tool accessible anywhere, without installation? We build bespoke web applications.

See our web application expertise

Définitions liées

← Retour au glossaire