Zwift doesn’t need to be modified to follow a sequence. It already has the functionality in place. If it didn’t you’d not be able to select a direction already.
You also wouldn’t have it use a sequence of left/right. You would define it by the “segment” name.
This gives them the ability to more easily add additional options in existing intersections, and allows for an easier reverse course turnaround method.
Like I said, I look at it from a resource management perspective. What you think is a simple addition (it’s actually, going to take longer than an hour, and it will have to touch the hands of the UX/UI Designer, needs to touch various devs, QA, UA, etc.
While each of those hats may be filled by one or many people, it’s broke out as individual resources.
Even if it touches each resource for just an hour, you’re looking at between 5-10 hours (depending on testing/bug encountered, etc) just for a single addition to a feature.
That’s 5-10 hours of resource time that can be spent on a new fully functional feature, or, the way you look at it at the end of the project, is time given back to work on existing bugs or features in the pipeline. Then, and here’s the other kicker, you have to dedicate more time down the road once you launch a more inclusive feature.
In order for Zwift to be manageable, make a profit, and continue development, they are going to need to start managing their resources better.
I can already tell just from the broken continuity in the UI, that they have just been trying to rush features to make sure there’s enough changes to build and keep interest in the product.
If they had thought the feature through, they would have realized that recycling the existing UI of the workout selection (as you mention, that came before the workout creator) that uses a populated list of choices for route selection (climbing, flat, group, standard, blah blah, even Century), then they would be done with UI design.
Now they need to dedicate a resource to add a new radio button if they want to add a new option, that button needs to have additional code added to make it functional, and they need to modify how all that interacts.
Borrowed elements saves time, it also provides continuity to the user base.
This was a big update by them. It’s possibly the biggest update in terms of them showing us what Zwift can do/become and will definitely breath life into watopia.