device-integrationlisted

# Device Integration ## Purpose Design the integration strategy for device hardware APIs (camera, sensors, biometrics, Bluetooth, etc.), including permission flows, fallback behavior, and cross-platform abstraction. ## Scope Constraints Reads hardware API documentation, framework references, and permission configurations for integration analysis. Does not modify files or execute code. Does not access device hardware, sensors, or biometric data directly. ## Inputs - Feature requirements involving hardware capabilities - Target platforms and OS version minimums - Cross-platform framework (if applicable) - Privacy requirements and data sensitivity ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Inventory required capabilities - [ ] Step 2: Map permission requirements - [ ] Step 3: Design permission flow - [ ] Step 4: Evaluate cross-platform abstraction - [ ] Step 5: Design fallback behavior - [ ] Step 6: Power and performance impact ### Step 1: Inventory Required Capabilities List every hardware API the feature needs: - Camera (photo, video, barcode scanning) - Location (GPS, network-based, background location) - Biometrics (Face ID, Touch ID, fingerprint, device PIN fallback) - Bluetooth (BLE scanning, pairing, data transfer) - Sensors (accelerometer, gyroscope, compass, barometer) - Push notifications (remote, local, rich notific