Field note 17 · Android connections
Google Fit, Google Health and Health Connect: What Actually Changes Before 2027
Find the route behind your connection before changing it. Separate an app, an API and an on-device bridge, then keep a small record of what actually arrives.
First identify the connection that might change
A notice about Google Fit can sound as though every connected watch, app and old record has the same deadline. They do not share one route. Before changing anything, identify the source that recorded your observation, the connection carrying it and the app that reads it. A familiar logo is less useful than those three names.
Google’s current migration guide, checked 3 November 2026, says Google Fit APIs, including the REST API, are supported until the end of 2026. It directs cloud-based integrations toward the Google Health API and mobile-first uses toward Health Connect. Its table also says an existing Health Connect integration can remain.
Four names that describe different things
Google Fit APIs
These are legacy developer interfaces. Google’s guidance distinguishes cloud history and session integrations from mobile step tracking and watch-side recording. Knowing that a screen says “Google Fit” is not enough to identify which interface sits behind it.
Google Health app
This is the consumer app formerly named Fitbit. Google announced a rollout beginning 19 May 2026. It is an app you can open, not another name for every health-data connection. Its Health Connect settings control supported sharing with other apps.
Google Health API
This is a developer service built as the next generation of the Fitbit Web API. Its official overview describes an OAuth-based interface for health and fitness data. A provider must actually implement a connection; an app acquiring a new name does not prove that another service has migrated.
Health Connect
This is an Android data-sharing platform on the phone. Apps read and write supported categories with permissions. The platform architecture explains those separate app permissions. The source must supply the category and the reader must support it; either side can leave a gap.
There can also be a separate account connection, such as Nutrinaut’s source-reviewed Garmin route. Keep that route distinct from Health Connect. Watch-side Health Services on Wear OS provides a recording interface to device sensors. It should not be confused with an authorization screen on the phone.
Build a small route passport
Choose the connection you can confirm from settings or provider documentation. If you only recognize a brand, choose “I am not sure.” The diagram explains the selected route and what to check next; it does not connect to your account or detect which apps you installed.
Connection passport
Documentation checked 3 November 2026
This worksheet runs in your browser. It requests no health records, sends no selections to a server and does not save your choices.
Route not established
Identify the bridge before choosing a replacement
- SourceYour device or source appFind one dated observation where it was first recorded.
- ConnectionConnection not confirmedCheck the name in settings or ask the provider.
- ReaderYour destination appCheck what arrived, including category, date and source.
There is not enough information to apply the Google Fit API deadline to this route.
Checks to make next
- Find one known observation and record its category, time, unit and source.
- Find the exact connection name in the app’s settings or help.
- Ask the provider which route supplies that feature before changing permissions or disconnecting.
A brand name or a “connected” badge does not confirm a data route. Keep the original record while you investigate.
Automatic copy is unavailable. Select and copy this text:
Several routes can coexist. Work through one observation at a time, then repeat for another category. A sleep record arriving through one path does not prove that HRV or a complete workout history travels through it too.
Keep a before-and-after record that can answer a question
Before a provider changes its connection, choose one ordinary recent day and one older day you care about. Use a private note or a provider’s available export. You do not need to upload that information to this website.
| Keep | Why it helps |
|---|---|
| Source and connection | Separates the recording app from the bridge and the destination. |
| Time and timezone | Prevents a moved calendar label from becoming an invented second event. |
| Category, unit and definition | Keeps time asleep separate from time in bed, and a daily total separate from a session. |
| Value and last sync | Makes a changed value or a stale copy easier to locate. |
| Unknown fields | Preserves the difference between missing information and a measured zero. |
Repeat the same check after a change. Start with definitions and timestamps when totals disagree. For file-format or interval questions, the browser-local Forensics Lab can help inspect an export. It cannot confirm the private permissions of a live account.
A worked decision: last night arrived, last month did not
Illustrative situation, not a customer record or Nutrinaut test. Alex can see last night’s sleep in a destination app, but an older night is absent after reconnecting. Alex initially thinks a migration deleted the older record.
The useful next step is to locate that older night in the original source. If it is still there, the missing destination copy does not establish deletion at the source. Alex records the connection name, last sync and the earliest date visible in the destination, then checks whether that route supports the requested history.
For Health Connect, Google documents history-reading restrictions and additional history permission. The Google Health app’s setup also distinguishes historical and background access. Those are separate questions from whether the current night synchronized. Neither permission should be assumed from a general “connected” label.
If Alex cannot establish the route, the right result is a precise support question, not another connection added at random. Keep the source record and avoid erasing or disconnecting a working route merely to make the displays match.
What this means when considering Nutrinaut
Nutrinaut’s reviewed Android implementation associated with build 99 contains Health Connect readers and a separate Garmin connection path. The connections guide explains the supported input categories and source checks. These implementation findings are not a test of the currently installed store build, a certification of every wearable or proof that a particular history transfer succeeds.
Use the same passport when considering any app. A useful choice begins with the observations your setup can supply and the job you need completed. Our Android app comparison separates those decisions from proprietary score names and hardware purchases.
Ask a support question that can be answered
Share only the details needed through the provider’s appropriate support channel. You can describe the category and date without sending an entire health diary. A clear route, one known observation and one specific gap give a provider something more actionable than “my wearable stopped syncing.”
Sources and checking scope
Official documentation checked 3 November 2026. The connection passport is our explanatory decision aid, not a live account diagnostic. The worked situation is illustrative.
- Android Developers: Google Fit migration paths and API support period.
- Android Developers: Health Connect architecture and permissions.
- Google Health API: developer overview.
- Google Health Help: Health Connect sharing, historical access and sync checks.
- Android Developers: reading data and history restrictions.
- Android Developers: Health Services on Wear OS.
- Google: Fitbit app transition to Google Health.
- Nutrinaut: source-reviewed connection documentation and its limits.
How this guide was prepared
Official platform documentation was checked on 3 November 2026. The route planner classifies the answers you select; it does not establish which connection a particular installed app uses. Nutrinaut implementation references describe inspected Android source associated with build 99, rather than a new test of the current published Android app or its backend. No private user records or user-count statistics are used.
Analysis and drafting were AI-assisted. Eugene Blago is responsible for this guide. To report a factual correction, send the page URL and source to [email protected]. See our editorial and corrections policy.