Skip to main content
The Activities tab, along the bottom.

The timeline

Your day in order: when you woke, sessions you did, protocols, first and last meal. Each row shows the time, what it was, and a summary. Tap for detail.

First: your activity catalogue

Menu → Activities Management is where you tell the app which activities you actually do. A new account starts empty, and that is the one setup step nothing else here works without. Until the catalogue has something in it:
  • a detected session has nothing to be linked to, so it cannot be logged automatically
  • you have nothing to pick from when logging a session by hand
Add the activities you do regularly — running, resistance training, whatever it is — and give them colours if you like. You can add more at any time.
Today will say “Set up the activities you want to track, then log one — detection starts from there.” until you have done both. Tap that message to go straight to the catalogue. Setting it up is the first half; detection only begins once you have logged or synced a session, because that is what gives the app a first day to work from.

Where sessions come from

Two routes: Synced from your device. A workout recorded on your watch arrives with heart rate, duration and often a route. Detected by the app. The Workbench can notice a period of sustained activity that no device recorded as a session — a long walk, say — and offer it to you.
A detected activity is a suggestion, not a claim. It is offered because the data looks like something happened. If it is wrong, dismiss it; if it is right but unlabelled, tell it what it was.

Session detail

Tap a session for distance, duration, heart rate, load, route where available, and notes. Notes are generated from the data — pace, speed, heart rate and so on. The app is selective: it will not put average pace on a resistance session, because pace is meaningless for it. Where a session has a GPS route, it is drawn, along with pace, cadence and per-kilometre splits. The app will also tell you when its own distance and your watch’s disagree, and by how much.
That last line — “GPS 3410 m vs the watch’s 3295 m — 3.5% apart” — is the app declining to pretend the two agree. Small disagreements are normal and worth ignoring; a large one is worth telling us about.
This example was captured on Android, so it names Health Connect. On an iPhone the same panel reads Apple Health, Oura or Polar. Everything else is identical.

Effort

You can record how hard something felt, on a 1–10 effort scale. Worth doing occasionally. Your sense of effort carries information no sensor has: the same session at the same heart rate can feel very different depending on what else is going on.
Polar users: effort ratings entered in the Polar app do not reach us — a limitation of Polar’s interface. Enter them here instead.

Linking

If a detected activity matches something in your catalogue, you can link them so it is recognised next time. This is what turns detection into something that works on its own: once a walk is linked to Walking, later walks can be logged without asking you. It is also why the catalogue has to exist first — there is nothing to link to otherwise.

Ask Eir

Where there is something to explain, the Eir circle appears here too. In this build it is tied to symptom context, so it will not appear often.