All guides and articles

Health apps to use with your wearable: choose a useful connection

Edited edition: . Manuscript received . The original first-publication date is unknown.

Illustration of hands reviewing an open journal beside a phone with abstract symbols.

Image description: Illustration of hands reviewing an open journal beside a phone with abstract symbols.

AI-generated illustration of reviewing personal records and app permissions. It does not depict a real app, patient or tested device. Illustration generated with OpenAI for Wearables & Beyond.

Provider documentation reviewed October 19, 2026. Check the linked compatibility instructions again before subscribing or connecting a device.

You've unboxed a wearable, connected its companion app and started looking at the numbers. An Oura Ring, Apple Watch or Fitbit can produce a lot to sort through. Before adding another app, decide what you want to do with the information: compare workouts, keep a food diary, organize readings for an appointment or record symptoms alongside your own notes.

A useful connection has a specific job. Check which records it receives, where they came from and what happens after you grant access. Installing another dashboard does not mean it can read everything your device collects.

Find a starting point

These are starting points for the task, with connection and medical-use limits explained in each section.

What belongs in your health stack?

A “health stack” is the collection of tools you use together. It might include a wearable, its companion app, a shared health-data hub and a third-party service. You can keep that collection small. The companion app may already do the job you need.

Think through one example before connecting accounts. If you want to see sleep beside a symptom diary, find out whether sleep records can reach that diary. If you want a workout on a training calendar, check the activity connection. A service that imports workouts may not import sleep or all-day heart rate.

The wearable sensors guide explains how a recorded signal differs from the interpretation an app builds from it. Keep that distinction when comparing apps, too.

Apple Health, Google Fit and the changing Android connections

Apple Health brings together supported records from apps and devices. A paired Apple Watch can contribute activity and heart-rate information. You control compatible apps' access by category and can inspect the sources behind a data type. The app supplying the records may have a sharing setting of its own.

On Android, distinguish Health Connect from the Google Health app. Health Connect manages participating apps' read and write access to particular health categories. Revoking access does not automatically delete copies already stored. Google's availability guide lists Android 9 or later with Google Play services, while individual apps may need newer software.

Google Fit needs a current compatibility check. Google's Fit migration guide says its Fit APIs are supported through the end of 2026. That developer timetable is separate from an individual app's migration. Google also renamed the Fitbit app Google Health in 2026. Health Connect, that consumer app and a cloud API are different parts of the connection.

A hub can collect steps, sleep or other authorized records, but the actual categories depend on the source. Check the direction of sharing for each category. Do not assume that linking two familiar brands produces a complete two-way copy of your health information.

MyFitnessPal: check which records synchronize

MyFitnessPal can put a food diary alongside supported activity records for reviewing your weight-management goals. Its Apple Health instructions describe different directions: food information goes from MyFitnessPal to Health, exercise and sleep come from Health, and weight can move both ways. Its Health Connect connection has its own rules for steps, sleep, food and exercise.

Look for duplicate workouts when several services feed the same diary. Also check the provider's current integration issues if records stop arriving. A successful account connection does not guarantee that every record has synchronized.

Wearable calorie figures are estimates. A 2017 laboratory study of seven older devices found substantial energy-expenditure error; it does not rank today's models. Avoid treating a calorie adjustment as your precisely measured food requirement.

Strava: review a workout and choose its audience

Strava organizes supported activities and provides social features for people who want them. Its Garmin connection guide explains automatic activity transfer after permission is granted. Its Apple Watch guide describes the watch app and permissions for fields such as heart rate. Neither connection means that every all-day health metric transfers.

Before sharing a route, read Strava's privacy controls. Hiding a map from other Strava users does not necessarily hide the same information from an authorized third-party service. Check the receiving service's settings as well.

Compare similar workouts when you can, accounting for different routes and conditions. Clubs and challenges can be enjoyable without setting the right exercise plan for every participant. The wearable gamification guide looks at the distinction between an engaging feature and evidence that it changes behavior.

Calm and Headspace: content, session records and reminders

Calm and Headspace provide ways to start a meditation or breathing exercise. Their wearable features are different, so check the current app instead of assuming both respond to the same data.

Calm's Apple Watch app includes selected content and breathing exercises. Its Wear OS guide describes a limited selection for Premium members and warns that the app is temporarily unavailable on some devices. Calm's Health Connect integration can write completed guided sessions as mindfulness data with permission. That is a session record, not a measurement of how relaxed you became.

Headspace's current Apple Watch experience includes audio and haptic breathing. It also describes optional reminders informed by permitted HealthKit signals, including HRV, sleep and workouts. Revoking HealthKit permission pauses those reminders. Check its current watch and paired-phone requirements before relying on this feature.

A physiological prompt does not diagnose an anxiety disorder or explain why you feel distressed. NIMH's self-care guidance discusses self-care alongside professional help. You can raise concerns with a clinician regardless of what an app reports.

Heart and blood-pressure records: three different app approaches

The CDC's hypertension page reports high blood pressure in about 48% of U.S. adults. A separate report using 2024 National Health Interview Survey data found that 11.3% of adults aged 45 and older had ever had heart disease. The two reports describe different populations and measures.

Welltory's data-source documentation describes connections through health hubs and direct services. Available records depend on their source. It warns that connecting the same source both directly and through a hub can create duplicates. Its wellness interpretations, including stress-related estimates, should not be presented as a medical diagnosis.

Empirical Health requests Apple Health access to supported Apple Watch heart, sleep and activity records. Its data-collection page lists categories it may request; a request for blood-pressure data does not mean a watch measures it. Its terms distinguish the platform from clinical services delivered by independent medical providers. Check eligibility and what a plan actually includes before arranging care or subscribing.

