Developer preview
Capability areas
A high-level guide to the types of Armor integration developers can plan for.
Model-aware applications
Armor is a family of device variants. The feature set available to an app can depend on the selected model and its supported software.
Use capability information published with the SDK release. Do not infer support from a product name or assume every device has the same hardware.
Planned capability areas
| Area | Examples | Availability |
|---|---|---|
| Connection and device state | Discovery, connection, battery and device status. | See release documentation. |
| Audio experiences | Audio routing, voice interactions and sound settings. | See release documentation. |
| Camera and media | Capture, file listing, transfer and recovery. | Model support and availability to be confirmed. |
| Device settings and light | Supported controls and product-specific settings. | See release documentation. |
| Updates and diagnostics | Firmware update status and diagnostic information. | See release documentation. |
Build capability-aware interfaces
Present a feature only when the selected device and SDK release report that it is supported. Distinguish unavailable, unknown and ready states in the app UI.
Final model compatibility and feature availability will be published with each SDK release.