dat-conventions

Use async/await for all Wearables SDK calls and wrap them in do/catch blocks to handle typed errors, preventing asynchronous misuse during device discovery or camera streaming on iOS.

You need @MainActor for iOS wearable device UI updates whenever rendering display output or handling frame data, ensuring safe and predictable main thread execution during async streaming and photo capture operations.

The best way to name Swift sessions and selectors for Wearables device discovery is to apply standardized type and symbol naming conventions, ensuring readable and consistent code structure across registration and configuration processes.

Yes, you can use MockDeviceKit for testing iOS async camera streaming by importing the Mock module to simulate device discovery, registration, and photo capture scenarios without requiring physical hardware.

Yes, the iOS Wearables SDK requires module-scoped imports for camera and display capabilities, meaning you must import the specific Core, Camera, or Display frameworks to match the exact capability you are using.

Your iOS Swift async code blocks the main thread during DAT frame handling if you are not using async/await-first patterns, which are required to avoid blocking the main thread during streaming or session updates.