News

So it seems that v1 of Nike’s service is back up… well some of it. I tweeted this a few days ago, but I didn’t want to announce it here until I was sure. As it stands, most of v1 of Nike+PHP should work and the widget I created is working again too.

It looks as though Nike have removed their support for v1 of the API. Although I have been working on v2 of the API, I am not even close to being able to release anything yet.

I will update the site when I get some time to work on v2, but for now, it looks like Nike+PHP is unusable.

As a subscriber to the Mac Rumors twitter feed, I came across this tweet yesterday. As you may be aware, Nike+PHP has returned a few heart rate specific fields, but to the best of my knowledge I had no idea on how to get your Nike+ device reading that data.

So it seems that there are plans for a Nike+ hear rate monitor, that could make it’s first appearance in early June. I’m glad to say that, while it seems that not all iPod’s/iPhones will support this new service, Nike+PHP should be able to handle the data instantly!

Work continues on v2 of Nike+PHP and I’ll do my best to make sure this is included.

Nike seem to have changed their approach slightly, but thanks to a user reporting a problem with the Nike ID script, I’ve been able to add better error reporting and hopefully fixed the issue all together.

If you enter incorrect details, you should get a message asking you to check them and the form will be presented to you again.

Last week, I revealed gCount to the wall. Simply put, it’s a small service that counts the total downloads of a specified Google Code project. Its something i’ve always wanted fo display on Nike+PHP as a badge of pride more than anything! You can see the download count over on the main Nike+PHP site.

Despite what I said in my post yesterday, I’ve created a roadmap page to give a small heads up on what the future holds for Nike+PHP.

The short version is that there will be a v2 sooner rather than later, but v1 will be around for as long as there is a v1 on Nike’s ‘api’. Check out the roadmap page for more information and for updates.

I’ve had a road map since v1.0 and that roadmap continues for the next two versions of Nike+PHP, the beta releases ensure I had everything ready and from v1.0 I’ve been able to create the first widget for the project.

Without revealing too much about where I want Nike+PHP to go, I am looking to create more widgets and get the project out there. Because of the nature of the project, I’m not sure a WordPress widget is really appropriate, but I I’ll make them all compatible by making them rely on JavaScript.

I’d like to hear from users of Nike+PHP about what widgets they’d like built for them. I have a few in mind, but I think catering for what the community really wants would be the best way to go. Please feel free to contact me privately, or post a comment to this post. I won’t close comments on this post until I’m ready to start a second batch of these requests.

Getting your Nike+ ID has always been one of the hardest issues, but I’ve made it a hell of a lot easier!

You can now get your Nike ID by filling in the Nike ID form. I do not capture any results and the form below is used purely for retrieving your Nike ID.

To make it easier to maintain, Nike+PHP’s support website (this one) has moved to a WordPress platform. The code continues to be hosted on Google Code, but this new platform should mean that I can now provide a RSS feed for updates and news about the project, something I wasn’t really able to do with the old site.

If you have any comments/concerns about a release, please comment on the latest release, and I’ll do my best to respond where necessary.