As most of you will know Strava is moving to a new and improved version of their API (the way I get all my data from Strava to populate VeloViewer) and I’m currently working on VeloViewer to use this new version of Strava’s API. In general we are all going to be very excited by what the new API will offer us and I’ll go into that very soon in another post, but there is one sad bit of news – the main API that drives VeloFlow will no longer be available 🙁 This will mean that I will not be able to get the list of rides to display and I can’t think of another way to do it. So, the only hope I can see to keep VeloFlow going is to get all you good people to vote up and comment on my request to save the API on the Strava support site to show Strava how much you all want to keep VeloFlow running.
Please visit my request to save the VeloFlow API on the Strava site and get voting (click the “Me too!” button) and commenting and we’ll see if the power of the people can make a difference!
Add comments on the request page rather than on this blog post. Ta!
Please note: This is only effecting the VeloFlow functionality on VeloViewer. The rest of VeloViewer will be improving immensely (QOM, runs, heart rates and much more) by using all the new goodies offered up by the new, improved Strava APIs. Strava have been very supportive of VeloViewer and this is made clear by them giving me early access to their new API.