---
title: "Native apps first, then Native Shell"
url: https://endomint.com/p/I3_rKfzGBMsB7xyL7fVS0g/native-apps-first-then-native-shell
published: 2026-11-21
updated: 2026-11-21
tags: ["avalonia", "linux", "macos", "nsh", "qt", "windows", "xerahs"]
---

# Native apps first, then Native Shell

The Avalonia work in KovaForge/XerahS is ramping down, in favour of the native apps in BriarForge/XerahS. Native Shell comes after those apps are finished.

BriarForge/XerahS is a separate tree. It does not carry the Avalonia UI. Each operating system gets its own application, checked against one product contract. Linux is Qt 6 and C++17, and it is the one underway. Windows is WinUI 3 and Win32. macOS is SwiftUI and AppKit. Android is Kotlin and Jetpack Compose, and iOS is Swift and SwiftUI. Neither phone app has been started, and nor have Windows or macOS.

The generated platform progress report marks 179 of 324 Linux desktop requirements implemented, and 0 of 324 on Windows and on macOS. A row counts only when it is marked implemented. Partial work counts as zero, and the report is not a forecast of how long the rest will take. The README still shows an older snapshot, 173 of 324, dated 12 November 2026.

| OS | Toolkit | Requirements marked implemented |
| :-: | :-: | :-: |
| Linux | Qt 6, C++17 | 179 of 324 |
| Windows | WinUI 3 and Win32 | 0 of 324 |
| macOS | SwiftUI and AppKit | 0 of 324 |

The native application replaces the Avalonia one after full-parity acceptance, with a settings migration. Finishing that is the job in front of me.

[Native Shell](https://nsh.dev/) (NSH) is the experiment after that. It is Longbridge's Rust UI framework: one description of the app, drawn with the operating system's own widgets. Release [v0.6.1](https://github.com/longbridge/nsh/releases) is dated 20 November 2026, and the project is still in heavy development. I will try it once the native apps are done, regardless of how far along it is, and grow with it from there. I will fork it. Where I find a limitation, I will write the patch and contribute it upstream.

The UI has to be a one-to-one match. NSH leaves colour, type and spacing to the app, so that match is work I am taking on.

~ Mike
