Welcome to the forum. I’ve moved your post under an existing topic with the same feature request.
I did this because TrainerRoad likes to group discussions into single topics when practical. You can see the existing discussion above for reference.
Welcome to the forum. I’ve moved your post under an existing topic with the same feature request.
I did this because TrainerRoad likes to group discussions into single topics when practical. You can see the existing discussion above for reference.
As far as I understand it, the Fatigue, Fitness, and Form (or ATL, CTL and TSB) model is proprietary to Training Peaks, and requires some form of licensing by other apps to use it in their systems. I don’t know the specifics beyond that.
So, that may be a contributing factor to TR’s integration of it.
That aside, this functionality has been requested for a while now without it being acted upon.
Hard to speculate as to the reasons.
A few years ago, one could argue that those metrics were less intuitive to use for those new to endurance training and better suited to power-users, more experienced athletes already using Training Peaks and/or detailed analysis tools like WKO. However, with mainstream companies like Garmin building these functions into most of their consumer wearables today, it can be argued that even casual athletes may now understand and find these metrics useful.
In a recent TR survey asking for future state ideas, I requested this — along with the potentially heretical idea that they open the TR platform up to allow other coaches to develop training plans for their platform. This gets into deeply philosophical waters about whether TR should consider separating their amazing training platform from their ‘coaching’ functions. It would be very complicated and most likely necessitate subscription tiers, etc. I’ll leave that hornets nest alone for now.
As a user of TR and Training Peaks, I’d love to see either more integration with TP (let me automatically sync my TR training plan into TP - where I can do more sophisticated seasonal strategizing and forward planning). Or, integrate TP functionality into TR (and possibly make using TP unnecessary — simplifying my life).
Another thing to consider is TR’s development team size and budget. Being self-funded, we know (and appreciate) that the team considers where they invest their efforts carefully.
Going by what we’ve recently seen with the integration of running into the TR platform (and perhaps Jonathan’s recent tri-curiousness ) that triathlon-oriented functions feature prominently in the TR product roadmap. If so, then integrating swimming might be in there somewhere too.
This could suggest that for now, TR is having to prioritize widening their base of possible users rather than refining the other end for those who are deep into it and seeking specialized functionality per their experience level or specific discipline.
Mostly speculation on my part. I happen to advise companies on this kind of thing for a living, so hard to resist temptation sometimes.