A few more bugs here:
Bug: Start Workout layover briefly flickers onto screen at a resistance change
This happened to me on one of my workouts on Sunday. It only happened once, and I do not know how to reproduce it.
Bug: In some workouts, the change resistance beep is too late
During today’s workout, the beep that you hear before a resistance change was about 5 seconds late. Instead of three beeps I only got the first one.
UI issue: Touch targets on go back chevron way too small
The go back chevron’s touch targets seems to be only the chevron rather than also e. g. the text next to it. While this may make sense, it requires too much dexterity and precision — both come at a premium during or after hard intervals.
I have tested and reproduced this issue on both, my iPhone 7 and my 12.9" iPad Pro (2018).
Proposed solution: Significantly increase the touch targest.
UI issue: Calibration screen not adapted to larger screen sizes of iPads, especially 12.9" iPad Pros
The screen is plain ugly and hard to use as all pertinent UI elements are kilometers apart.
Usability issue: Calibration value not displayed on in-workout power meter calibration screen
I have another issue with the same calibration screen: it no longer displays any value. Preferably, it should display the before and the after value. This way, users can detect large drifts that indicate a problem with their setup.
UI issue: Legend for power profile can be partially off-screen (12.9" iPad Pro (2018))
Another big issue is the workout preview. It comes in from the right and barely uses any space even though I have tons left on my iPad. What is worse, when I want to check the power profile, when I arrive at the second half of the workout, the legend with the power data and duration is partially off-screen and becomes unreadable.
UI improvement: display workout times more appropriately
The length of TrainerRoad’s workouts is always quantized in minutes and there are no workouts that are longer than 9:59:59. So the duration should be formatted accordingly, rather than 00:30:00, it would be easier to read “0:30 h” or “30 mins”. There are iOS APIs that do this automatically. You can configure them to display either e. g. 90 mins or 1:30 h or something similar. My podcast client displays 30m, and it is perfectly clear from the context what the implied unit is.