A desktop application is installed on each computer and usually keeps its data in a local database, so it keeps working without internet. A web application runs in a browser from a server, so every branch and device sees the same data. Commission desktop for one site with weak connectivity, web for several sites, and a hybrid for both.
This guide is for an owner or manager who has been told "make it desktop" or "make it web" for a POS, billing, CRM, school or stock system and does not know which to ask for. It is about software you commission, not about choosing a ready-made product. If you already know your users are spread across branches, phones and home offices, our web application development page explains how that kind of system is built. If you are still deciding whether to commission anything, start with custom software versus ready-made software.
Key takeaways
- The real choice is where the data lives: on one computer, on a server everyone reaches, or on both with sync between them.
- Desktop software fits one site, one or a few computers, weak internet and fast counter work with local printers and scanners.
- A web application fits several branches, a remote owner, phone access, and portals for customers or staff.
- A hybrid keeps a local copy at each site and syncs to a central server. It solves both problems and costs more to design and test.
- A web application works offline only if offline mode is built in. It is not automatic.
- Backups are your job with desktop software and the hosting side's job with a web application. Decide who owns them in writing.
- If a ready-made product already fits how you work, commissioning either kind is the wrong move.
What is the difference between a desktop application and a web application?
A desktop application is a program installed on a computer, often with its database on the same machine or on the office network. A web application is opened in a browser and runs on a server, with one central database. The difference shows up in internet dependence, where data lives, how updates arrive and who can reach the system.
| Question | Desktop application | Web application |
|---|
| How is it installed? | An installer is run on every computer | Nothing to install. Users open an address in a browser |
| Does it need internet? | No, for a single computer with a local database | Yes, unless an offline mode has been built in |
| Where does the data live? | On the computer or an office server | On a hosted server, in one central database |
| How do updates arrive? | A new version is installed on each computer | The server is updated once and everyone gets it |
| Can several branches use it? | Only with a shared server, a network link or sync | Yes. Every branch reaches the same database |
| Who does backups? | You do, on a schedule you must check | The hosting side, as part of the service you agree |
| Which devices work? | The operating system it was built for, usually Windows | Any device with a modern browser, including phones |
Two points in the table are often misunderstood. A desktop program with a simple local database file is built for one computer. SQLite, a common choice for this, describes itself as local storage for individual applications and devices, and its own documentation recommends a client and server database when many computers must use the same data over a network. And "web" does not have to mean the public internet: a web application can be hosted on a server inside your own office.
When does a desktop application or offline-first system fit?
A desktop application or offline-first system fits when work happens at one site, on one or a few computers, and must continue when the internet or the server is unreachable. Typical cases are a single shop counter, a clinic front desk, a school office or a workshop where a stopped screen means a stopped queue.
Signs that point this way:
- One location. A single counter or office with no need to see data from anywhere else.
- Unreliable internet. Connections that drop during trading hours, or sites where a good line is not available.
- Speed at the counter. Barcode scanning and receipt printing where every second per sale matters. Installed software talks to local receipt printers, scanners and cash drawers directly, which is simpler than doing it from a browser. This is a software integration question; the devices themselves are bought separately.
- Data kept on site. A policy or preference that records stay on your own computer.
- No recurring hosting. Nothing has to be rented each month for the system to run.
The price of these benefits is responsibility. If the data sits on one PC, a failed disk, theft or a virus can take every record with it unless a tested backup exists somewhere else. The operating system matters too: Microsoft ended support for Windows 10 on 14 October 2025, and PCs on it still run but no longer receive security updates unless they are enrolled in Microsoft's Extended Security Updates programme, so a desktop system has to be kept working on a supported version of Windows.
When does a web application fit?
A web application fits when more than one place or person needs the same live data: several branches, an owner who checks figures from home, staff on phones, or customers who log in. One central database removes the copying and merging that separate desktop installations require, and one update reaches every user.
Signs that point this way:
- Multiple branches. Stock, customers and sales must be visible across locations on the same day.
- A remote owner or head office. Reports are read by people who are not at the counter.
- Mobile access. Sales staff, technicians, teachers or drivers use the system on a phone or tablet.
- Portals. Customers, parents, dealers or suppliers need their own login to see orders, fees or statements.
- Integrations. The system must exchange data with payment gateways, accounting software, messaging or an online store.
- A mixed set of devices. Some users are on Windows, some on a Mac, some on a phone.
The cost is dependence on the connection. If the internet or the server is down and no offline mode was built, work stops at every site at once. Hosting, a domain, security updates and backups also become ongoing items that someone has to own.
What is the hybrid option between desktop and web?
The hybrid option keeps a working copy of the data at each site and a master copy on a central server, with software that syncs the two. Staff keep working when the connection drops, and the owner still sees every branch. It is built either as local-first software with sync or as a web application with an offline mode.
- Local-first with sync. An installed application writes to a local database first, then sends changes to the server when a connection is available. This suits busy counters. Our guide to offline-first POS architecture covers how sync and conflicts are handled.
- Web application with offline mode. A progressive web app (PWA) is a web application that can be installed from the browser and built to work offline. A background script called a service worker stores the app's screens on the device and answers from that store when the network is missing. Data entered offline is held in the browser and sent later.
Two cautions apply to browser offline mode. It is not automatic: someone has to design which screens work offline and what happens to data entered there. And browser storage is less permanent than a database file. Storage limits vary by browser, the browser can clear stored data when the device runs short of space unless it has been granted persistent storage, and a user can delete it. For that reason a PWA usually holds offline work for hours or days, not as the only copy of the records.
The hard part of any hybrid is conflict handling. If two branches edit the same customer or sell the last unit of the same item while offline, the system needs a rule for what happens when they reconnect. Those rules are business decisions and should be written down before development starts.
What changes in cost and maintenance between desktop, web and hybrid?
Cost and maintenance change with the number of platforms, the sync logic, hosting and who looks after backups and updates. A single-computer desktop system has the fewest moving parts. A web application adds hosting and security upkeep. A hybrid adds sync and conflict handling, which is usually the largest extra item to design and test.
| Cost driver | Desktop | Web | Hybrid |
|---|
| Build effort | Lowest for one computer; rises with a network or multi-user version | Moderate; one codebase serves all devices | Highest; the local app, the server and the sync between them |
| Hosting | None, or an office server you maintain | Ongoing server and domain costs | Ongoing server costs plus the local installations |
| Rolling out updates | Each computer is updated | One server update | Server update plus each local installation |
| Backups | Your responsibility on site | Part of the hosting arrangement | Central backup, with local copies as a fallback |
| Adding a branch | New installation, plus a way to combine data | New logins only | New installation and a sync setup |
| Adding phone access | A separate app has to be built | Usually already available in the browser | Available through the server side |
| Testing | One operating system, several versions | Several browsers and screen sizes | Both, plus offline and reconnect scenarios |
| Support | Visits or remote access to each computer | Central, on the server | Both |
This guide gives drivers and not figures, because a price depends on the modules and rules of the particular system. For published market ranges, clearly labelled as such, see our guide to custom software development cost.
Worked example: a two-branch shop leaving a single-PC billing program (illustrative)
This example is made up to show the reasoning. It is not a client project and it carries no prices. A shop has run a billing program on one PC for years. The owner opens a second branch, and the program cannot share stock or customers between the two.
| Requirement | What it rules in or out |
|---|
| Both branches must see the same stock and customer balances | Two separate desktop installations are ruled out. Data must be central |
| The owner wants daily sales on a phone | A server and a browser view are needed. Desktop only is ruled out |
| The connection at the second branch drops a few times a week | A web application with no offline mode would stop the counter. It is ruled out for billing |
| Each branch has one counter with a receipt printer and scanner | The counter software must print and scan reliably without a connection |
| Ten years of customers and items sit in the old program | A data migration is part of the project, whatever the choice |
The reasoning lands on a hybrid: counter software at each branch that works from a local copy and syncs to a central server, plus a web dashboard for the owner. The team then writes the conflict rules. For example, stock is deducted at the branch that sold it and corrected centrally at sync, and customer balances are updated only on the server so two branches cannot both extend the same credit.
Change one fact and the answer changes. If both branches had dependable internet with a mobile data backup, a plain web application would be simpler and cheaper to maintain. If the second branch never opened, the old desktop program with a proper backup might still be enough.
Can an old desktop program be moved to the web?
An old desktop program can be moved to the web, but it is a rebuild of the screens and logic with a migration of the data, not a conversion. The existing database is usually the most valuable part. The work starts by listing what the program really does, including rules nobody wrote down, and then moving in stages.
The common routes are to rebuild module by module while the old program keeps running, to move the database to a server first and replace screens later, or to keep the desktop program for counter work and add a web layer for reports and remote access. Our legacy software modernization page explains how these routes are assessed and sequenced.
When is desktop versus web the wrong question?
Desktop versus web is the wrong question when a ready-made product already does the job, when the workflow itself is not agreed, or when the real need is a backup or a report. In those cases commissioning new software of either kind adds cost and delay without fixing the cause.
- A ready-made product fits. A standard shop counter, a simple customer list or a small school register is often served by existing software. For example, Timeline POS is free, offline retail POS software for Windows. Test a product like that before commissioning anything.
- The process is not settled. If staff disagree on how a sale, an admission or a return should work, no architecture will fix it.
- The worry is losing data. An automatic off-site backup of the existing program may solve the problem at a small fraction of the effort.
- Only reports are missing. A reporting layer over the current database can be enough.
Glossary: desktop application, a program installed on a computer; web application, software that runs on a server and is used through a browser; PWA (progressive web app), a web application that can be installed from the browser and built to work offline; offline-first, a design where the software works from local data and treats the connection as optional; local database, a database stored on the user's own computer or office server; sync, the process that copies changes between local copies and the central server.
How Timeline Digital approaches the desktop or web decision
Timeline Digital is a custom software development company founded in 2013 and headquartered in Islamabad, Pakistan, that builds web applications and offline-capable business systems as managed projects, with the choice between desktop, web and hybrid made from your requirements. The free pilot of 2 to 3 key modules is ready in about 2 days. Timeline Digital does not publish prices for custom software, because every project is custom. The price is set in three steps: we analyse your requirements, build a free pilot of 2 to 3 key modules, and after you approve the pilot we agree the scope, milestones and commercial terms in writing. Any change request outside the approved scope is reviewed and agreed with you before extra work begins.
