✦ Buying, cost and process
What is a web app, and why most business software should be one
A web app is software that runs in a browser rather than being installed, so anyone with a login and an internet connection can use it from any device. For most business systems - quoting tools, portals, internal dashboards - that's the format that causes the fewest headaches.
Haystak · 11 August 2026 · Updated 11 August 2026 · 7 min read
A web app is software that lives on a server and is accessed through a web browser, rather than something a user downloads and installs on their own device. You log in, it runs, and when you close the tab, nothing is left behind on your machine except perhaps a saved login.
That sounds like a technical distinction, but it has real, practical consequences for a business choosing how to build a new system: how updates happen, who can use it, what it costs to support, and whether it works on the odd mix of laptops and tablets most companies actually have.
Web app vs website: what's the actual difference?
The line between a website and a web app is really about what the user does there. A website mostly presents information - pages, images, a contact form. A web app lets someone do something with data: create a quote, update a job status, view figures that are different for every logged-in user.
In practice they share the same underlying technology, and many systems are a mix - a company website with a logged-in web app tucked behind a "customer login" link is extremely common, and is exactly the pattern behind most client portals.
Web app vs native app vs desktop software
This is the comparison that actually matters when scoping a new system, because it drives cost, maintenance, and how many places the software needs to be built and kept up to date.
| Format | Where it runs | Updates | Typical use |
|---|---|---|---|
| Web app | In a browser, on any device | Instant for everyone, no user action needed | Business systems, portals, dashboards, internal tools |
| Native mobile app | Installed from an app store, one platform (iOS or Android) | User must download the update; store approval required | Field workers, apps needing camera, GPS, or offline-first use |
| Desktop software | Installed on a specific Windows or Mac machine | Manually rolled out to every machine | Specialist tools tied closely to that operating system |
The instant-update row is the one that matters most for ongoing cost. A web app fixed at 9am is fixed for every user by 9:01, with nothing to install. A native app fix has to be approved by the app store and then downloaded by each user individually - which can take days, and some users never update at all.
Does a web app work offline?
By default, no - a standard web app needs a live connection to the server it talks to. That's a genuine limitation for anyone working somewhere without reliable signal, such as a site visit or a warehouse with patchy wifi.
It isn't a hard wall, though. Modern web technology, built on standards such as service workers maintained by the W3C, allows a web app to cache data and queue actions locally, syncing once a connection returns. This covers a genuine offline need without the cost of a fully native app, though it adds real complexity and is worth scoping specifically rather than assuming it comes for free.
Deployment and updates: the case for web apps in business software
Most B2B software isn't sold to the public - it's used by a defined set of staff or customers you already know. That changes the calculation. You don't need app store discovery or the marketing benefits of a native app icon; you need something everyone can access reliably and that you can fix without visiting every desk.
- One codebase, not a separate build to maintain for iOS, Android, Windows and Mac.
- No installation step, which removes a common source of IT support requests.
- Centralised control over who has access, revoked instantly when someone leaves.
- Works on whatever device is in front of the person - laptop, tablet, or phone - without asking IT to install anything first.
Device support: what "works everywhere" really means
A well-built web app should work consistently across current versions of major browsers - Chrome, Edge, Safari, Firefox - and adapt its layout sensibly between a large monitor and a phone screen (responsive design). It's worth confirming this explicitly with any developer, since "it's a web app" doesn't automatically mean it was tested properly on a phone.
| Question to ask | Why it matters |
|---|---|
| Which browsers and versions are supported? | Very old browsers can behave differently; know the cut-off before launch |
| Is the layout responsive, or just resized? | A genuinely responsive design rearranges itself for a small screen rather than shrinking everything |
| Has it been tested on the actual devices staff use? | A simulator is not the same as a real, older tablet with a cracked screen and patchy wifi |
When a native or desktop app is still the right call
A web app is the sensible default, not a universal answer. Native apps still earn their place where deep integration with a device's hardware is central to the job - barcode scanning at speed, GPS tracking in the background, or work that genuinely happens with no signal for hours at a time. Specialist desktop software is occasionally still right where it must integrate tightly with other Windows-only tools already on that machine.
If you're not sure which category your project falls into, that's a five-minute conversation worth having before any build starts - see our thoughts on choosing between a web app and a mobile app, or look at our custom web application development service directly.
✦ Where this fits
More on this from us: our custom web application development service.