Desktop GUI framework comparisons

Why choose Forge KUI

Build lean, extensible native desktop products with familiar HTML and CSS.

Web layout skills.
Native application control.

KUI combines standard layout, lightweight Lua, professional extensions and virtual components in one desktop environment. DevTools and MCP let developers and agents inspect the running result.

Run the complete example ↗
Native KUI desktop workspace

Six reasons to choose KUI

01

Modern web layout

Use familiar Flex, Grid, selectors, CSS variables, typography and animation. Canvas, SVG and DOM events have dedicated APIs, with individual support details in the reference.

↗
02

Lean runtime & Lua

KUI ships its own HTML/CSS renderer, without Chromium or a system WebView. Keep business logic in the native host, and use optional Lua for interface interactions.

↗
03

Built-in virtual components

VirtualList, ListView and TreeView are built in. Instantiate rows for the viewport and overscan, with APIs for selection, tree expansion and dynamic data changes.

↗
04

An extensible native core

Add an editor, PDF viewer or 3D through standalone extensions. Register your own elements through a pure C ABI, with styling, events and a defined drawing lifecycle.

↗
05

DevTools & automation

Inspect the DOM, computed styles and box model. Edit styles, debug Lua and record performance. Automation APIs and MCP connect a running app to your development tools.

↗
06

Built for agent-assisted development

You do not need to learn KUI’s features first. Describe layout, style and actions using HTML/CSS web standards. Your agent can consult the SDK docs, handle integration and inspect the UI and interactions through DevTools/MCP.

↗

Start with your current stack

Why KUI: compared with Electron

Familiar pages. A lean native delivery.

Why KUI: compared with Sciter

Standard layout and a complete development workflow.

Why KUI: compared with Tauri

A renderer that ships with your application.

Why KUI: compared with Wails

Connect Go business logic to a native UI.

Why KUI: compared with Qt

HTML/CSS as your desktop UI language.

Why KUI: compared with Flutter

Build desktop products with web layout skills.

Why KUI: compared with Avalonia

Author native desktop interfaces in HTML/CSS.

View runtime models and migration details

How the interface runs

The renderer and interface model shape integration choices. This table describes common desktop setups; add-on modules, plugins and embedding modes can use other paths. Scroll horizontally to see every column.

Eight desktop GUI options
FrameworkRenderingApplication and UIReuse and adaptation
Forge KUIOwn HTML/CSS pipeline, Skia renderingC++ / C / Go / Rust; optional LuaAdapt HTML/CSS to supported features; rewrite JavaScript logic
ElectronChromium + Node.jsHTML / CSS / JavaScriptReuse Web UI; integrate host features through Electron / Node.js
SciterOwn HTML/CSS engineHTML / CSS / JavaScript; native hostCheck Sciter CSS, DOM and scripting contracts
TauriOperating-system WebViewWeb frontend + Rust / pluginsReuse Web UI; check platform WebViews and bridging
WailsOperating-system WebViewWeb frontend + GoCall Go services through generated JavaScript bindings
QtQt Quick scene graph / Qt WidgetsC++ / QMLBuild UI in QML or Widgets; assess WebEngine separately for HTML
FlutterFlutter engine and widget treeDart; platform channels / FFIUse Flutter widgets; HTML/CSS pages do not run directly
AvaloniaOwn rendering; default Skia backend.NET / XAMLReuse .NET application logic; build UI with Avalonia controls

Where KUI fits

KUI hosts HTML/CSS interfaces in native applications through its own DOM, style, layout and painting pipeline, with optional Lua. Existing React, Vue or browser-JavaScript pages need adaptation. The initial website release documents Windows x64; Linux, macOS and HarmonyOS follow on the roadmap.

Compare the same task

Use the settings-panel project as a starting task: match fields, save validation, keyboard flow, window size and fonts. State whether package size includes runtimes. Measure idle and active memory, cold and warm startup, and frame-time distributions. Comparable benchmark results for these frameworks are not published here.

Official sources

Technical models were checked against official sources on 2026-11-09. Reuse and migration guidance is our engineering assessment; effort depends on the application. Each detail page covers the work involved in moving to KUI.