BUI vs Qt
BUI and Qt both provide native desktop UI libraries, but they target different workflows and licensing models. Qt is a mature commercial toolkit with platform-native widgets and an established ecosystem; BUI provides Blender's specific interaction model and look as a small C library.
| Feature | BUI | Qt |
|---|
| License | GPL-3.0 | LGPL (open source) / Commercial (proprietary apps) |
| Widget style | Blender's look | Platform-native or custom |
| Language support | Python, Rust, JavaScript, C, C++, Dear ImGui | C++ (primary), Python (PyQt/PySide), others |
| Accessibility | Not yet | Supported |
| Pricing | Free (GPL-3.0) | Commercial license for proprietary apps |
BUI is the better choice when your users are Blender artists who already know drag-to-scrub number fields, pie menus, and Tab-to-search, and you want to give them those exact gestures. It also fits Python projects that want to drop Tk's dated look with minimal code changes, and Rust or JavaScript projects that need native windows without a browser or webview.
Qt is worth evaluating when your app needs to follow host OS design conventions (macOS HIG, Windows Fluent Design, GNOME HIG), when accessibility support is required from day one (BUI's README notes no accessibility support yet), or when you need Qt's commercial support contracts and certified toolchains for embedded or automotive targets. Teams shipping proprietary closed-source desktop apps that cannot release source under GPL-3.0 terms will find Qt's commercial license is the established path.