Skip to content
← Apple stack HealthKit, both ways

Every set, in your Health database.

Most lifting apps write a workout envelope to Apple Health — duration, calories, activity type, period. The per-set detail dies on the way. flexRep writes every set as its own workout segment with the exercise, the load, and the reps attached. The bench press you logged is still bench press six years from now, even if you uninstall the app.

FRAMEWORKS HealthKitWorkoutsHealth metadata
The four points

What this actually does, in flexRep.

01 / 04

Per-set detail, not just an envelope.

Every set writes to Apple Health as its own segment with the exercise name, the load, the reps, the RPE, and the set type attached. Your bench press at 225×5 is still bench press at 225×5 when Health reads it back, even from a future install on a future device.

02 / 04

Two-way body weight + bodyfat percentage.

Step on a smart scale that writes to Health — flexRep picks it up. Log a weight in flexRep — Health picks it up. The sync is in the free tier on day one.

03 / 04

Quality tiers — full · partial · summary.

Imports from other apps carry a per-set quality tier so you always know what is authoritative versus reconstructed. The in-app "About Apple Health Sync" sheet names every caveat honestly.

04 / 04

The recovery path of last resort.

Phone wipe? Future install? The detail on Health is enough to rebuild your training without losing what mattered. Apple's platform is the survival path — not a server we control.

Where we stop

Four refusals on this surface.

  • We don't paywall HealthKit sync.
  • We don't write only a session envelope.
  • We don't silently overwrite Health-authored data.
  • We don't need a flexRep server to make this work.

Log once. Land it everywhere.