Target all platforms.

Slint compiles the same .slint UI natively to desktop (Windows, macOS, Linux), mobile (Android and iOS), embedded devices and microcontrollers, and the web via WebAssembly.

Slint's runtime fits in under 300 KiB of RAM and runs on microcontrollers and embedded Linux, on bare metal or an RTOS, with or without a GPU.

No. You pick the renderer when you build: GPU-accelerated where the device has a GPU, or a software renderer (full framebuffer or line-by-line) where it doesn't.

Slint compiles to WebAssembly and renders to a canvas, so the same .slint UI used on desktop and embedded runs in any modern browser with zero install.

Yes. Slint compiles to native code and does not bundle a browser engine, so applications start faster and use far less memory and disk than a typical Electron app.

Rust, C++, JavaScript/TypeScript and Python on desktop and embedded Linux. Microcontrollers support Rust and C++; iOS and Android are Rust only. The .slint UI is the same whichever you use.

Slint's runtime fits in under 300 KiB of RAM. On a microcontroller it can render line-by-line from a small line buffer instead of a full-screen framebuffer, usually the largest RAM consumer, so a smaller, cheaper part is often enough. It has run on an RP2040 with 264 KB of RAM.

No. Slint's software renderer can draw line-by-line into a small line buffer, so a full-screen framebuffer is optional: the single biggest RAM saving on a memory-constrained device. When a GPU or a full framebuffer is available, Slint uses it.

Yes. Slint is independent of the operating system: it runs on bare metal with your own event loop, or on an RTOS such as FreeRTOS, Zephyr or QNX, as well as on embedded Linux.