Things feel like they have stalled a little with regards to the calendar on the web client, and the app on iOS. Some things that I have noticed recently that have been around for a while:
My weight shows as different in the web client to the app
Date formats on both platforms do not respect country conventions (they are formatted in the US MMDDYYYY rather than DDMMYYY.
I often use an iPad Pro 11-inch to view my calendar. This is only possible in landscape mode. Surely the web calendar can be scaled to a display of that size in portrait? This only became a problem with the updated calendar.
Searching for workouts in-app versus on web is different for no apparent reason. Why is the duration filter field closed in-app by default? Surely thatās one of, if not THE most important field when picking a workout? Why is the workout duration filter sometimes in Hours:Minutes and sometimes just in minutes? Why is the order of the filters different on web versus on app?
It is very annoying to have to jump between the app and the web browser to do certain tasks when using a phone. Want to view your calendar? Has to be in the app. Want to analyse your ride? Has to be on the web client. Why canāt it all work in one place?
The app on iOS is really really laggy now. Sometimes I canāt navigate the interface for up to a minute when I first open it, and then it will register all touches at once. Sometimes the same quick menu can be loaded over itself another multiple times and you have to navigate back through them all. Sometimes the interval time and total time fields will lag and jump when completing a workout. This lag has been spoken about before and it seems to be getting worse not better.
Iāve been a TR user for more than 7 years now, and these moments of friction for the user start to get pretty frustrating after a while. Does anyone else have little niggles they would like to add?
I find the app to hang a lot when opening or displaying workouts or old data. Especially when trying to add in RPE. Itās really annoying. They clearly have a lot of data loading issues going on.
Yep, same issue on the IOS app when trying to add RPE or find a workout from a few months ago in the calendar. It becomes unresponsive and there is no indication that itās loading slowly or that an error has occurred.
For what is really a very basic app itās criminal how slow it is. I bought a new (android) tablet simply to run TR and while itās a lot better it a) shouldnāt have been necessary and b) still feels like a laggy piece of shit.
I hope the developers theyāre using for all the AI-led stuff are more competent than their front end developersā¦
Iām having the devs take a look at the slowness on iOS.
As for the weight not syncing, it should be the same between the app and the web. Iād be curious whether you notice it doesnāt sync after you update on the app or on web? Both? If you can post a screenshot of what you are seeing that would be great as this may be a bug.
Iām a bit confused by the filters in #4. The duration dropdown in the app, the list view in the Filters tab on the app, and the list on website are all showing the same to me. Maybe the reference to sometimes showing in minutes is referring to the Workout Alternates duration filter?
If you could also provide screenshots for these that would be great
āIām having the devs take a look at the slowness on iOS.ā
Itās not just iOS, and theyāre already very definitely well aware of how inefficient the app is. Please ask them to re-do it in vanilla html/css/js and stop using whichever ridiculously bloated frameworks theyāre currently in.
I just wanted to clarify here that the app slowness issue is being discussed by the team and itās high priority for us to make sure we get that sorted out.
I have been experiencing a log of hangs in the app iOS as well when dealing with the calendar, finding alternates, etc. Btw another thing if you have an outdoor workout schedule you canāt find an alternate using the app, you need to change it to indoor or use the web.
I am still having a lot of problems with the IOS app to the point where I have almost completely stopped using itā¦ Sometimes the field for RPE is completely blank, other times it freezes, sometimes gives limited options.
So I have to add RPE to my rides using the web client because I do not get any or all of the options on IOS. But then when I open the calendar on IOS the rides all say āadd RPEā even though I have already done it through the web app. I have given up on the IOS app completely. Unusable.
It seems to me like thereās some disconnect between the published app minimum system requirements in the App Store and reality. Up until recently, I had an iPhone 8 with iOS 16, which while absolutely old, was well within the minimum system requirements in the App Store. The app was really laggy as others here have experienced and at times borderline unusable on that phone without a lot of patience, restarting the app, etc. I recently upgraded to an iPhone 16 running iOS 18, and the lagging is definitely reduced thus far and the crashing hasnāt happened. Thereās definitely issues that need to be ironed out that it sounds like the team is working on, but I also wonder if itās worth revisiting device requirements to better set expectations for users. I needed a new phone for other reasons (abysmal battery life, mainly), but the TR app was the only app giving me repeated issues with lagging and crashing, making me think the device really wasnāt actually up to the task of reliably running the app especially since a new phone has drastically improved things for me thus far. If the phone can technically open the app but the app runs so poorly on the device to be borderline unusable, that doesnāt really seem like it actually meets the minimum requirements to me. Probably not the explanation for everyoneās issues, but figured Iād share my experience in case itās helpful in any way.
