Skip to main content
The Health page answers one question before anything else: how you are doing right now, as a single score, with the areas behind it underneath. Everything it shows comes from Apple Health on iOS or Health Connect on Android, plus the check-ins you type yourself. Nothing is read from your phone unless you switch it on.

The score and the dials

The number at the top is your health score, with a plain-language band next to it (“ready”, “steady”, and so on) and a line telling you how many of the past days were actually measured. A score built on two days of data says so rather than pretending. Beneath it sits a row of dials, one per area. Each dial shows that area’s own score and a line of context, and tapping one opens the area screen behind it. Under the dials, a short summary explains what moved, followed by How to move it: two to four concrete cards (“+2,400 steps”, “+35 min sleep”) with the points each would add to your score. Trends and history at the bottom opens every signal by week, month, or year.

Choosing which dials appear

The Health header carries two buttons: the sliders icon opens Dials, and the pencil opens Correct a reading. Tap the sliders icon to open Dials and switch areas on or off. This is purely about what you want to look at: switching off the Sleep dial does not stop sleep syncing, and its charts stay in Trends either way. Dial choice is stored on your account, so it follows you across devices. Fewer dials also means bigger ones; the ring size falls out of how many you show rather than being fixed.
Body has no ring. There is no honest target to grade a weight against, so the Body dial shows your latest reading instead of a score.

Area screens

Every area screen follows the same shape: a headline stat, charts you can flip between week, month, and year, and an About section explaining where each number comes from and how far to trust it. Area screens hide charts with no data. If you have never recorded body fat, the body fat chart is not there, rather than sitting empty and implying you forgot something. Trends is the exception: it shows every series whether or not it has readings, because that page exists to tell you what the app can track.

Body

The Body area at /health/body covers weight and composition. It plots weight and body fat over time, and reads from both sources at once: check-ins you type in Progress, and readings your scale writes to Apple Health or Health Connect. Change is measured against your first reading in the log, not yesterday’s. A day-to-day difference on a bathroom scale is mostly water, and a fortnight is the shortest window that means anything. Days with no weigh-in are drawn as a break in the line, never as a drop to zero.
Smart-scale body fat percentages come from electrical impedance. Treat a move from 22 to 20 as real and the 20 itself as approximate.

Correcting a reading

A watch left on the charger produces a day that is wrong rather than missing, and every number on this page is a composite: one night recorded as two hours of sleep drags a fortnight of recovery down with it. The pencil in the Health header opens Correct a reading so you can say so. The sheet steps back through the last seven days, one at a time. Beyond a week you are guessing rather than correcting, so it stops there. Each day offers sleep, steps, resting heart rate, heart rate variability, active energy, weight, and body fat, and every row is labelled with where its number came from: read from Apple Health, you typed this, or nothing recorded.
1

Pick the day

Use the arrows either side of the date, or the calendar button to jump straight to a day. Today is the default and the furthest forward you can go.
2

Type the right number

Enter what the reading should have been. Sleep is typed in hours even though it is stored in minutes, and weight follows your unit preference.
3

Save

Whatever you typed is what every score on the page now uses.
Corrections are recorded per field, not per day. Fixing a bogus resting heart rate leaves that day’s step count synced and still updating, so one bad sensor does not freeze everything the phone recorded alongside it. To hand a field back, tap Use synced on its row, or clear the box and save. The override is dropped and the next sync owns the field again, restoring whatever the health store actually says.
Values outside the plausible range for their metric are refused, not rounded to the nearest legal figure. A slipped decimal point should look like an error rather than settle quietly into your baseline. The message names the range.

Pushing corrections back to your phone

The sheet carries an Also update Apple Health switch (Health Connect on Android). It is off by default, and it only changes what other apps see: OneRep uses your corrected figure whether or not you turn it on.
Your phone will show two readings for that day. Neither Apple Health nor Health Connect lets one app amend a sample another app wrote. A correction is added next to the original rather than replacing it, so the health store ends up holding both your figure and the device’s. This is a limit of the platforms, not something OneRep can work around, which is why the switch is off until you ask for it.
If your phone refuses the write, because you declined write permission or the record type cannot be written at all, the correction still stands inside OneRep. A refused write-back is never a reason to lose the edit.

Filling a custom metric from your phone

Custom metrics can read themselves off your phone. When you create one, tap Fill from Apple Health and pick a catalogue entry: blood glucose, blood pressure, caffeine, VO2 max, and everything else the two stores expose beyond the ten OneRep scores on.
  • The unit comes from the catalogue rather than from your description, because the unit the sync writes in is not negotiable
  • Metrics your phone cannot deliver stay on the list, greyed, wearing the reason. “Your platform has no record for this” is a better answer than a metric that quietly is not there
  • Typing a value yourself marks that day as yours, and the sync stops overwriting it
  • Type it myself at the top of the list is the way back to an ordinary manual metric
A bound metric is labelled Read from Apple Health wherever it appears. See Progress for the rest of the metric builder, and the catalogue for every signal you can point one at.
Custom metrics are moving onto this page, to be grouped and scored alongside the readings already here rather than sitting apart in Progress. The metrics you have keep their history and their bindings through the move, and the API surface does not change. The layout will be documented once it stops moving.

Choosing what OneRep may read

Go to Settings → Health & wearables. Turn on sync, grant the permission your phone asks for, and then use the switch list below to decide, metric by metric, what OneRep reads. The list is grouped into Activity, Recovery, and Body, and covers the ten metrics the app scores on: A metric you switch off is never read from the phone in the first place. This is a sharing control, not a display filter: the app does not fetch the readings, so there is nothing to delete afterwards. Switches are stored per metric on your account. A metric added in a later release arrives switched on if its catalogue default says so, and one you explicitly switched off stays off through every update.
Bone mass is Android only. Apple Health has no bone mass type at all, so the switch has nothing to read on an iPhone however you set it.
The switches are inert until sync itself is on. Each row says Turn on Apple Health sync first (or Health Connect, on Android) rather than moving and doing nothing.
For the full catalogue of what each platform exposes, and the metrics you can point a custom metric at, see Health metrics by platform.

Body composition sync

With the Body metrics switched on, weight, body fat, lean mass, bone mass, and basal metabolic rate are read from HealthKit or Health Connect and filed as check-ins, in the same place a typed weigh-in lands. Your scale readings show up in Progress and in the Body area without a second data set to reconcile. Two rules keep this from eating your own numbers:

Typed beats synced

A check-in the sync did not create is never overwritten. If you typed a weight for Tuesday, no later scale reading replaces it. Editing a synced row makes it yours, and the sync stops treating it as its own from then on.

Only what the reading carries

Only fields a reading actually contains are written. A scale that reports weight but not body fat cannot blank a body fat percentage you recorded by hand on the same day.
Readings outside a plausible range for their metric are dropped individually. One badly behaved app writing a 900 kg weigh-in loses that field, not the day. Every check-in records whether it was typed or synced, and that source is returned by the API and MCP tools alongside the values.