Software · Desktop and consumer
Desktop apps
Installable apps for Windows, macOS and Linux that work offline and talk to local files and hardware.
Some work belongs on the desktop: large files, local hardware, offline use or heavy processing. We build desktop apps with Tauri, Electron, Qt or native toolkits depending on size, speed and platform needs, and ship them with signed installers and safe automatic updates.
What we build
- Cross-platform apps for Windows, macOS and Linux from one codebase
- Native Windows apps with WinUI 3 or .NET, and macOS apps with SwiftUI
- Offline-first data storage with SQLite and background sync to a server
- Integration with printers, scanners, USB and serial devices on the local machine
- Signed installers, MSIX and DMG packages, and silent automatic updates
- Modern rebuilds of old VB6, WinForms or Delphi applications
DemoInteractive · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
use std::fs;
#[tauri::command]
fn word_count(path: String) -> Result<usize, String> {
let text = fs::read_to_string(&path)
.map_err(|e| e.to_string())?;
Ok(text.split_whitespace().count())
}
What it does well
Small and fast
Tauri apps use the system web view and a Rust core, keeping downloads small and startup quick.
Offline first
Work continues without a connection, and changes sync safely when the network returns.
Local hardware
Apps talk to printers, scanners, cameras and serial devices that a browser cannot reach.
Signed releases
Builds are code-signed, and notarised on macOS, so the operating system trusts them.
Automatic updates
Updates download in the background and apply on restart, with staged rollouts.
Managed deployment
MSI and MSIX packages install silently through Intune or other device management.
Questions
Tauri, Electron or Qt: which should we choose?
Tauri suits apps that should be small and light with a web interface. Electron is mature, with a large ecosystem and identical rendering everywhere. Qt fits performance-heavy or hardware-close apps in C++. We recommend one after looking at your features, team skills and target machines.
Can you modernise our old desktop application?
Yes. We study the existing app and its data, then rebuild it screen by screen, often keeping the same database at first. Users get a familiar workflow on a current toolkit, and the old app is retired only when every screen has a replacement.
How are updates delivered to users?
Each release is signed and published to an update server. The app checks for updates, downloads them in the background and applies them on restart. For managed company machines, we also provide packages your IT team can deploy centrally.