Features model¶
On TapSDK2, the device does not use Text / Controller / Raw mode writes. Streams and behaviors are toggled with DeviceFeatures over framed GATT writes.
Why features instead of modes¶
TapSDK input modes are a single personality for the whole device (who receives HID vs app events). Developer firmware exposes independent streams: model detection (taps / air gestures), IMU motion, raw IMU, standby, and vision sensor settings. Your app enables only what it needs. The TapXR developer firmware has the full gesture set; TapBand uses the same BLE API.
Typical flow¶
await connect()→TapSDK2- Register callbacks
await sdk.start()(notifications + keepalive)set_feature(...)/ vision / IMU helpers as needed
Related¶
- Recipes: Use features
- API: TapSDK2
- Wire path: Connection model