Skip to content
kodenaKodena
Services/

04 · Desktop apps

For teams that live in one tool all day: editors, point of sale, control panels and offline first applications for Windows, macOS and Linux.

Book a call about desktop apps
An engineer working at her laptop

Problems we solve

01

Legacy software nobody can update

A careful rebuild that keeps the workflows your team relies on.

02

Unreliable internet at work

Offline first apps that sync safely when connected.

03

Hardware integration

Printers, scanners and card readers connected properly.

What you get

Deliverables, in writing.

An engineer working at her laptop

Process

  1. Step 01

    Discover

    Two to five workshops to agree on goals, users, constraints and what success looks like.

  2. Step 02

    Design

    Flows and interface designs you can click through before a line of production code.

  3. Step 03

    Build

    Signed builds for every platform at the end of each sprint.

  4. Step 04

    Ship

    Launch, monitoring, handover documentation and a support window agreed up front.

Typical stack

  • Tauri
  • Electron
  • Rust
  • TypeScript
  • SQLite

FAQ

Good questions.

Tauri for small, fast apps; Electron where a library needs it. We explain the trade off before we start.

Related work

A thirty minute call with a senior engineer. No sales script, just an honest view of how we would approach it.