A renderer that ships with your application.
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.
WebView and a Rust host
Tauri displays HTML in operating-system WebViews and connects the frontend to Rust through message passing, with plugin interfaces. Existing Web interfaces need verification against the target platform's WebView.
Migrate UI and commands
Retain UI-independent Rust logic and reconnect it through the KUI Rust SDK. Map frontend invoke calls, event subscriptions, state synchronization and plugins to host callbacks. Adapt Web components and JavaScript dependencies to KUI's HTML/CSS and Lua scope.
Verify deployment
Build a minimal consumer in a clean Windows x64 directory and check Rust bindings, the C ABI runtime, resources and extension dependencies. Tauri plugin permissions and configuration do not become KUI access controls automatically; design those boundaries in the application.
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.
Something unclear?
Report an issue on this page →