Roadmap

Nike+PHP is a project I really enjoy working on, but over the last 6 months, quite a bit has changed.

When I started the project, Nike+ was still flash based, but in that time, they moved to a beta and now full release of their new site, utilizing v2 of their ‘api’.

In response to these changes, and to avoid putting the inevitable off for too long, I’ve decided to document the long term road map for Nike+PHP.

v1.x

For future versions of 1.x I’ll continue to maintain the script and whatever the final release is, will remain available for download. As long as Nike supply v1 of their ‘api’, I’ll try to support the project in this state.

v2

Since Nike+ seems to be stable in v2, I’ll be migrating the project on to v2 as soon as I can. This means figuring out their new calls, services and feeds, but that shouldn’t be too much of an issue.

Moving to v2 will give me the chance to implement a few more of the things I’ve wanted to do in the past.

Update: After playing with v2 of their ‘api’, the switch will not be as easy as I first anticipated. Whereas Nike+PHP is easy to use because you don’t have to wait for any logging in to happen, just for the data to be returned, v2 may be forced into taking that route. Now, this isn’t ideal, and not where I want to take the project, but that may be the only way forward. I have a plan on how to approach it, but i think v1.3 is a higher priority right now for me.

The method for returning data in v2 may also increase load/response times, which isn’t ideal, so depending on some near future testing, I may find that v1 will take on bigger cycles of development and incorporate more features rather than a complete overhaul of code.

What does this mean for Nike+PHP users?

I will maintain v1 for as long as possible, and even when I move from v1 to v2, I will do my best to keep the final arrays exactly the same. Some data might come in or drop out, but the service should be as similar as possible.

Originally, I planned that v2 would have more data available than v1, but that may change and v1.x may have just as much if not the same information, with both versions just relying on different ways of extracting it.