You are about to commission custom software for your business, and the first question is on the table: desktop app or web app? A program installed on the computer at the till, or a system that opens in a browser from anywhere? The wrong choice means years of inefficiency.
As cloud and browser technologies have advanced, web apps have replaced desktop programs in many areas. Still, for needs such as barcode scanners, receipt printers, large files or working without internet, desktop apps remain strong. And today you don’t even have to pick just one approach.
In this article we compare the two approaches from a business perspective, explain the hybrid options in between (PWA, Electron, Tauri) and describe why we use web, mobile and Windows together in our own product, KATSİS.
The difference between a desktop app and a web app
A desktop app is software installed on the user’s computer that runs directly on the operating system. Since the vast majority of desktop computers in Türkiye run Windows (around 85% in 2026, according to Statcounter), in businesses “desktop app” usually means “Windows program”. Data can be kept on the local computer, on a server in the office or in the cloud.
A web app, on the other hand, runs on a server, and users access it through a browser. No installation is needed; an address and a username are enough. Cloud versions of accounting programs, CRM systems and online management panels are typical web apps.
There is also a difference between a website and a web app: a website mostly provides information, while a web app is a system where users log in, create data and get work done. This article is about the latter.
When choosing, you need to look not only at today’s needs but also three to five years ahead. A program used by five people in one office today could become a system used by fifty people across three branches and field teams tomorrow. Making the initial architectural decision with that growth in mind saves you the cost of rewriting later.
Desktop vs web app: a comparison across 8 criteria
| Criterion | Desktop app | Web app |
|---|---|---|
| Installation | Separate installation on each computer | None; a browser is enough |
| Access | From the device it is installed on | From anywhere with internet, on any device |
| Offline use | Naturally strong | Limited; partly possible with a PWA |
| Hardware access | Full access to printers, scales, card readers, serial ports, etc. | As far as the browser allows |
| Performance | Uses local resources directly | Depends on the server and connection |
| Updates | Updates must be distributed to each device | Once on the server; everyone is on the new version instantly |
| Data and backups | With local data, backup responsibility lies with the user | Centralised; backups on the server side |
| Platform | Usually a single operating system | Windows, macOS, tablet or phone, it doesn’t matter |
The table shows the general trend: if accessibility, multiple users and easy maintenance are priorities, web comes out ahead; if hardware, offline use and heavy local processing are priorities, desktop does.
When is a web app the right choice?
Today the default starting point for new business software is usually a web app. Web is by far the better option in these cases:
- Multiple locations or remote work: branches, field teams and staff working from home need instant access to the same data.
- Customer or dealer access: if outside users need to log in, asking them to install a program isn’t realistic.
- Frequently changing business rules: if price, campaign or process changes need to reach everyone at the same time.
- A mixed device fleet: if some employees use Windows, some Mac and some tablets.
- Centralised reporting: when management wants to see data from all branches on one screen.
The weak point of a web app is the internet connection. When the connection drops, work may stop; so for critical processes you need to plan an offline scenario from the start. Another issue is security: a system exposed to the internet must be protected with HTTPS, strong authentication, authorisation and regular updates. For details, see our website security guide.
When is a desktop app still the best option?
In the cloud era, desktop software is not an outdated concept. In the following cases, a desktop app, or at least a desktop component, is still the right solution:
- Heavy hardware integration: receipt and label printers, electronic scales, barcode scanners, cash drawers, industrial devices communicating via serial port or USB.
- Must run without interruption: places such as tills, production lines or warehouses where work must not stop when the internet goes down.
- Heavy local processing: large images, video, CAD files or high-volume data processing.
- Sensitive data that must stay local: environments closed to the internet where data must not leave the corporate network.
- Heavy keyboard use: shortcut-driven, instantly responsive interfaces for operators doing fast data entry all day.
For Windows desktop development, .NET-based technologies such as WPF and WinUI are mature and long-lived. Through our desktop app service we develop projects requiring hardware integration with these technologies.
In between: PWA, Electron and Tauri
The line between desktop and web is getting thinner. Three hybrid approaches stand out in particular:
PWA (Progressive Web App)
An “installable” version of a web app for computers or phones. It opens in its own window, has an icon on the desktop, can work offline to a limited extent by caching some data, and can gain capabilities such as opening and saving files. The extra cost is low; however, hardware access is still limited by the browser.
Electron
Turns an app written with web technologies (HTML, CSS, JavaScript) into a desktop program that bundles a browser engine. Many popular desktop apps use this approach. Much of the web code can be reused and full access to the operating system is possible; the downside is relatively large app size and memory usage.
Tauri
A similar approach to Electron; but instead of bundling a browser engine, it uses the operating system’s own web view and runs Rust on the back end. The result is usually much smaller and lighter apps. Its ecosystem isn’t as large as Electron’s, but it is growing fast.
The question is no longer “web or desktop”; it’s which experience you will offer to which user, on which screen.
A real example: web, mobile and Windows together in KATSİS
Our own product KATSİS is a good example showing that the answer to this question can be “both”. KATSİS is apartment and residential complex management software: it brings together dues and debt tracking, cash management, announcements, support requests, virtual POS and SMS modules. Because different users have very different needs, a single interface wasn’t enough:
- Web panel: so managers can access the system and reports from anywhere, without installing anything.
- iOS and Android apps: so residents can follow announcements, see their balance and create requests; in other words, so the most frequent tasks are in their pocket.
- Windows app: an experience that takes advantage of the speed and comfort of the desktop for users doing heavy work at a desk.
The key to this structure is that all three interfaces are connected to the same infrastructure and the same data. A payment entered in the web panel appears instantly in the mobile app and the Windows app. Since the business rules live in a single place, when a new feature is added the logic is written once; the interfaces simply adapt that logic to their own screens. For details on KATSİS and our other products, take a look at our projects page.
If you are weighing which technology to choose on the mobile side, our native vs cross-platform article is a natural follow-up to this decision.
Desktop or web? A 6-question decision guide
Answer these questions for your own project. Where the “yes” answers cluster will show you the direction:
- Question 1 — Will users access it from different locations or from outside the company? If yes, web.
- Question 2 — Is it unacceptable for work to stop when the internet goes down? If yes, desktop or a hybrid with offline support.
- Question 3 — Is constant communication with devices such as printers, scales and readers needed? If yes, desktop, or web plus a small desktop helper service.
- Question 4 — Do users use different operating systems and devices? If yes, web.
- Question 5 — Do business rules change often, and does everyone need to be on the latest version instantly? If yes, web.
- Question 6 — Must the data stay within the corporate network? If yes, desktop with a local server, or a web app hosted on-premises.
For many businesses the right answer is a web app at the core, with desktop or mobile apps connected to it for special needs. If you are designing such a system from scratch, we explain how the process works in our custom software development article.
- Have user groups and the devices they use been listed?
- Is the need for offline use clear?
- Has the hardware to be integrated been identified?
- Has it been decided where the data will be hosted?
- Have the update and distribution processes been planned?
- Has the possibility of adding mobile or web later been considered?
Frequently asked questions
Does a web app work without internet?
A classic web app requires an internet connection. Web apps developed as PWAs, however, can work offline to a limited extent by caching some data and syncing it when the connection returns. If full, long-term offline operation is required, a desktop app is the safer option.
Is a desktop app or a web app more secure?
Neither is inherently more secure. Web apps are exposed to the internet, so they need strong authentication and regular updates; with desktop apps, backing up local data, device loss and un-updated installations pose risks. Security depends on architecture and maintenance.
Can I convert my desktop program into a web app?
Yes, but this usually means redevelopment. Business rules and data structures can be preserved, while the interface and infrastructure are redesigned for the web. During the transition, it is important to run both systems in parallel for a while and migrate data carefully.
Is developing a web app cheaper than a desktop app?
If you are targeting multiple platforms and many users, the total cost is usually lower on the web, because a single codebase runs on all devices and no update distribution is needed. For a hardware-intensive job on a single operating system, a desktop app may be more economical.
Can a web app run on our own server?
Yes. A web app can be hosted on a cloud server or run on your company’s own server, accessible only from the internal network. In cases where data must not leave the organisation, this model keeps the data in-house while preserving the web’s ease of installation and updates.
Does an app built with Electron count as a desktop app?
Yes. Electron apps are real desktop apps that are installed on the computer and can access the operating system; their interfaces are written with web technologies. This makes sharing code with a web app easier, but size and memory usage are higher than native apps.
Final word
The answer to whether to choose a desktop app or a web app lies in where, on which device and under what conditions your users work. Web comes out ahead for accessibility and easy maintenance, desktop for hardware and uninterrupted operation; often the strongest solution is to use both together on a shared infrastructure. We applied this approach in our own product, KATSİS. If you would like to determine the right architecture for your project together, you can take a look at our web software and desktop app services, or directly get in touch with us.