Skip to main content

Desktop App Development

Desktop software, and the narrow set of reasons to still build it. Usually hardware, offline, or file-system work that a browser cannot reach.

The Reasons That Still Justify It

Most business software belongs in a browser. Desktop is worth building when something specific rules that out.

Hardware a browser cannot reach. Scanners, scales, label printers, till systems, serial and USB devices, specialist instruments. This is the most common legitimate reason by a distance.

Sustained offline use. Not a cached page, but hours of real work with no connection and reliable sync afterwards.

Heavy local processing. Large files, video, CAD, anything where uploading to a server is the bottleneck.

Deep file-system work. Watching folders, batch processing, integrating with locally installed software.

A locked-down environment where the browser is restricted or the network is not available.

If none of those apply, a web application is cheaper to build, distribute and maintain, and it removes the whole problem of getting updates onto machines.

What Desktop Costs That Web Does Not

Distribution. Getting the software onto machines, and getting updates onto them afterwards. This is a permanent operational cost that browsers simply do not have.

Code signing. Certificates, renewals, and the warnings users see when it lapses.

Per-platform work. Windows and macOS differ in installation, permissions, file handling and expectations.

Version fragmentation. Some users will be on a build from eighteen months ago. Support has to cope with that.

Auto-update infrastructure, which is not free and is not optional if you want anybody on the current version.

The Middle Option

Where the requirement is hardware or local files but the interface is ordinary, Electron lets a web application run as a desktop app with access to the machine. One codebase, familiar tooling, and genuine access to devices and the file system.

The trade is memory and installer size, which for a business tool used all day is usually acceptable. It is frequently the right answer when the only reason for desktop is one specific capability.

What Moves The Price

How many platforms. Windows only is common in business and much cheaper than both.

The hardware integration itself. Each device is its own body of work and vendor documentation quality varies wildly.

Offline and sync. If two people can edit the same thing offline, conflict resolution is a real design problem.

Update mechanism, and whether the environment permits automatic updates.

Whether it must work without administrator rights on locked-down machines.

Where These Projects Go Wrong

Choosing desktop by default. Because the previous system was desktop, rather than because something requires it.

Underestimating distribution. The build is the easy half; getting it installed and kept current across an estate is the ongoing cost.

No plan for old versions. They will exist. If the server cannot cope with an older client, users get stranded.

Hardware assumptions. Testing against one scanner model and discovering the customer has three others.

Questions To Ask Whoever Builds It

  • What specifically requires desktop? Then check it against what a browser can now do.
  • How do updates reach users? And what happens if somebody declines.
  • Which platforms, and is the estimate for both?
  • What hardware exactly, and have you tested against the actual models?
  • What happens offline, and how does sync resolve conflicts?

A Brief You Can Send Anyone

What it does: [the job, not the technology]
Why not a website: [the specific blocker]
Hardware involved: [makes and models]
Platforms: [Windows, macOS, or both]
Offline requirement: [none, brief, or hours]
How many machines: [and who administers them]
Whether users have admin rights:

How We Advise

We will check the browser route first, because if it works it is cheaper in every dimension including the ones that arrive later. Where genuine hardware or offline requirements exist, Electron usually gives you desktop capability without a separate codebase.

If the answer is that a browser will do, web application development is the cheaper route, and a progressive web app covers installation and offline for a good proportion of cases.

Get in touch with what the software needs to touch.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.