The Future
June 5th, 2007 | Published in Youtube API
Hi everyone!
Last Thursday at the Google Developer Day, we announced that the next iteration of the API will be based on the Google data ("GData") standard! We hope to release read feeds later this summer. As the date gets closer, we'll be posting announcements and documentation here, on the developer homepage, and the forums. Check out our presentation on, of course, YouTube: http://www.youtube.com/watch?v=zEUDvEd31F8
Why GData?
- Better scalability/stability/flexibility
- Standardizing on an existing framework - easier to mash up with other GData APIs
- Setting us up for write feeds later in the year by using the authentication models
- Developers can leverage GData resources, such as client libraries and developer guides
What will happen to the old API?
The existing API will continue to be available for the foreseeable future, but all new features will be built into the GData API. Plenty of notice will be given before the current API goes anywhere.
What do I do now?
Give us feedback! This is your chance to let us know what you want in a YouTube API. The team goes through the API Feature Request wiki regularly, so sign up for our forum (if you haven't already), and get involved!
We hope that the new API will improve the developer experience, and make it even easier to add YouTube content into your project.
Cheers,
Steph
Last Thursday at the Google Developer Day, we announced that the next iteration of the API will be based on the Google data ("GData") standard! We hope to release read feeds later this summer. As the date gets closer, we'll be posting announcements and documentation here, on the developer homepage, and the forums. Check out our presentation on, of course, YouTube: http://www.youtube.com/watch?v=zEUDvEd31F8
Why GData?
- Better scalability/stability/flexibility
- Standardizing on an existing framework - easier to mash up with other GData APIs
- Setting us up for write feeds later in the year by using the authentication models
- Developers can leverage GData resources, such as client libraries and developer guides
What will happen to the old API?
The existing API will continue to be available for the foreseeable future, but all new features will be built into the GData API. Plenty of notice will be given before the current API goes anywhere.
What do I do now?
Give us feedback! This is your chance to let us know what you want in a YouTube API. The team goes through the API Feature Request wiki regularly, so sign up for our forum (if you haven't already), and get involved!
We hope that the new API will improve the developer experience, and make it even easier to add YouTube content into your project.
Cheers,
Steph