Skip to content

Desktopapplications.

Some work does not happen in a browser: local files, devices, printers and scales, or work somewhere with no internet at all. That is when a desktop application is the only right choice.

An engineer at a large workstation in a quiet home office
Desktop applications

What you get

When desktop makes sense.

Rarer all the time, but still irreplaceable for these cases. If your case is not on the list, you probably want a web application.

Working with devices

Scales, scanners, tax devices and industrial machinery a browser cannot see.

  • Connecting to local devices
  • Receipt and tax printers and tills
  • Card and barcode readers
  • Industrial devices and machinery
  • Printing without a dialog box

How it runs

How it runs.

  1. Phase 1

    The check

    Whether desktop is really needed, or a web application solves the same thing more cheaply.

  2. Phase 2

    The smallest version

    The core workflow, trialled with a handful of users.

  3. Phase 3

    Devices and integrations

    Connecting to the equipment and the existing systems.

  4. After

    Upkeep

    Updates, monitoring and support.

Who this is for

Who it works for, and who it does not.

It makes sense if:

  • You work with devices a browser cannot see
  • The work has to run without internet too
  • You process large volumes of data locally

It does not make sense if:

  • Everything you do works in a browser - then a web application is cheaper and easier to maintain
  • Your users are on different devices in different places

This is our rarest service and the first question is always whether a web application would do. If it would, that is what we suggest, even though it is the smaller job for us.

Frequently asked questions

Questions about desktop applications.

Windows, macOS or both?
It depends on what your people use. There are approaches that share code across both, with a little more work.
How do updates reach the users?
Automatic updating is built in, so nobody has to walk round the machines. That is part of the job from the start, not an afterthought.
Can we have both web and desktop?
You can, with a shared core and shared data. More often than people think, that is the cheapest solution.

For work a browser cannot do.