Journal des modifications
Short version: this is not a release log. It tells you where the notes for your version actually live, and — more usefully — what an update can and cannot change about the training data you already have.
The Lactate Training app changes over time: calculations get refined, screens get reworked, wording gets corrected, broken things get fixed. That is ordinary — but if you are eight weeks into a build and a familiar number suddenly reads differently, it raises a fair question: did something just change under me?
Where the release notes for your version live
Two places, and neither of them is this page.
- The store listing you installed from. Whichever platform you downloaded the app on publishes the notes for each release next to it, and that listing changes at the same moment your app does.
- The app itself. The version you are running is recorded in the app, so if you need to tell us which build you are on, it is there to find.
A hand-typed list on a website is always the stalest of the three. Pointing you at the live source beats keeping a copy that drifts and then quietly misleads you.
What an update can change mid-block — and what it cannot
Your training history does not reset. Sessions you have already done, and the analysis attached to them, are not wiped by an update. Your connected accounts stay connected. Updating does not sign you out of Garmin or Strava — if a sync looks stuck afterwards, the cause is almost always the ordinary one it would have been on any other day. And your plan does not vanish. Your scheduled sessions are still your scheduled sessions.
What can change is how something is worked out. If the method behind a figure is improved, the figure can read differently from the day before without anything about you having changed. That is a reporting change, not a fitness change, and confusing the two is why an update can feel alarming.
What you notice, and what it usually means
| After an update you notice… | The likely explanation | What to do |
|---|---|---|
| A threshold or fitness figure differs from yesterday | How it is calculated changed. Your body did not change overnight | Look at the trend across weeks, not the step |
| A chart looks emptier than it did | Data is still being re-read, or the range shown changed | Let the sync finish, then check the date range |
| Your zone boundaries have moved | Zones follow your threshold, so they move when it does | Check the threshold figure first — zones are downstream of it |
| Your plan looks reordered | The plan adapts to what you have actually done, update or no update | Check the dates against your last few sessions |
| Wording in your language reads oddly | Translations get revised, and a revision can be worse | Send us the exact sentence |
Reading a recalculated number correctly
A new figure is usually the better one, but it is not comparable with the old one — so do not read the step as a training result. A threshold pace that moves after an update is not three weeks of work arriving overnight, and it is not fitness lost. It is a different ruler.
Recalibrate once, then carry on: run the next easy session to the new numbers and see how it feels, because your own sense of effort is the check on any calculated zone. What a lactate threshold actually is explains why that one figure drives the rest.
If something looks wrong after an update
- Let the sync finish. The app may re-read a stretch of your history, and a half-finished backfill looks exactly like missing data.
- Check the connection is still live. The Garmin integration guide and the Strava integration guide cover the usual causes, almost none of them update-related.
- Compare weeks, not days. One figure moving is noise.
- Get in touch via the contact page with what you expected, what you saw, the session date, and your version.
Frequently asked questions
Why does this page not list version numbers?
Because a hand-maintained list goes stale and then misleads you. The notes published alongside the app on the platform you installed from are the live record. This page covers what those notes do not: what an update means for training you have already done.
Does updating the app delete my training history?
No. Your completed sessions and their analysis are not removed by an update. If something looks missing straight afterwards, the usual cause is a sync still in progress rather than data loss.
Why does a number look different after an update?
Almost always because the way it is calculated changed, not because your fitness did. A recalculated figure is not comparable with yesterday's — judge the trend over weeks instead.
Do I need to reconnect Garmin or Strava after an update?
Not normally. An update does not sign you out of a connected account. If activities stop arriving, work through the usual checks in the Garmin or Strava guide before blaming the update.
Will an update change my training plan?
Your scheduled sessions are not wiped by an update. The plan does adapt to what you have actually done, but in response to your training, not because a new version arrived.
Keep reading your own trend, not the step between two days
An update can change the ruler without changing you, which is why a single figure is a poor way to judge a block. Lactate Training syncs your Garmin activities and health data and your Strava activities, and builds and adapts a plan around them, with zones anchored to your lactate threshold rather than an estimate.