FORGE KUI / compare

Why KUI: compared with Wails

Connect Go business logic to a native UI.

Version 3.61.7

Connect Go business logic to a native UI.

KUI brings HTML/CSS interfaces, native application logic and built-in capabilities together for teams that want control over their desktop runtime, components and delivery.

  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
Actual KUI workspace

Go and a Web interface

Wails uses native WebViews for Web interfaces and generates bindings for JavaScript to call Go services. This page uses Wails v3 documentation; v2 projects also need the separate v2 documentation.

Which Go code can remain

Business packages independent of the Wails runtime can be evaluated for reuse. Reconnect windows, dialogs, events and frontend bindings through the KUI Go SDK. Check goroutine callback context and UI-thread requirements before updating the DOM.

Start with one call chain

Trigger a Go task from a button, return a result and update text, then test failure, cancellation and window closure. Check object lifetime, DLL paths and string encoding. Explicitly map frontend Promise failures to KUI host callback handling.

Sources and practice

Technical models were checked against official documentation on 2026-11-09. Migration sections are our engineering guidance, without cross-framework benchmark results. Check KUI interfaces, limitations and examples for specific capabilities.