ResourcesSetup
Setup

Apple Health vs Google Health: how step and calorie sync actually works

📖 5 min readBy the Yōdha teamUpdated Jul 2026

If you are running a challenge across a mixed group, half your people are on iPhones and half are on Android, and the two phones keep their fitness data in completely different places. On iPhone it is Apple Health. On Android it is Google Health (Health Connect). The good news is that from your members' point of view the setup is nearly identical: grant an app permission once, and their steps and calories flow in on their own. This guide explains how each side actually works, so you know what to expect and can help anyone who gets stuck.

Two ecosystems, one job

Both platforms do the same thing: they are a private, on-device vault where your phone and watch deposit your activity, and where apps can read it only after you say yes. Nothing is shared until you grant permission, and the permission is specific, one data type at a time. Understanding that shape makes every setup question easier to answer.

How Apple Health works

On an iPhone, Apple Health is the central store. The phone's motion sensor logs steps and distance whenever it is in a pocket or bag, and an Apple Watch, if there is one, adds far more: heart rate, active energy, and full workouts. Apps like Yōdha never talk to the sensors directly. They ask Apple Health for permission to read specific figures, and the person taps to allow Steps, Active Energy, and Workouts.

On iPhone, permission is granular and one-directional. If someone's steps sync but their calories do not, it is almost always because the Calories toggle was left off during setup. It is fixed in seconds under Settings → Health → Data Access & Devices.

How Google Health works

Android is a little newer here. The hub is Health Connect, which on recent phones (Android 14 and up) is built right into the system settings; on older phones it is a small app from the Play Store. Health Connect is the meeting point: a source app writes activity into it (the phone's own fitness tracking, Samsung Health, Fitbit, a Wear OS or band app), and other apps read from it with permission.

That two-step shape is the one thing worth knowing about Android. There must be something feeding Health Connect in the first place, and then the challenge app is granted permission to read from it. If a member is brand new to it, the flow is: make sure a fitness app is tracking their activity, allow that app to record into Health Connect, then let Yōdha read from Health Connect.

What "connecting" actually does

Connecting grants read access, nothing more. Your members' health data is not uploaded to a public profile or sold on; the app simply reads the same step and calorie numbers their own health app already shows them, to keep the leaderboard live. Leading with that reassurance removes most people's hesitation at the permission screen.

Getting a clean setup

A few habits make the difference between smooth sync and a support message:

  • Grant all three: Steps, Active Calories, and Workouts. Steps alone leaves cyclists and swimmers looking inactive.
  • Wear the watch if there is one. An Apple Watch or Wear OS watch captures far more than a phone in a pocket, especially for non-walking exercise.
  • Pick one source per person. Two apps both writing steps into the same hub is the usual cause of double-counted numbers. One tracker feeding the platform keeps totals honest.
  • Give it a few minutes. The first sync backfills recent history, so a new joiner's board does not stay at zero for long.

When the numbers look off

The handful of issues that come up, and what they mean:

  • Phone and watch disagree. The watch is the more complete source; the platform de-duplicates so nobody is counted twice, and the higher, watch-based figure is the right one.
  • Calories show zero on some Android phones. A few devices (some Samsung models) are stingy about writing active calories into Health Connect. A good platform works around this by deriving the figure rather than showing a zero, so your Android members are not unfairly stuck on nothing.
  • Data is not appearing at all. Ninety percent of the time a permission toggle was skipped. Re-open the health permissions and confirm Steps and Calories are on. On Android, also confirm a source app is actually feeding Health Connect.
  • Steps look doubled. Two source apps are writing the same activity. Turn one of them off as a source.

The short version for your members

You do not need to teach anyone the plumbing. The message that works is: "Download Yōdha, enter the code, and when it asks for health access, allow Steps, Calories, and Workouts." That single sentence covers both platforms. For anyone who wants the exact taps, point them at the connect-your-steps help page, which walks through iPhone and Android screen by screen.

On Yōdha, this is the whole setup: one permission and people are on the board, whether they carry an iPhone or an Android. Any group, one leaderboard, no matter what is in their pocket.

Free download

Get the team-challenge playbook

The full six-part guide as a polished PDF you can forward to your team or committee. We will email it over.

No spam, just the occasional new guide. Unsubscribe anytime.

Ready when you are

Run it on Yōdha.

Yōdha sorts your group into Clans, syncs from Apple Health and Google Health, and runs a live Yodha Board so you never touch a spreadsheet. Score steps, active calories, or both, and people join with one code in under two minutes. Any group, one leaderboard.

Start free at yodhaclans.com