Most business tools belong in a browser. An installed desktop app earns its place in a small number of situations: the work needs the local file system, it needs hardware plugged into the machine, it has to keep going when the connection does not, or the files are large enough that uploading them is the slowest part of the job. A fifth matters to some firms: data that should stay on the machine. If none of those describe your tool, a web app is the simpler answer, and usually the honest one.
That is a different question from whether you need a site or a tool at all, which the guide to website vs web app covers. This post is the axis after it: once you know you are building software, does it run in a browser tab, or does somebody install it?
When does a desktop app beat a web app?
When the tool needs something a browser is deliberately not allowed to do. Four cases come up repeatedly:
- Local files at volume. A tool that walks a folder of thousands of files, reads them and writes results back alongside them is natural on the desktop, awkward in a tab.
- Hardware on the desk. Label printers, scanners, scales, card readers and older machine controllers are reached far more easily by installed software.
- Work that continues offline. Sites with no signal, vans, warehouses, plant rooms. An installed app holds its own data and syncs later.
- Large files. Video, CAD drawings, scan bundles. If the upload is the bottleneck, working where the file lives is much faster.
The fifth case is quieter. Some records are ones the owner would rather not put on somebody else's server, and some sit under an agreement about where they may be held. If a contract or a regulator governs where your data can live, take regulated advice on your own obligations.
Browsers have closed part of this gap. Mozilla's documentation for the File System API describes an interface for reading, writing and saving files and reaching directory structure on a user's local device or a user-accessible network file system, says access is disallowed unless the user specifically permits it, and says the feature works only in secure contexts, in some or all supporting browsers. Last verified: 7 September 2026. Read that page before planning around it, because browser support changes. It suits a tool that opens a file the user picked, not one that watches a folder.
What does a web app do better for most businesses?
Nearly everything about getting the tool into people's hands and keeping it there. No install, no packaging, no certificate, no version drift, because everybody is on whatever you deployed last.
- Rolling out to a new starter is a login, not a visit to their machine, and removing access when they leave is one switch.
- One codebase covers Windows, macOS, Chromebooks and the tablet in the workshop.
- Fixing a bug means deploying once, not persuading twenty machines to update.
So the default is a web app, and overturning it takes a clear reason from the section above. A desktop app is not better software, just a different trade: the install chain in exchange for local access.
What does installing software mean for packaging, signing and updates?
It means you own a release chain, not just a codebase. Three parts matter first.
On Windows the modern packaging format is MSIX. Microsoft's MSIX overview describes it as giving an app a reliable, clean install and uninstall with no leftover files or registry entries, states that all MSIX packages must be signed before installation, and says only the changed 64 KB blocks are downloaded on update. Last verified: 7 September 2026. Check that page before planning a Windows release, because packaging guidance moves.
On macOS the extra step is notarisation. Apple's documentation on notarising macOS software before distribution describes the notary service as an automated system that scans software for malicious content, checks for code-signing issues and returns the results, and says the ticket it issues tells Gatekeeper the software was notarised when a user first installs or runs it. The page lists a Developer ID certificate, the hardened runtime and a secure timestamp among its requirements, and states that beginning in macOS 10.15, all software built after 1 June 2019 and distributed with Developer ID must be notarised. Last verified: 7 September 2026. Read Apple's page before planning a Mac release, because the requirements have changed before.
Signing is not a step you defer to version two. The Electron code signing documentation states that both Windows and macOS prevent users from running unsigned applications, and that the Squirrel.Mac updater requires the app to be signed for automatic updates to work at all. Last verified: 7 September 2026. Read that Electron page before planning a release, and if you build with a different toolkit, read its own signing page rather than assuming this carries across.
What does the release chain actually cost you?
Time and attention that never touch the product. Installed software brings four jobs with it, and each has to be settled before the first user opens the app. InnerZero, the privacy-focused AI desktop assistant built by Summers Solutions, is desktop software of this kind.
- Identity comes before code. The Developer ID certificate Apple's page lists as a requirement, and a Windows signing identity, both wait on somebody else verifying your business. Engineering cannot speed that up, and nothing ships until it arrives.
- A clean machine is the only real test. A build that runs where it was compiled proves little, because that machine already has every tool the app needs. A spare laptop finds the missing dependency in a minute.
- Uninstall is part of the product. Microsoft's MSIX overview above makes clean removal a selling point of the format, which tells you how often the alternative used to happen.
- Every release repeats the chain. Build, sign, notarise, package, publish, every time. Pick the update route before the first release, because retrofitting one means asking every user to download the app again, and script the rest early.
None of that argues against desktop software, only for being sure you need it.
How do you decide for your own tool?
Write down the one job the tool exists to do, then ask five questions.
- Does it need files on the user's machine, in numbers or sizes that make uploading them silly?
- Does it need to talk to a device plugged into that machine?
- Does it need to work with no connection, for hours rather than seconds?
- Is there a real reason the data must not leave the building?
- Would the people using it be worse off for having to install and update it?
Two or more yes answers among the first four, and a desktop app is likely right. A yes to the last one alone argues for the browser. If they are all no, build the web app and revisit when a limit bites.
There is a middle road too: a web app for the everyday work plus one small installed helper for the local part, such as printing labels, which confines the install chain to the piece that needs it.
Frequently asked questions
Can a desktop app and a web app share code?
Often a good deal, particularly the data model and the business rules. One common route goes further: build the interface with web technology and ship it inside a desktop shell such as Electron or Tauri, which is why the Electron page above applies to so much business software. That buys a single interface codebase, but it does not exempt you from the packaging, signing and update work above.
Does the app have to go in an app store?
No. Direct distribution is normal on both platforms, and Microsoft's MSIX overview above points to App Installer as the route for delivering updates without the Store. Last verified: 7 September 2026. Check current Microsoft and Apple distribution guidance before deciding.
What happens if we do not sign the app?
The Electron code signing documentation linked above states that both Windows and macOS prevent users from running unsigned applications, and that running one anyway takes multiple advanced and manual steps. It also says Squirrel.Mac requires signing for automatic updates to work at all. Last verified: 7 September 2026. Read that page before relying on any of it. Signing is part of the build, not an extra.
Can a desktop app still connect to our other systems?
Yes, to a server, an API or a shared database, just as a web app does. The difference is that it can keep working when that connection drops, then reconcile when it returns.
If you have a tool in mind and are not sure which side of the line it falls on, the desktop app development page sets out how we approach installed builds. A short conversation is usually enough to settle it.
Need a practical digital build?
Summers Solutions can shape websites, workflow tools and public product pages around a clear business goal.