HeartWatch organizes Apple Watch information across activity, sleep, workouts and wellness displays. Its dashboards can also include records supplied to Apple Health by other sources. Check where a displayed measurement originated before treating it as a watch measurement.

A blood-pressure reading needs an appropriate measurement device; a cholesterol result needs its own test. Heart rate, HRV, ECG information and oxygen estimates answer other questions. ApoB and Lp(a) are laboratory measures, not readings an ordinary watch creates. Ask your healthcare professional which records, including home readings, would be useful alongside your appointments and how to share them. An unexplained graph should not determine medication changes.

Dexcom G7 and Nutrisense: follow the glucose data back to its sensor

The CDC's September 2026 statistics page estimates that 12.0% of the U.S. population had diabetes in 2023 and that 115.2 million adults had prediabetes. The population percentage is not an adult-only percentage.

A continuous glucose monitor estimates glucose in the fluid between cells. The NIDDK's CGM explanation describes the sensor, transmitter and compatible display. The Dexcom G7 system and its companion app belong in that category. A watch displaying a sensor's result has not independently measured glucose.

Dexcom's Direct to Watch explanation describes a supported G7 sensor connection to a compatible Apple Watch, with a compatible phone required to pair a new sensor. Check the exact compatibility listing for your region, sensor, app, phone and watch. G7 and G7 15 Day are separate systems; an indication or setup instruction for one should not be transferred to the other.

Nutrisense combines glucose trends with meal and lifestyle records. Its bring-your-own-sensor page lists supported sources by platform. Ask which route supplies the records and how quickly they arrive. Imported history, a sensor's current display and an alert used in a care plan can have different timing and purposes.

For diabetes care, use the prescribed system's instructions and your care plan. Another analytics app does not inherit a sensor's regulatory clearance or replace its required alerts. The FDA's warning about watches and rings distinguishes devices claiming to measure glucose on their own from displays connected to authorized sensors.

RISE: work with sleep records without chasing every score

RISE describes estimates of sleep need, sleep debt and daily timing. Its wearable-connection guide explains importing sleep through Apple Health or Health Connect, with some direct connection options. First check that your source actually writes sleep records to the route you plan to use.

The ordinary app's coaching and RISE's separate clinical sleep service are different offerings. Check which you are considering and whether its eligibility and cost fit your circumstances. A personalized schedule is not proof that an app diagnoses or treats your sleep problem.

If reviewing scores makes bedtime stressful, you can reduce dashboard checking and keep a simpler record of your schedule and daytime symptoms. Persistent sleep problems deserve a conversation beyond the app. The sleep-tracking guide explains why consumer stage estimates and a clinical assessment need different interpretation.

Natural Cycles, Flo and Clue: distinguish cycle records from contraception

These apps should not be grouped under one promise about wearable temperature or pregnancy prevention.

Natural Cycles lists specific compatible wearables. Oura's integration instructions describe transferring temperature trends after syncing, with membership requirements for applicable ring generations and a separate Natural Cycles subscription. Follow the instructions and eligibility for the specific Natural Cycles product and intended use. A ring's own cycle display is a separate feature.

Flo's Apple Health guide describes permission-based sharing with category limits. That connection alone does not establish a particular wearable-temperature pathway. Flo says it is not birth control; a low predicted probability does not mean pregnancy is impossible.

Clue's wearable guide lists different imported metrics for different partners. Its temperature explanation distinguishes wearable temperature from manually recorded basal body temperature. Clue's current fertile-window guidance says not to use that estimate to prevent pregnancy.

Choose a cycle record for the job you need. If pregnancy prevention or fertility care is the purpose, discuss the appropriate method and its specific instructions with a healthcare professional.

TrainingPeaks, Habitify, Medisafe and Bearable

TrainingPeaks can connect a training plan with supported workout records. Its Apple Watch guide separates sending structured workouts to the watch from receiving completed workouts through Apple Health. It also says that daily steps, resting heart rate and sleep do not synchronize through that connection. Check the workout type and targets you actually use.

Habitify can use permitted Apple Health records to check progress toward supported habits. It also documents limited writeback for supported manual entries. Logging time in bed is different from recording sleep stages. Check the category before expecting two-way sharing.

Medisafe's current U.S. developer listing includes an Apple Watch app and medication reminders. Check its current requirements and reminder settings on your devices. A reminder can support your routine; it does not establish that a dose was taken or replace prescribing instructions. Discuss uncertainties about dosing with your prescriber or pharmacist.

Bearable combines your own symptom and mood entries with supported imported records. Its data-direction explanation says it reads external health data but does not write symptom or mood entries back to those platforms. If an import fails, check the upstream hub and permissions. A correlation in a journal can help you describe a pattern without proving its cause.

Check one connection before adding another

Write down the record you want, its source and where you expect to see it. Confirm your exact device and phone requirements, then check the receiving app's permissions. Look for missing or duplicate entries before trusting the combined view.

For example, choose a workout recorded after you enabled the connection and within the receiving app’s supported import period. Note its date and time in the source app. Synchronize the source, then check the receiving app for the same activity. Compare its timestamp and source if those are displayed, and confirm that it appears once. If it has not arrived, check the provider’s stated delay and whether that activity type is supported before adding another connection. A delayed record and an unsupported category need different fixes.

Review subscription renewals, export options and deletion instructions. Ask what happens to previously shared copies if you disconnect. Think about whether the app needs the information you are being asked to supply, especially symptoms, medication details, cycle and fertility records, or routes that reveal where you spend time. Inspect sharing, retention and deletion settings before importing historical records.

For medical records, ask your clinic whether it accepts an export and how to send it. Start with the connection that addresses your question and keep it only if it remains useful.