Hi, I’m getting back on the bike after an extended break and am working on setting up a Base-Build-Peak plan but am having an issue. The web UI has really low weekly target hours versus the iPhone app. See attached photos - that’s the final week of the plan where you can easily see the difference (iPhone app telling me I should be doing nearly 20hrs that week versus less than 9hrs on the iPhone app). Any idea what could be going on? I don’t think it is a big issue because I expect I’m naturally going to have to way overshoot the web UI target hours in order to get the XSS I need, but it is confusing nonetheless. I feel like I’ve maybe asked a question similar to this before but pretty sure this is the first time I’ve noticed that the iPhone app seemingly has more reasonable targets.
The first thing I notice is the date selection differs. In the Iphone picture the week goes from august 5 to 12. In the web site picture the week goes from august 9 to 15, which is 3 days past the end date of the program. That could explain the lower number of hours.
Unfortunately it doesn’t matter. Both data sets slowly ramp up and the taper week actually doesn’t really seem to reflect a taper. I think that may be part of the issue, the hours aren’t the core metric of the Xert framework, XSS is, so potentially this are just instances where it’s not 100% accurate but the decision was made to not worry too much since we don’t train to accumulate hours, we train to accumulate XSS (ie magic buckets structure where you can do the prescribed ride in a short time or a very long time depending on intensity). Now that I’m talking thru it, I’m nearly positive I’ve asked this same question and I may have just parroted the official response I got.