New home screen gets a hard nope. Too tedious for my poor vision. JMO
You can change the scaling/size of the screen in the settings menu, did you try that?
Received update for macOS last night. Main thoughts:
- I am used to picking one of my custom workouts and then selecting a route, but I canât do that anymore. Iâm first asked to pick from a selection of routes presented to me. It tells me to cancel, find a route, then after starting route, choose my workout. THIS IS WAY TOO COMPLICATED to have to do every time I want to workout.
- It takes too long to find my favorite route (the pretzel). There has to be a way to mark one or more routes as a favorite so I can find them quickly. Ideally make it an optional property of a custom workout.
- Once I start on a route, if I then choose my custom workout, it doesnât start some of the time (60 minute free ride).
- Even though my Saris smart trainer was detected (ANT+), it wasnât offering much resistance based on my current FTP set in my custom workout. I re-calibrated it using the Saris iPhone app to be sure but that didnât fix the issue.
- ERG mode is not working for me anymore. Bumping up the intensity has no effect.
I suspect 4. and 5. have to do with the fact that I now have to start a route and then pick a workout, something I never did before. I always picked my custom workout (which has ERG mode enabled with a specific FTP set) and then chose the route.
UPDATE: 4. and 5. were due to my trainer not being paired using the version of the trainer shown in the list that had âFE-Câ in the name. I hadnât had to re-pair my trainer in at least 2 years and didnât notice when I re-paired in an attempt to fix things.
I did not experience #4 and #5. check in the paring screen that you paired as Power source and Controllable using FE-c option.
Gerrie,
I did check and re-check the pairing of the trainer/power meter/etc. but Iâll double check these were done using the FE-c option.
Thanks
The new home screen pins my Memory and GPU. It calms down once I select an event, but it has crashed mid-event once since. I was very surprised and disappointed that after it froze, it remembered where I was on the course, but experience stats and most of the points were lost.
My experience thus far with Zwift apps leads me to think you are leaning way too heavily into agile and product management. The fact that there are two apps and a website all with different purposes indicates you donât really have a strong idea or internal agreement about where you are going. You seem to be focused too much on the short term and not enough on your overarching architecture and user journey. It shows. There should be no way that stats are lost when the app crashes, but Iâm guessing that is buried deep in someoneâs backlog and gets deprioritized in favour of whatever you think will bring more subscribers in the next month.
Iâd rather say that it is a plus that Zwift are doing at least something in a somewhat agile way and addressing some of the most obvious UX issues to boot. The problem is that the product has at least 7 yearsâ worth of unaddressed technical debt, and doing anything at all on top of a foundation like that results in, well, you know. At this point, the most sustainable and efficient solution would be a complete reimplementation of the entire platform, but I donât think that is coming anytime soon, Iâm afraid.
Being update to the new Home Screen with no choice and not being able to join Zwifters seems like a downgrade to me. Consider this feedback to restore the ability to join Zwifters ASAP.
Gerrie,
Youâre right. Somehow when I re-paired the devices none of them were using the FE-C option.
Thanks
Still feels like a feature gap and a workaround. Workarounds are not feature solutions.
Iâm not sure why there is this insistence that users HAVE to ride the guest worlds. Just give users an easy accessible feature to choose.
You have three worlds to pick from. You do not HAVE to ride the guest worlds. You can ride Watopia which is always there.
There are two guest worlds which is two more than there were 3yrs ago (iirc?). Then Zwift added one guest world. Then 2yrs ago, they added a second guest world.
Finally have the new screen. Took me a while to realize you could get to the list of routes at the top â was already VERY tired of having to scroll down and then hit exactly the magic spot to scroll sideways just to get to the âpick a route yourselfâ option. That seems suboptimal? I tried changing the âsizeâ option but unless I pick âExtremely smallâ (which includes illegibly small font) I canât get the routes card to fit on the screen.
Jumping right into an event: nice. Definitely am eagerly awaiting being able to pick my route for workouts rather than either having to do a million steps or just canceling-repicking-canceling-repicking until an acceptable one shows up in the âsuggestionsâ.
Also, another random UI feedback note, although this one isnât new: on Mac, I think the program is trying to automatically size so that it doesnât overlap the dock, but my dock is on the left and it always puts one dockâs worth of extra space on the right. I generally maximize Zwift anyway, but still.
Love the product in general, but not at all a fan of the new Home Screen UI - (on MacOS)
It requires more clicks to set yourself into the right thing you want for the ride.
You can no longer see all the aspects in one place together (e.g world, course, workout selected, sensors are paired) with o know you are good before you press go.
It is less functional e.g. if starting a workout there are 3-4 courses in total possible without going through a frictional process to find the world/course you want, start a free ride and then start the workout.
Felt strongly enough about this to figure out how to send feedback on this. Please roll me back.
Nobody will be going back.
Just out of curiosity, can anyone explain why the new home screen rollout would be done in this way, i.e. being attributed to small batches of accounts using the same device platform, over a period of weeks/months?
Apart from the scaling issues that were dealt with early on, I donât think thereâs anything else that has been visibly modified on the screen for PC since the rollout began, so I wonder why it isnât just being given to everyone on the platforms for which it is available.
Is there some semi-manual process involved at ZHQ for the switch? Or some other reason that makes it too resource-heavy to do in one go? Iâm curious what the logistics are, compared to a game update that is made available to all users at the same time.
I got the new home screen yesterday. Having followed all the discussion on here so far and learnt from everyoneâs comments, it was relatively straightforward to navigate. Lots of room for UX improvement, as pointed out already here.
I did notice that my ten day-old PC, which is only used for Zwift, was far noisier (fans span up high very quickly) and hotter pre-ride when I was in the garage and setting up, than it was last week when mid-ride in crowded ToW, for example. FPS was lower, too.
I have to say that I not a fan of the new UI. It is always difficult to get the masses to agree to a change but the general consensus here is that the new UI is not an improvement & I agree.
More clicks required & making customised option choices more difficult = less satisfaction.
I hope you are listening to your paying customers Zwift.
Horizontal scrolling should NEVER be a thing. Ever.
I said it earlier, Iâll say it again.
This is going to be a NIGHTMARE on AppleTV.
Contrary to this I would expect it to work very well in terms of navigation precision on Apple TV, seeing how you can now navigate to anything with cursor keys, enter, and esc. However, some things require too many cursor key presses now so unless some of the user journeys are shortened significantly, there will probably be far too many swipes on the ATV remote compared to what my thumb joints can stand in the long run.
Example: Now it takes approx. 20 keypresses to start a ride on Watopia Flat - every time you want to ride that.
Itâs a massive resource hog, and the whole game performs noticeably worse than it did before. One would think this would have been picked up in the aforementioned testing phases.
Only if you are looking for it.
Or paying attention. . . ![]()