Core Concepts

Use this section to understand the SDK model before working with individual device or AI features.

Essential Concepts

Discover, then create a device: Scanning returns a discovered-device handle. Convert it to a storable device before saving or connecting it.
Wait until the device is ready: A Bluetooth link is not the final ready state. Issue feature commands after the SDK completes its device handshake.
Check capability protocols: A connected device exposes only the feature protocols supported by its model and firmware. Cast to the required protocol before calling a feature.
Separate global and device events: SDKDelegate reports SDK-wide events; DeviceDelegate reports events associated with one device.
Install only the modules you use: Core functionality, device communication, AI providers, logging, media, and diagnostics are delivered as separate CocoaPods subspecs or through All-in-One.
Treat plugins as integration boundaries: Provider and bridge plugins connect optional service-provider implementations to the core SDK without making every integration mandatory.

Use SDK Glossary for concise definitions of Bluetooth, device, audio, AI, media, OTA, and architecture terms.
Use Architecture for module relationships, plugin boundaries, and the device lifecycle.
Use Core Features when you are ready to implement device capabilities.