A shared interface, with user permission
Google introduced Health Connect on May 11, 2022 as a platform and API being built with Samsung. The proposal gave Android developers a common way to read and write health and fitness information with user permission, rather than arrange a separate connection for every pair of apps.
Google described standardized data covering activity, sleep, nutrition, body measurements and vital signs. It said Health Connect's store was encrypted and kept on the device. Users would be able to review permissions, stop access, delete unwanted data and prioritize one source over another.
Those were the platform's stated controls, not an independent assessment of every participating app. An application's ability to exchange a heart-rate record does not establish that the measurement is medically accurate or that sharing it improves a health outcome.
The later beta brought specific integrations
On November 14, 2022, Google separately announced the Health Connect beta app in Google Play and said more than ten health, fitness and wellness apps were rolling out integrations. Its examples included MyFitnessPal, Oura and Peloton.
Google described Peloton members choosing to share workout statistics with other participating services. That was a specific example of the intended exchange, not a statement that every app already supported every record type. The beta announcement also described a common schema with more than 40 data types across six categories and a central permissions interface.
Integration and interpretation are different jobs
The sequence matters: May supplied developer access and the collaboration's basic design, while November identified a beta and an initial integration wave. A shared schema can help applications exchange consistently structured records without resolving how each application interprets them. Neither announcement by itself establishes current availability, clinical effectiveness or the behavior of all software that later joined the ecosystem.