You don't have to build everything from scratch. The community has created robust wrappers and libraries to speed up your workflow:
: Newer versions of NativeUI allow for items to be hot-swapped and directly manipulated. This means you can change menu options dynamically based on what the user is doing in real-time, making the UI feel "alive." nativeui
In an era of Electron, Flutter, and Tauri, NativeUI remains the gold standard for user experience. It is the only approach where the OS feels like an ally, not a foreign layer to be fought. The cost — separate UI code — is steadily decreasing thanks to shared-logic frameworks. For any product that aspires to excellence on a given platform, NativeUI is not a relic; it is the benchmark. You don't have to build everything from scratch
: For developers using the C# version of NativeUI, avoid heavy calculations inside the Tick event. Optimization of core classes like UIResText and UIResRectangle is often the difference between a smooth menu and a stuttering one. It is the only approach where the OS
refers to a user interface built using the official, platform-provided frameworks, toolkits, and APIs of an operating system. It is the "default" way applications look and behave on a given platform.
| Approach | Examples | Native feel? | Performance | Code reuse | |----------|----------|--------------|-------------|-------------| | Fully native (separate codebases) | macOS AppKit + iOS UIKit | ✅ Perfect | ✅ Native | ❌ Low | | NativeUI with shared logic (MVVM + binding) | SwiftUI + Kotlin Multiplatform | ✅ Very high | ✅ Native | ✅ High (logic) | | Self-drawn cross-platform (canvas) | Flutter, Qt Quick, Avalonia | ⚠️ Mimics but not identical | ⚠️ Good, but extra layer | ✅ High | | Webview-based (HTML/CSS/JS) | Electron, Tauri (webview), Cordova | ❌ Feels foreign | ❌ Higher memory, less smooth | ✅ Very high |