You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice UX if competitions in the same country as the user (determined either by the region in their WCA profile, or from geolocation data from their request) were "pinned" to the top of the "Upcoming" list.
An extreme version of this would sort competitions as follows:
Competitions the user is registered for
World Championships
Continental Championships
Competitions in the user's country
All other competitions
The text was updated successfully, but these errors were encountered:
Honestly, WCA Live isn't the right place to search for competitions, because some organizers import the competition to WCA Live only shortly beforehand, and if we are talking about competitions in a few weeks then it's unlikely that they are imported in general. For that reason I think sorting by date is the most reasonable. The list of upcoming competitions is there for a reference, but honestly I would expect users to only care about ongoing competitions in practice. We could special case user-country competitions within each date span, but most users won't be signed in, because they have no reason to.
The thinking here is for users to quickly and easily find ongoing competitions, especially on busy weekends. I agree it would be low priority and if you feel it's unncessary/out of scope we can close it.
The thinking here is that people are generally opening WCA Live wanting to see results for a particular competition, and using some sort of sorting order can decrease the friction (ie scrolling) to finding that comp.
It would be nice UX if competitions in the same country as the user (determined either by the region in their WCA profile, or from geolocation data from their request) were "pinned" to the top of the "Upcoming" list.
An extreme version of this would sort competitions as follows:
The text was updated successfully, but these errors were encountered: