PhormLab is in a beta
Thank you for trying it. This page says what works, what does not yet, and where to send what you find. It is kept up to date — if something here is wrong, that is worth reporting too.
What works
- Connecting Strava and syncing your history. The first sync is the longest thing the application does; with years of activities it takes a few minutes and you can leave the page.
- Your activities with splits, heart rate zones, best efforts and photos.
- Training load, form and the risk tile, computed from your own thresholds.
- The plan wizard: goal, availability, and a plan you can adopt into the calendar.
- Equipment, injuries, resting heart rate, goals and milestones.
- German and English, light and dark.
What is unfinished
- There is no payment. The plan switch in the profile costs nothing and charges nothing; it exists so the coached features can be tried out.
- The assistant needs your consent and can be switched off again at any time. It proposes; it never computes a plan on its own.
- Automatic sync via Strava webhooks may not be active yet. Until it is, the sync button is the way.
- The mobile layout has been built for a phone but not worn in. Anything that feels cramped is worth a screenshot.
- Nothing here has been used by many people at once. If something is slow or behaves oddly, that is exactly the kind of thing this beta is for.
Your data
It is real training data and it is treated as such: encrypted Strava tokens, encrypted backups, no tracking, nothing sold. You can download everything or delete the account at any time from the profile. What is stored and where it goes
One honest warning: this is a beta run by one person. Backups are taken nightly and the restore has been tested, but if something breaks badly you could lose up to a day. Do not let PhormLab be the only place your training exists — Strava keeps your activities either way.
Reporting something
Write to the person who invited you. Useful things to include: what you did, what you expected, what happened instead, and roughly when. If a page showed an error, the identifier at the bottom of the message helps a lot — it points straight at the request in the log.
Small things are worth reporting. A label that reads oddly in German, a number that looks wrong, a button in an awkward place: those are the reports that make the application better, and they are the ones people usually keep to themselves.