When desktop is the right choice
We recommend desktop in three situations: when work must not stop if the connection drops, when the software runs alongside hardware, or when data has to stay local. Outside those, most business applications can run in the browser, and usually they should. We decide in the scoping call, and if a web application covers your needs, we’ll say so.
How long does a desktop application take to build?
A tool that does one job and keeps its data on the computer takes 3-5 weeks. Two things add time: working offline and syncing with head office once the connection returns, and talking to devices such as receipt printers, barcode scanners or scales. Applications that need these take 6-12 weeks.
| Scope | What it includes | Time |
|---|---|---|
| Single-purpose tool | One flow, local data, export | 3-5 weeks |
| Offline business app | Roles, local database, sync when back online | 6-10 weeks |
| Device-integrated app | Works with printers, barcode scanners, scales and similar hardware | 6-12 weeks |
| Modernising a legacy desktop program | Migrating existing data, renewing the interface and foundations | 4-8 weeks |
A typical budget for this service is US$3,500-14,000, excluding VAT (as of October 11, 2026). Where you land in that range depends on the number of user types, the systems to connect and how much design work there is; the exact figure comes as one price once the scope is written down.
Cost and timeline guide
Every budget band, our rates by role and the timeline for each scope tier, on one page.
Pricing
The four engagement models, payment terms and what the price covers.
Offline behaviour can’t be bolted on later
How the application behaves without a connection (which data lives on the device, how conflicts are resolved when it reconnects) has to be planned into the first version. Adding it later means rebuilding the data model.
Is desktop right for you? A quick check
Choosing desktop means installing the app on each computer, digitally signing the installer and rolling out updates. If the first list sounds like your work, desktop can be worth that extra effort. If most of your answers sit in the second list, a web application will be less hassle.
Desktop is likely the right choice
- The till, warehouse or production line must keep going when the internet drops
- The software works alongside a device such as a printer, barcode scanner or scale
- Data has to stay on computers inside the company
- It will replace an old desktop program that has been in use for years
A web application may suit you better
- Users will connect from different places and different devices
- You want to give customers or suppliers access
- The app will change often and everyone needs the new version on the same day
- Connectivity isn’t a problem and there is no device to connect to
How does a desktop app work offline?
Every record is written to a local database on the computer first, then sent to head office in order once the connection returns. In a point-of-sale app, that means sales carry on while the internet is down. It sounds simple, but a few questions need clear answers at the planning stage.
- Which data lives on the computer: the full product list and prices, or only the day’s records?
- If the same item is sold at two tills while both are offline, how is stock corrected?
- How long can the connection be down: a few hours, or a few days?
- If a price changes at head office, when and how does it reach a till that is offline?
- Will users see on screen that they are offline and how many records are waiting to be sent?
Preparing for an app that works with hardware
During discovery we ask for the make and model of every device you use, and its technical documentation if there is any. The most common problem with device integration is not having the real device to hand during development. If your branches use different models, listing each one early saves surprises later.
Receipt and label printers
The model and connection type (USB, network or Bluetooth) should be known up front. Receipt and label templates go into the scope too.
Barcode scanners
Most scanners behave like a keyboard and connect easily. If you need a special scanning mode, test it early.
Scales
How weight readings reach the program varies by model. We need the device’s technical documentation.
A test device
Ideally a sample device stays with the team throughout development. If not, we test remotely on your computer.
Moving from a legacy desktop program to the new version
We recommend a staged switch: the old program and the new one run side by side for a while, and everyone moves across only once the data has been checked. The risk in replacing a program that has run for years lies in moving the data and the team’s habits.
- 01
Review the existing program
We map the screens, reports and data structure, and note which task people do on which screen.
- 02
Trial data migration
A copy of the real data is moved into the new structure. Missing or broken records are checked with you.
- 03
Side-by-side use
A few users try the new version on real work, while the old program stays open as a fallback.
- 04
Switch-over day
The final data transfer runs and everyone moves to the new version. If you like, the old program is kept as a read-only archive.
Frequently asked questions
Desktop app or web app?
If work must continue offline, the software has to run with hardware, or data must stay local, go desktop; if none of those apply, a web application is faster to build and easier to maintain. We decide that in the scoping call.
Will it run on both Windows and macOS?
Yes, we prepare installers for both operating systems. Only where a hardware requirement is specific to one operating system is that part handled separately.
Can you rebuild our old desktop program?
Yes. The first step is reviewing the existing program and its data structure; how the data will be migrated, and how much can be kept, becomes clear after that review.
Do updates have to be installed on each computer by hand?
No. The app can check for a new version when it starts and install the update once the user agrees. If you would rather roll updates out across the company yourselves, we can plan for that instead.
Why does a security warning appear when the installer is opened?
Windows and macOS warn about installers that aren’t signed. To avoid this, the installer is digitally signed. The certificate and developer account needed for signing carry a yearly fee, and it’s best to have them in your company’s name.
Where is the data kept, and how is it backed up?
The data sits in a local database on the computer where the app is installed. During discovery we agree how often it is backed up and where a second copy is kept: a separate disk, a company server or a cloud account of your choice.