How Desktop Works

Calimero Desktop is the end-user application. This page explains the architecture behind it and how it fits into the wider Calimero stack.

High-level architecture

Calimero Desktop is built as a Tauri application with a web frontend and native integrations for node lifecycle management.

flowchart LR
    UI[Desktop UI] --> TAURI[Tauri shell]
    TAURI --> NODE[Local merod process]
    UI --> AUTH[Hash-based SSO and identity flows]
    UI --> REG[App discovery and install flows]
    REG --> REGISTRY[App Registry]
    NODE --> CTX[Contexts and applications]
    TAURI --> UPDATE[Auto-update and release channel]

    classDef lime fill:#14210a,stroke:#a5ff11,color:#f5ffe0,stroke-width:2px;
    classDef cyan fill:#0b2526,stroke:#39d0c8,color:#dcfffd,stroke-width:2px;
    classDef purple fill:#221133,stroke:#c084fc,color:#f7ecff,stroke-width:2px;
    classDef orange fill:#2c1805,stroke:#ffb54d,color:#fff2d6,stroke-width:2px;

    class UI,AUTH lime;
    class TAURI,NODE cyan;
    class REG,REGISTRY purple;
    class CTX,UPDATE orange;

Main responsibilities

1. Local node management

Desktop provides a user-facing control plane for the local node.

That includes:

starting and stopping the bundled or installed merod,
wiring user actions to node APIs,
exposing a simpler install and launch experience than raw CLI usage,
surfacing context and application state without forcing users into terminal workflows.

The existing desktop docs mention SSO for developers. In practice, the app coordinates browser-based auth with a return-to-desktop flow using a hash/redirect exchange.

This is useful when:

a user signs into a Calimero-hosted experience,
a builder wants a smooth “open in desktop” experience,
the desktop app needs to recover the auth result after the browser hands control back.

3. App installation UX

Desktop is one of the main consumers of the App Registry.

Typical flow:

browse or receive an app reference,
resolve the bundle,
verify the artifact/signature path,
install the app into a local node,
create or join a context,
launch the application UI and methods from the desktop shell.

Monorepo pieces

The tauri-app repository includes more than just the desktop binary:

Part	Role
`apps/desktop`	Main desktop application
`apps/download-site`	Distribution/download website
`packages/*`	Shared React/JS packages used by the app and related tooling

This separation matters because the desktop user experience, update pipeline, and reusable UI packages evolve together.

Development workflow

The Tauri app monorepo supports a normal web-like dev loop plus native packaging:

pnpm install
pnpm --filter desktop dev

Important prerequisites from the source repo:

Node.js
pnpm
Rust toolchain
platform-specific Tauri dependencies

There is also explicit support for opening DevTools during development with the shortcut:

Cmd/Ctrl + Shift + I

Update and release model

The Tauri monorepo also documents auto-updates and release handling. That makes Desktop more than a wrapper around a node binary. It is a maintained delivery surface with:

packaged builds,
update channels,
release automation,
a companion download site.

When to use Desktop vs CLI

Use Desktop when	Use CLI when
You want a graphical install and launch flow	You need scripts, CI, or automation
You are onboarding new users or testers	You are managing nodes headlessly
You need SSO/browser-assisted desktop UX	You want reproducible terminal operations
You want app browsing and installability in one place	You are debugging low-level runtime issues

Desktop and CLI are complementary, not competing surfaces.

How it fits with the rest of Calimero

Desktop gives users a local-first control surface.
merod provides the node runtime.
The App Registry provides signed app discovery and distribution.
Cloud/MDMA provides hosted operator and managed-node workflows.