// the take
Bluejay wraps CoreBluetooth in a callback-based, FIFO-queued API for apps that talk to a single BLE peripheral on iOS. It's aimed at teams building companion apps for BLE hardware (fitness trackers, custom sensors) who want to avoid writing their own CoreBluetooth state machine.
The FIFO operation queue is the real selling point — CoreBluetooth's delegate-based API makes it easy to issue overlapping reads/writes and get undefined behavior, and Bluejay serializes everything for you. Background restoration (reconnecting and resuming listens after the OS kills your app) is implemented and documented in detail, which is one of the most fiddly parts of CoreBluetooth to get right. The Receivable/Sendable protocols give you a clean, testable boundary for packet (de)serialization instead of scattering byte-offset parsing through view controllers.
No commits since January 2024 — nearly two years stale, with no visible response to iOS/Swift version changes since; worth checking open issues for whether it still works on current iOS before adopting. The API is entirely callback-based with no async/await surface, which will feel dated if your codebase has otherwise moved to structured concurrency. It only supports one connected peripheral at a time by design, a hard limitation if your app needs to juggle multiple BLE devices simultaneously. The Carthage install path pulls in XCGLogger as a required dependency, which is extra baggage if you don't want a third-party logger in your app.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →