Nike+ plus has been around since 2006 when it was first introduced as a peripheral for the iPod nano. It worked by having sensor in the sole of your compatible Nike running shoe which sent the data to your iPod. When syncing your iPod to your computer, you could then send your exercise data to the Nike+ website for storage and sharing. Main issue with the Nike+ sensor is that it’s essentially a pedometer, it counts steps. There’s nothing wrong about using a pedometer, you just need to be aware of their limitations. Don’t expect better than ±10% accuracy.
In comes Nike+ GPS for the iPhone. As the name implies, it uses iPhones (3G, 3G S or 4) GPD receiver to track your run and you don’t, obviously, need to buy any hardware. I ran over 140km split across 10 exercises with the app. It’s not masses but I’d say it’s enough to get a good idea of what the app about. Much of the review is about how I would use it and the kind of training I’m doing so keep that in mind. I didn’t test the features I couldn’t care less of.
It’s only $1.99 (£1.19). Nike+ kit for your iPod nano is around £20. I think for that, anyone wanting a little bit of encouragement for your runs should get it and try it out. I really like the map view of the run with each kilometre (or mile) marked. What makes this even cooler is that you can switch to a ‘heat map’ view. This creates a gradient with green-yellow-red to mark the fast and slow parts of your run. Is that useful? I’m not sure. As it doesn’t take into count the effort you’re putting into the run, yellow or red might either mean your running slowly or you’re running slow because it’s an up hill (website has an elevation view as well but it’s only directional. Read: inaccurate). Nevertheless, it’s fun little feature to show off your run with.
You can also label your runs with your mood, weather conditions and write a short note to remind yourself how it went or what type of run it was.
If you’re Nike, you can have the likes of Paula Radcliffe and Lance Armstrong do voice overs for the app. So they did. Yesterday, Lance congratulated me for the fastest 10k I’ve recorded with it. Another time Paula said I just did more exercises this week than the week before. Nice touch.
I was also impressed with it not draining the battery too badly. I would leave for 3 hour run with a full battery and return with at least 60% left. Your milage may vary, I’m using it with the iPhone 4.
Heat map display should have a way of increasing the contrast around the areas where you’re actually running. To explain. Say I’m on a 15k run around the streets of London. There’s bound to be places where I have to stop or walk for ten, fifteen steps. These spots are marked as your slowest pace for the exercise although they might only count ten meters of the training session.
If Nike is listening, I’d recommend ‘crushing’ those areas off of the scale and marking them in black thus leaving more contrast for the actual run. At the moment all of the heat track just looks a bit too similar all the way through.
For the past two years, I’ve done more or less every one of my runs with the Polar RS200 SD. It’s extremely accurate. On my last marathon in Edinburgh, it was only 300 metres off. That’s less than 0.5%. People who have tested these, say that it’s more accurate than the current GPS based running computers.
That said, I’m very disapointed with the accuracy – or the lack of – with the Nike+ GPS. It can be that the iPhone’s Location Services isn’t giving it accurate data but most runs it’s been off by a considerable margin.
Look at the fig. 2. That’s a heat map of a run I did on 3rd October. Notice anything strange? Was I really running at 1:23/km pace? Pace faster than Usain Bolts pace on 100m. That fluke is caused by the GPS getting mixed up and it thinking that I’m in two very different places almost at the same time. The GPS tracking isn’t continuous, it pings the satellite every few seconds and if the location is very different between those two samples (see fig. 3), it wont think there’s something wrong. Instead, it’ll think I’m Clark Kent and thus capable of such speeds.
Not only does that screw up how the heat map is show. More importantly it throws of the total for the exercise. In the case above by almost two kilometres. Also, it’s not only limited to these large ‘once of’ inaccuracies. Look at fig. 4. At least when running in a city, there’s a constant jiggle on the route. This, over time, adds a fair bit into the over all distance. Trees and bridges are another weak spot. I think Nike could do a lot in software to improve the accuracy even if the GPS data isn’t perfect.
The last straw for me personally was yesterday. I was on a 10+10+10k run (cleverly to mark 10/10/10*) around my usual route through Tower Bridge and Westminster, when on the way back it stopped my exercise at around 24k mark without telling me it had done this. If you’re collecting data from your runs, nothing is more annoying than incomplete data.
I think it’s OK for some runners. I wouldn’t recommend it to long distance runners or anyone wanting a reliable way of recording runs that are longer than 10k. If you’re a beginner runner and want some encouragement, go for it. Me, I’m sticking with the RS200 but will also give RunKeeper a try so stay tuned for another one of these reviews.
*Take this a step further:
Running 10+10+10k in training for a marathon is fitting as 101010 is 42 in binary and marathon is just over 42k. #running