Start a conversation

Desktop & cross-platform

Windows, macOS and Linux applications — including the signing, updating and installer work that breaks at the last minute.

  • Electron
  • Tauri
  • Qt
  • C++
  • Rust
  • .NET
  • C#
  • Squirrel / Sparkle

Desktop software is having a second life: local-first tools, professional applications that cannot live in a tab, and anything that has to touch hardware or the filesystem. The engineering is fine; the distribution is where projects stall.

We build in Electron and Tauri when the product is essentially a rich application with web technology underneath, and in Qt, C++ or .NET when it needs native performance, real-time behaviour or platform APIs that a webview cannot reach. Tauri is worth a serious look when binary size and memory matter to your users.

Then there is everything after the build: Apple code signing and notarisation, Windows signing, an auto-update channel that can be paused when a release goes wrong, installers and clean uninstalls, and offline licensing if the product is paid. This is the part most teams discover two weeks before launch, and it is the part we plan first.

What you get

  • Signed and notarised builds for macOS, Windows and Linux
  • Auto-update channel with staged rollout and the ability to stop one
  • Installers, uninstallers and first-run experience
  • Filesystem, hardware or peripheral integration where the product needs it

Common questions

Electron, Tauri or native — how do you decide?
By what the application actually does. Heavy real-time processing, low-latency audio or graphics, or deep OS integration argue for native. A rich but conventional application with a small team argues for Electron or Tauri, and between those two Tauri wins when installer size and memory footprint matter to your users.
Do you handle code signing and Apple notarisation?
Yes, including getting the certificates into CI so releases do not depend on one person’s machine. If you do not have an Apple Developer or code-signing certificate yet, we will tell you early, because the lead time on those has sunk more launch dates than any bug.
Can you work on performance-critical desktop software?
Yes — profiling, threading, memory and render-loop work are ordinary tasks for us, in C++, Rust or .NET. Bring the profile trace to the first call if you have one.

Next step

Tell us what has to ship, and by when.

One call, no deck. If we are not the right team for it we will say so, and usually point you at who is.

Start a conversation branislav@thrivee.io

Typical reply within one business day · CET / CEST (UTC+1 / UTC+2)