The web app
There is nothing to update. Refresh the page and you have the current version —
new work goes out continuously rather than in numbered releases, so there is no
version for you to be behind.
If a page looks wrong after an update, a hard refresh (Ctrl/Cmd + Shift + R)
loads it fresh rather than from your browser's cache. That fixes almost every
"it looked fine yesterday" report on the web.
The mobile app
The mobile app is not on the App Store or Google Play, so there is no update to
install and no auto-update to switch on.
Downloading the app explains wherethings stand and what to use meanwhile.
If you are running a test build, updates arrive the same way the build did — a
new TestFlight version on iOS, a new download link on Android. There is no
in-app update prompt.
Checking your version
In the app: Profile > About, which shows the version.
On the web there is no version to check, for the reason above. If you are
reporting a problem on the web, the date and time it happened is the equivalent
detail, and it is genuinely useful.
Release notes
We do not currently publish release notes or a changelog, and there is no
"What's new" screen in the app. If a change affects how you use ClapDiet, it is
reflected in this help centre — every article carries the date it was last
checked against the product.
After an update
If something looks wrong after an update:
you were doing when you noticed
Signing out and back in is worth trying early: it is quick, and it clears the
one kind of stale state that survives a refresh.
Early access
There is no public beta programme to join. Test builds are shared privately
with a small group. If that changes, it will be described here.
Related Articles: