Skip to content
AF

Every question the Architecture pages answer

The 15 architecture pages answer 75 named questions between them. Every one is listed below, and every link lands on the paragraph that answers it rather than the top of the page.

Incremental Sync: Reading Only What Changed Since Last Time

Backfilling Years of Wearable Data Without Hitting Rate Limits

Background Sync That Does Not Depend on the Phone Waking Up

Webhook ingestion for health data: making at-least-once delivery safe

Mapping Users to Wearable Provider Accounts and Devices

Deduplicating Health Data From Multiple Sources

Normalizing wearable data across providers

Timezones and Day Boundaries: Whose Midnight Defines the Day?

Missing Data and Gaps in Health Metrics

How Should You Store Health Time-Series Data?

Resolving Sync Conflicts in an Offline-First Workout Log

Versioning Derived Metrics and Recomputing Health History

Monitoring a Health Data Pipeline for Silent Failures

Deleting and Exporting a User's Health Data

Caching Fitness API Responses Without Serving Stale Health Data

Back to the Architecture hub, or see every question this site answers.