Service · 03

Desktop software development.

We build programs that stay open all day in the office, the warehouse or on the production line. They run on Windows and macOS, keep data locally when the internet drops, and talk directly to printers, barcode scanners and similar devices.

Tell Us About Your Project Desktop software: timelines and budget

Scope

What we build in desktop projects

Programs for Windows and macOS that handle stock, orders, labels or reports, and keep working when the internet goes down.

  • Business applications

    Programs for stock, orders, quotes and production tracking, written around the way your team works today.

  • Offline-first

    A local database with sync, so the software keeps running when the connection drops.

  • Hardware integration

    Apps that talk directly to printers, barcode scanners, scales and serial-port devices.

  • Cross-platform

    Windows and macOS from one codebase with Electron or Tauri. For Windows-only programs that process a lot of data, we use .NET.

  • Legacy modernisation

    We move a program you have used for years, data included, to a new codebase that is easier to maintain.

  • Auto-update

    Signed installers and automatic updates. Nobody has to go round every computer to install a new version.

By the numbers

When desktop software is the right choice

  • OfflineKeeps working without a connectionLocal database + sync
  • HardwareDirect access to printers, scanners and devices on siteSerial, USB, network
  • SecurityData stays inside your company networkRole-based access

Toolbox

Technologies we use for desktop software

  • .NETFor data-heavy business programs that only need to run on Windows.
  • ElectronOne codebase for Windows and macOS, built with web technology.
  • TauriRust-based. It produces smaller installers than Electron.
  • SQLiteA local database embedded in the program. Data is kept here while the internet is down.
  • REST / gRPCData exchange with your central server, ERP and web services.

Roadmap

Desktop software project steps

We start by watching how your team works today, on site. We build the program in two-week sprints and test it with your printers, barcode scanners and other devices where they are actually used. Before everyone switches over, a small group runs it as a pilot.

  1. Step 1:

    Process analysis

    We observe your team’s current workflow on site and pin down the bottlenecks.

    1–2 weeks
  2. Step 2:

    Interface and prototype

    A design built around keyboard shortcuts and data-dense screens.

    ≈ 2 weeks
  3. Step 3:

    Build and hardware tests

    Tested in the real environment with printers, scanners and serial devices.

    Two-week sprints
  4. Step 4:

    Pilot

    A live trial with a small team, refined with their feedback.

    1–2 weeks
  5. Step 5:

    Rollout and training

    Signed installer, automatic updates and user training.

    At launch

See our process

Estimates up front

Desktop software:
timelines and budget.

  • Indicative range

    Single-purpose tool

    For example stock counts, label printing or quote preparation.

    Timeline
    6–10 weeks
    Budget
    Fixed quote after discovery
  • Indicative range

    Enterprise application

    Several modules, roles, reporting and server sync.

    Timeline
    3–6 months
    Budget
    Fixed quote after discovery
  • Indicative range

    Legacy modernisation

    Moving to a new codebase with data migration and a phased switch-over.

    Timeline
    Set after discovery
    Budget
    Fixed quote after discovery

These ranges are estimates based on industry benchmarks and our own projects, not a binding offer. Prices are in euros, excluding VAT. We give you the exact timeline and price in a written quote once the scope is clear.

Deliverables

What you get from a desktop software project

  • Process analysis and requirements document
  • Interface design and prototype
  • Windows / macOS application
  • Signed installer
  • User training and documentation
  • Maintenance and release management

FAQ

Questions about desktop software

Why desktop instead of a web app?

Desktop is the better fit if the program has to work without internet, connect to devices such as printers or barcode scanners, handle large data sets, or keep data inside your company network. If none of that applies, we usually recommend a web app.

Can you move our existing data across?

Yes. We test the import from Excel files, old databases or other programs on a copy first, check the results with you, and only then switch the live system over.

Can the same app run on both Windows and macOS?

Yes. With Electron or Tauri we build installers for both platforms from one codebase. For Windows-only, data-heavy enterprise scenarios we may choose .NET instead.

Next step

Let’s design the tool your team uses every day.

In a free first call we listen to what you need and work out the scope and a rough schedule with you.

Tell Us About Your Project See our process