[Intermediate → Advanced] · Write it once per OS, using that OS’s own SDK. Best result, most work.

The stacks

PlatformUILanguage
macOSSwiftUI (modern) / AppKit (mature)Swift
WindowsWinUI 3 / WPFC#
LinuxGTK4 / libadwaita, or QtC, Rust, Python, C++

When this is right

When the app is the platform experience. Professional creative tools, system utilities, anything where users are expert and notice everything. Apple’s own apps, Windows system tools.

When you need APIs nobody wraps — deep OS integration, a specific hardware framework, kernel-adjacent behaviour, a new platform feature on day one.

When performance or size is genuinely critical. A native app can be a few MB with near-zero idle memory.

When you only ship to one platform. If your users are all on macOS, “cross-platform” is a cost with no benefit — and SwiftUI is a genuinely pleasant way to build.

The things to know

The cost is linear in platforms and it is not amortised. Three platforms is three UIs, three build pipelines, three sets of bugs, three areas of expertise. The usual compromise is a shared core — business logic in Rust, C++ or Kotlin Multiplatform — with a native UI per platform. That’s the architecture behind several well-regarded cross-platform apps, and it’s a straightforward application of interface design: put the boundary where the platforms genuinely differ, which is the UI, and share everything below it.

SwiftUI and WinUI have converged on the same model — declarative UI as a function of state, with the framework diffing. The same idea as React → React. Learning one makes the others much faster.

Accessibility, localisation and platform conventions come free, which is the quiet argument for native and the thing cross-platform toolkits spend the most effort approximating.

Source: [reference] — scaffold, from Apple, Microsoft and GNOME documentation.

↑ Back to desktop/frameworks/ — Ways of Building a Desktop App