The blog has taken a bit of a back seat of late as I’ve attempted to get as many of the pages migrated across to the new Strava APIs as possible. The previous version of VeloViewer was around a year old and had grown slowly over that period and the replacement version will follow a similar path. Currently only the VeloFlow screen isn’t able to be migrated due to a few missing options in the new API but the majority of the rest of the site (and more) will be coming back on-line over the next few months. Where possible I will be improving those pages as I migrate them and also adding some interesting new features. As it stands I’m rather thankful that I have managed to get access to the new API as it seems a large number of people in a similar position to myself haven’t and it looks like that is how it will be for the foreseeable future.
Category: General
VeloViewer Usability Survey – The Results!
A massive thank you to everyone who took the time to fill in the usability survey and for those that added some comments at the end. VeloViewer’s final SUS score is 76.3 (out of 100) and here is how the responses averaged out:
VeloViewer Usability Survey
To continue the underlying driving force for VeloViewer (a playground for ideas for my day job) I want to try out a usability review of the site which I will then attempt to get my employers to embrace for their own products. For this I’ll be using the well proven System Usability Scale (SUS) that is made up of 10 very simple questions which can provide a great measure of usability for a website (or app) that can easily be bench-marked against any other sites (or apps). The survey should take less than 2 minutes to complete and is just 10, simple, multiple choice questions. A huge thank you to those of you that do take the time to fill it in.
Take the survey by clicking here! – Survey finished. Thanks for your feedback.
In a few weeks time I’ll post the results and show how it compares to other sites. I might run a similar survey for your views on the Strava site, you’d hope they would score a fair bit better than VeloViewer!
There will be a number of changes to VeloViewer as I swap over to the new Strava API’s during which I will attempt to improve the usability where I can, especially around the update page. I’ll post a blog entry soon as to what those changes are likely to be (for better and worse) when I get chance. Once the next version is live and in use I’ll run another of these surveys to see if the perceived usability has improved.
Train like Wiggins, ditch the power, use the VAM
I’m currently multi-tasking my late night baby feeding with reading “My Time” by Bradley Wiggins and was interested to read the following:
“The data we had been working on for road racing in 2012 was not power output or speed, but VAM. The average VAM for a big climb on the Tour in 2010 was 1,530-1,600: 1,530 on Plateau de Beille, 1600 on l’Alpe d’Huez.”
Welcome to the VeloViewer blog!
Due to almost unexpected popularity of the VeloViewer site, the complexity of it’s content and the constant trickle feed of new features I thought I would set up a more formal place to document what is going on and how things work so you can make best use of what’s already there and discover the new stuff.
I’ll try and work through the various areas of the VeloViewer site and explain what everything means. Check out the categories list on the right for a (hopefully) more structured view of the posts.
Post a comment if there is anything specific you want me to cover off sooner rather than later.