Nike+ Exporter 1.43 / 1.44

I have posted a minor update to the plugin which incorporates the most popular feature request, to have the list sorted in reverse order (i.e. most run first).

Also, I have added what might be a fix to the timezone issue. If the error occurs again, please email me your debug logging so I can diagnose further.

Update 24/01/2013: More bugs fixed with the timezone issue. Hopefully fixed now. Please try v1.44.

Please download the latest version by clicking the “Download” menu option above.

Nike+ Exporter v1.4

I have just released version 1.4 of the Nike+ Exporter Chrome plugin. Note the name change from Nike+GPX Export to just Nike+ Exporter, which highlights the biggest change with this version: TCX export!

I need more people to test this new functionality, so if TCX is your thing, then please try and use it and send me all your feedback. I also want to know if there is any need to split the run into multiple laps (e.g. km or mile laps, or as just one large lap). Also, with TCX I can put multiple runs in the one file so let me know if there is any need for such a feature (i.e. export all runs to TCX or perhaps export all runs on page to TCX, etc)

Here is a screen shot:


Click “GPX” for GPX export (only available for runs with GPS data), or TCX (which should work for runs without GPS data as well). Also there is a new icon for the toolbar (let me know if you like this one better than the old one.

If this version works well, I will submit it to the Chrome Web Store which should make it easier for novices to install.

Please download the latest version by clicking the “Download” menu option above.

Known Issues

A number of people have been said that runs might not be available for export for 2 hours, which could be a timezone issue.  However, I am yet to get any debug information. So if you have the same issue, or any other issue, can you send me the debug information using the following method:

  • Open up your console log after you log in (Right Mouse Button on the extension window, and inspect element/Console)
  • Use Plugin until the error occurs
  • Then cut/copy everything out of the console and send it to me in an email at

Running Apps Review

Over the last couple of weeks I have been comparing a few of the running apps currently on the market. It is an extremely crowded area with Sports Tracker, Runtastic, Runkeeper, Nike+, Strava, and Endomondo, to name just a few.

My all-time favourite is, without a doubt, the venerable Sports Tracker ( It was the pioneer, originally available on old Nokia Symbian (and developed by Nokia Labs) phones, and was eventually spun out of Nokia into a separate company. The web site is currently an all-flash site (I believe they are moving to HTML5 currently and are in beta testing), which is hugely functional and looks great. Their Android and iPhone apps also look and work fantastically. Sports-tracker also sell their own branded HR monitor.

The reason I went looking at other apps was because Sport-tracker was occasionally doing a really bad job at plotting the GPS path, giving me different distances for routes that were exactly the same. Also, some of the newer social and motivational features of other platforms including challenges, and recording/reporting records such as fastest ‘x’ km, or number of runs per week, etc, were missing. I also asked Sport-Tracker about public web services to get access to run data and they said that it was not a priority for them, which was a position that annoyed me considering almost every other service offered an API.

I tried Runkeeper but didn’t like it compared to Sports-Tracker, and dumped it immediately. Next stop was Endomondo but it was way too ugly for my discerning taste (ha! – I have been working with UX Designers for too long).

Nike+ then became free and I gave it a go. I loved the simple interface, calibration option at the end of the run, the fact that it stopped the phone from locking during the run like Sports-Tracker, how you could easily read the screen while running, and, best of all, hit the screen at any time to have the run details spoken to you.

What I disliked was the data was locked up in Nike+ with no export or import options. I wrote Nike+GPX export plugin to help with that issue, and also use the Garmin Forerunner TCX to Nike+ utility ( to import runs into Nike+. The ‘achievements’ feature were great (although when the GPS gets it wrong it can record personal bests that are incorrect and unrealistic with no easy way to back out).

Then I had friends start to use and recommend Strava. Easy, just export the GPX file from Nike+ and import into Strava which does a great job during import to smooth the GPS coordinates, and the process is essentially seamless. The social features are great, just like a ‘facebook’ for running. The custom segments are my favourite feature, which gives you a leaderboard for public segments, which is very motivating (and demoralising at the same time) . The GAP (Grade Assisted Pace) for split times is a good feature (even though I think most elevation data is normally wrong). And to boot, Strava has a public API (which I am yet to try but will do soon).

I spent last week trying out the Android app, and was very disappointed. Firstly, it does not stop the phone locking and therefore I had to type my password while running to check the details/pause/stop the run which is unacceptable. I found the Black-on-Gray text harder to read than the Nike+ White-on-Black text, and could not hit the screen for the voice features.

Further, a friend who was trying to complete a long distance challenge had the application crash while submitting his last 22km run, He emailed tech support and the response was just “sorry, the run is lost”. I have never had that happen while using Sports-Tracker or Nike+, so am not going to risk it.  I consider this an application architecture issue that is needs to be fixed.

I checked out Runtastic last week, which seemed good but it has ads (if you don’t pay), does not seem to have (on first look) Strava’s public segments features, and has an over-blown/out-dated UI (in my opinion, of course).

So, using Nike+ on Android as my running app, and exporting to Strava at the end of the run, is the best proposition for me right now (I also import into Sports Tracker to keep it on the radar and to have my entire run-history in one place).

Nike+ GPX Export v1.3

Sorry about all the activity lately, but I am travelling at the moment and have a bit more spare time than usual. I have just release version 1.3 of the plugin, which has the following features:

  • Export of Heart Rate data.
  • Fixed errors while trying to export runs with no GPS coordinates. The file now is created, but I don’t think it will be very useful with no data in it…
  • Indicators for runs that have GPS data (globe) and Heart Rate data (heart)
  • Fixing run descriptions to no longer include “undefined” etc.
  • UI tweaks

A big thanks to Byran for helping with this by supplying example data.

(Update 09/Oct/2012: New Version 1.32 released to fix bugs)

Please download the latest version by clicking the “Download” menu option above.


New Version of Nike+ GPX Export (1.1)

I have just released a new version of the Nike+ GPX Chrome Plugin (Version 1.1) to fix a problem with only some accounts (thanks Aleix for pointing out the issue). It turns out that I needed to strip out the white-space in users screen names in order to request the list of runs. This is a small change, but let me know if stops anyone from working. I also formatted the distance and duration fields in the table to make it more readable.

I am still working on heart-rate monitor export support (sorry for the delay).

Nike+ GPX Export

Given my inability to make a decision to switch completely to Nike+ from Sports Tracker, I have developed a solution to export Nike+ runs as GPX files which can be easily imported into Sport Tracker (manually). It is a Chrome plugin, which will login into Nike+ and then list your runs, and next to each run is the ability to export to GPX files.

Caveat – Nike+ doesn’t provide an interface to give the exact time at each GPS location, so I use the split data (1 kms) to average each GPS location over each KM (i.e. profile/lap data is accurate only to a 1km resolution).

There are other sites around that provide this kind of feature, but the latest Nike+ update broke most of them (at the time of this post). Therefore, this is the only option I have which works with the current Nike+ as of August-2012.

Please download the latest version by clicking the “Download” menu option above (or at the top of the blog web site for those using RSS readers).