Google Health API integration — Fitbit Air as a primary data source #2872

Summary

I'd like to request support for Google Health API as an alternative primary data source in NOOP, initially targeting the Google Fitbit Air, with potential compatibility for other Fitbit devices and Pixel Watches.

The goal is to use my existing wearable to power NOOP's recovery, strain, sleep, and health analytics without requiring a WHOOP strap.

Current situation

I'm using NOOP on iOS, installed through SideStore, alongside a Google Fitbit Air.

I have successfully imported my Apple Health history into NOOP, and the data is visible in the dedicated Apple Health section.

However, I haven't been able to use this history to populate the main NOOP analytics (Charge, Effort, Rest).

Additionally, not all Fitbit Air metrics, particularly HRV, are exported from Google Health to Apple Health.

Proposed functionality

1. Google Health API integration

Allow users to connect their Google Health account through OAuth 2.0, with read-only permissions.

Import relevant metrics, including:

Heart rate and resting heart rate

HRV (including overnight/daily measurements)

Sleep duration and stages

Respiratory rate

SpO₂

Skin temperature variations

Physical activities and workouts

2. Alternative analytics data source

Allow users to select Google Health as their primary physiological data source, instead of requiring a WHOOP device.

Imported measurements should feed NOOP's existing analytics wherever sufficient data is available:

Charge (recovery)

Effort (strain)

Rest (sleep)

HRV baseline and trends

The integration should preserve metric definitions and units, particularly when distinguishing RMSSD from SDNN HRV measurements.

3. Automatic synchronization

Support periodic or on-demand synchronization of newly available Google Health measurements, without repeatedly exporting and importing files.

4. Optional Bluetooth live HR

The Fitbit Air supports standard Bluetooth Heart Rate Profile broadcasting. This could provide an optional live heart rate feed for NOOP, while historical and overnight data would come from the Google Health API.

Privacy considerations

I understand that NOOP is designed around offline operation and data ownership.

The Google Health connection should therefore be strictly opt-in, use minimal read-only permissions, and continue storing and analyzing the retrieved data locally.

Users who prefer the existing fully offline WHOOP workflow should not be affected.

Why this matters

This would extend NOOP's usefulness to people who already own compatible wearables but want its transparent recovery and training analytics.

It could also establish a reusable integration for several Google Health-supported devices, rather than requiring a separate Bluetooth implementation for each manufacturer.

References

Google Health API: https://developers.google.com/health

Supported devices and data types: https://developers.google.com/health/data-types/device-compatibility

Google Health OAuth setup: https://developers.google.com/health/setup

Fitbit Air real-time HR sharing: https://support.google.com/googlehealth/answer/14236705

Would this fit NOOP's roadmap? If a full integration is too large, an initial read-only Google Health importer with manual synchronization could be a useful first step.

Thanks for developing NOOP and making personal health analytics more accessible!