Qt Bluetooth alternative
SimpleBLE replaces the Bluetooth layer under your Qt application and leaves the rest of Qt in place. You get one BLE API on Windows, macOS, Linux, iOS, and Android, peripheral role included, from a team whose product is Bluetooth.
A Qt application can reach Bluetooth Low Energy three ways. This is how they differ for a commercial product.
| Library | Platforms | Peripheral role | Languages | Outside a Qt app | License |
|---|---|---|---|---|---|
| SimpleBLEC++ library | Windows, macOS, Linux, iOS, Android | Every platform, Windows included | C++, C, Python, C#, Java, Rust, and more | Services, command-line tools, and test scripts, with no event loop | Source-available (BUSL 1.1); one commercial license per company |
| Qt BluetoothQt framework module | Windows, macOS, Linux, iOS, Android | Android, iOS, Linux, macOS. Not Windows | C++ and QML; Python through PySide6 | Runs inside a Qt event loop | LGPLv3, GPLv2, or a Qt commercial license |
| Native OS APIsWinRT, CoreBluetooth, BlueZ, Android | Windows, macOS, Linux, iOS, Android, each with its own API | Yes, through each platform's own API | C++/WinRT, Swift or Objective-C, D-Bus, Kotlin or Java | Yes | Included with each operating system |
SimpleBLE is a C++ Bluetooth Low Energy library with one API on Windows, macOS, Linux, iOS, and Android. It sits under your Qt application: forward its callbacks as signals, and the rest of your code keeps working with QObjects. The same backend serves C, Python, C#, Java, Rust, and other languages, so your Qt product, test harnesses, and manufacturing tools share one Bluetooth foundation. The team that builds it supports commercial customers directly.
Qt Bluetooth is the Bluetooth module of the Qt framework. It supports the BLE central role on all five platforms and the peripheral role on Android, iOS, Linux, and macOS, but not on Windows. It is available under LGPLv3, GPLv2, or a Qt commercial license, and it runs inside the Qt event loop. Bluetooth is one module of many in Qt; in SimpleBLE, it is the whole product.
Each operating system has its own Bluetooth API: WinRT on Windows, CoreBluetooth on macOS and iOS, BlueZ over D-Bus on Linux, and the Android Bluetooth API. Writing against them directly costs nothing in licenses and takes one implementation per platform, each with its own threading, errors, and lifecycle. SimpleBLE is that work, done once and maintained for you.
SimpleBLE calls are plain C++. Forward its callbacks as signals, and your QObjects work with Bluetooth the way they work with everything else.
#include <iostream>
#include <simpleble/SimpleBLE.h>
auto adapter = SimpleBLE::Adapter::get_adapters().front();
adapter.set_callback_on_scan_found([](SimpleBLE::Peripheral peripheral) {
std::cout << peripheral.identifier() << " " << peripheral.address() << std::endl;
});
adapter.scan_for(5000);Replace only the Bluetooth layer. Your UI and architecture stay as they are.
Advertise and serve GATT on all five platforms with one API.
Product code, test harnesses, and factory tools share one backend, in C++, Python, C#, and more.
Runs in services, CLI tools, and test scripts without a Qt application.
Plug in a Dongl for a dedicated radio on Windows, macOS, or Linux. Same code.
The team behind every SimpleBLE backend works directly with commercial customers.
Start with one flow: scan, connect, discover services, and exchange data. Evaluation needs no license, and for commercial use one agreement covers your whole company, with no per-seat, per-device, or royalty fees.
No. SimpleBLE replaces Qt Bluetooth underneath the application. Your Qt UI, application architecture, and other Qt modules stay in place.
No. SimpleBLE replaces Qt Bluetooth underneath the application. Your Qt UI, application architecture, and other Qt modules stay in place.
No. Qt's documentation lists the Bluetooth LE peripheral role on Android, iOS, Linux, and macOS, not on Windows. SimpleBLE hosts a peripheral on all five platforms, Windows included.
No. Qt's documentation lists the Bluetooth LE peripheral role on Android, iOS, Linux, and macOS, not on Windows. SimpleBLE hosts a peripheral on all five platforms, Windows included.
Wrap the peripheral in a QObject and forward SimpleBLE callbacks as signals with QMetaObject::invokeMethod. The rest of the application keeps its existing signals and slots.
Wrap the peripheral in a QObject and forward SimpleBLE callbacks as signals with QMetaObject::invokeMethod. The rest of the application keeps its existing signals and slots.
Yes. The same SimpleBLE backend is available from C++, C, Python, C#, Java, Rust, and other languages, so validation, manufacturing, and support tools share one foundation with the product.
Yes. The same SimpleBLE backend is available from C++, C, Python, C#, Java, Rust, and other languages, so validation, manufacturing, and support tools share one foundation with the product.
Replace one representative flow first: scanning, connecting, discovering services, and exchanging data. Evaluation needs no license or sales call.
Replace one representative flow first: scanning, connecting, discovering services, and exchanging data. Evaluation needs no license or sales call.
SimpleBLE is source-available under the Business Source License 1.1 and free for non-commercial use. Commercial use needs a license, and one agreement covers your whole legal entity, with no per-seat, per-device, or royalty fees.
SimpleBLE is source-available under the Business Source License 1.1 and free for non-commercial use. Commercial use needs a license, and one agreement covers your whole legal entity, with no per-seat, per-device, or royalty fees.