Trainiq Health Sync

3. Data Mapping

• Decoupling: Map androidx.health.connect.client.records.* directly to DomainModels.kt. Never let Health Connect record types leak into the UI or ViewModel.
• Unit Conversion: Standardize all units (e.g., metric) during mapping.

4. Metrics to Support

• Current: Steps, Calories, Heart Rate.
• Planned: Sleep (Duration and Stages), Exercise sessions, Body composition (Weight, Fat %).

Prohibited Patterns

• ❌ Do NOT read all data every time. Use TimeRangeFilter or ChangesToken.
• ❌ Do NOT store raw Health Connect records in Room; store mapped domain entities.
• ❌ Do NOT block the main thread for health sync operations.

Workflow

1. Check Availability: Verify SDK status.
2. Check Permissions: Verify user has granted access.
3. Fetch Data: Use readRecords or getChanges.
4. Map to Domain: Convert raw records to TrainIQ models.
5. Update Repository: Save to Room or update StateFlow.