Imperial vs. Metric #103
Replies: 4 comments 1 reply
-
|
Yes — this is a clean, doable feature and a fair gap. NOOP is metric-only and hardcoded right now (km / kg / cm / °C), so if you think in miles/lb/°F some screens read like a foreign language. The good news: everything is stored in SI (we normalise on import), so a units toggle is purely a display-formatting change — no migration, no re-import. The cleanest version is a small shared formatter reading one preference, so we convert in exactly one place per platform (that's how unit bugs get avoided). One question for the thread: one combined Metric/Imperial switch, or independent toggles (distance / weight / temperature)? Lots of people are mixed — metric distance but °F, or stone for bodyweight in the UK. I lean toward one primary toggle with a temperature override, but I'll build to what people actually use — so tell me your combos. Strong candidate for a near-term release. Thanks for raising it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again for the combos question upthread — I'm going to build this as one primary Metric/Imperial toggle plus an independent temperature override, which covers the mixed setups people actually run (metric distance with °F, that kind of thing). Default stays metric so nothing changes for anyone who doesn't go looking for it. The shape, for anyone curious: everything's already stored in SI, so this is purely a display layer. One small shared formatter per platform reads a single preference and converts in exactly one place — distance (km/mi), bodyweight (kg/lb), height (cm/ft-in) and temperature (°C/°F). HR stays bpm everywhere because that's universal. The Coach will speak your units too, so it won't tell an imperial user they ran 10 km. One thing I want to get right rather than fast: our skin-temperature readout is sometimes an absolute value and sometimes a small ± deviation, and those convert to Fahrenheit differently (a deviation doesn't get the +32 offset). So I'm writing tests around that specifically before it ships — a wrong sign there would quietly break the illness watch. No firm version number yet, but this is near-term. I'll post here when it lands. Last call on the toggle design: if you (or anyone reading) specifically want stone for bodyweight, say so now and I'll fold it into the same picker. |
Beta Was this translation helpful? Give feedback.
-
|
Shipped in v1.80 — there's now an Imperial/Metric toggle in Settings (distance, weight, height, temperature, with a separate temperature override). It's display-only — everything stays stored in SI, so nothing re-imports. Thanks for the nudge; grab v1.80 and switch it in Settings → Units. |
Beta Was this translation helpful? Give feedback.
-
|
Shipped in v1.80 — a full Imperial / Metric toggle in Settings covering distance (km/mi), weight (kg/lb), height (cm/ft-in) and temperature (°C/°F), with a separate temperature override. Display-only; your stored data is unchanged. Closing as resolved. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is probably in the roadmap but I'd like to see Imperial / Metric conversion
Beta Was this translation helpful? Give feedback.
All reactions