This means that each source must be handled differently. Each of these sources have unique data signatures – the data is registered in the same fields but with different meanings. There are currently dozens of different sources for the runs that end up on Nike’s site: the watch, the footpod, the iPhone and Android apps, runs sent from Tom Tom, runs sent from Garmin, the Apple Watch, and even connected treadmills. I invested an embarrassing amount of time in the task. So, I rolled up my sleeves and attacked the issue wholeheartedly. It pained me to see the frequent problems and errors. We have a fair number of Nike users on Smashrun and, for many people, the data we’ve retrieved has become the sole existing record of those runs. This turn of events is all the more painful because I’ve just spent over a month working to make the Nike import bulletproof. We’re not an official partner of Nike, and so we don’t have any recourse, but to wait and hope that they fix something. As of Sept 28th, new runs are no longer flowing through the pathways we use to retrieve your data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |