A Zwift Runner’s Wish List

I recently reached out on social media to the Zwift running community to see what Zwift running improvements they would like to see and also what bugs they would love to have fixed.

The results were surprising in that the majority of people are really happy with the Zwift running experience. Suggestions for improvements were minimal. The overwhelming majority of responses focused on fixing parts of the experience that don’t quite work as they should.

I’ve touched on it before: it’s common sense to expect that the development of running goes at a slower pace than cycling.  Although a healthy number of runners also ride and, therefore, are paying subscribers, there is also a large number of running-only members which Zwift receives no revenue from. 

I’ve separated the wish list into two sections: feature improvements and bug fixes.  So here you are, Zwift; this is what the running community would like…

Feature Improvements

Full Treadmill Control

For a long time many have wanted Zwift to control their treadmill in terms of automatically adjusting the gradient in line with the route you are running.  Hand in hand would be the ability to adjust the speed automatically when doing a workout. 

Both of these are possible using third-party software, but Zwift has never done this natively.  Those who have tracked the introduction of the Wahoo KICKR Run treadmill will have seen in the videos that this treadmill has that ability within Zwift. 

Those with other compatible treadmills would love this too!

Cycling Parity

Of course we want more levels!  And more badges for routes (yes I know we just got 10).  This I guess is where the debate around paying subscribers comes in.  Other requests were for a drop shop to purchase equipment and a running streak like cyclists have.  A workout editor also received several requests, it exists for cycling but not running.

Basically, parity with the cycling side of Zwift is sought.  So I guess the question would be, “Should runners start paying to open up these extra features?”

Power-Based Metrics

Many advanced runners like to run using power rather than speed.  Popular amongst multi-discipline athletes, power-based running using a suitable power meter such as Stryd allows for better analysis of a run in order to calculate efforts, etc…

Retain Mileage Between Events

Most runners run a set distance.  A few will run for a set time.  I’ve previously touched on how running alone can be dull, whereas in a group it’s more interactive.  Therefore, the request is that we retain our distance when we hop in and out of events. 

For example, say I’m wanting to run a 10k today.  There are two back to back 5k events starting half an hour in between.  It would be great to run 5k in the first event, then join the second event but the distance kept as one rather than autosaved and split in two.  (I’m also aware of the limitations to doing this, as if the events are in two separate worlds the Companion map for the activity is going to lose the plot a little.)

Integrated Speech To Text

Typing and running is a fine art.  Most people can’t manage it.  The result is that group runs can be a bit silent.  Speech-to-text is hit-and-miss, to say the least.  Despite the odd comical interpretation, it’s very dependent on the quality of hardware and software used.  Although it would remain reliant on your own hardware, wouldn’t it be great if there was an on-screen button that could be pressed for speech to text? 

Bug Fixes

Chat Function

The number one requested fix was the ability to have all chat visible to all runners during group events.  The chat function, like cycling, has a proximity limit to stop chat appearing from far away athletes, so it stays relevant.  However, running doesn’t attract the large numbers in group events like cycling events, so it would be great if everybody was involved.  Likewise, runners don’t tend to run in groups like a cycling peloton and everybody is spread out over a route.  (The workaround is to pick group events using a small circular course but then this limits the number of available routes.)

Include/Exclude Time Leaving Pen

The time to leave the pen until the course starts isn’t included in your run. At times, this could be up to 40 seconds, depending on the route.  The net effect of this is that your average pace at the end of the group event will not match your actual pace.  If you use the Companion app, the time starts when the route starts, whereas the in-game time starts before.  This also sends the distance markers wayward. (In London, this in really noticeable.)

Setting A Target

Those that run in KM will have known the fight with the distance target setting.  It jumps all over the place and doesn’t accept the distance you set.  Changing to miles often resolves this. 

Also, the maximum number of KM available to set is 30, which is under marathon distance. The ability to set a target beyond 30 would be awesome.

Beacons

Like cycling, you can have a lead beacon and sweep beacon in run events.  If the leader changes mid-event there seems to be a delay in the beacon changing, and if you have two nominated leaders on course the yellow beacon can jump between them.  Likewise, the red beacon often isn’t visible to the leader, so they have no idea where the sweep beacon is.  Others see the red beacon but the leader doesn’t.  Seems to be world/course dependant. 

RoboPacers

They suddenly disappeared without warning and seem to be taking a well-earned holiday.  Apparently they weren’t that popular, hence them being given a break – but actually people are missing them and would like them to return if possible.

What About You?

Does this list cover the Zwift running feature requests and fixes you’ve got? If not, share yours below!