Google Data » Jarek Wilkiewicz

We’re going live from Google I/O

Jarek Wilkiewicz — Thu, 09 May 2013 19:13:00 +0000

By Mike Winton, Director of Developer Relations

(Cross-posted from the Google Developers Blog)

At Google I/O 2013, we will share the future of our platforms with you. Developers from all over the world are the key innovators of powerful, breakthrough technologies, and that’s why we challenged ourselves to make the Google I/O experience available to every developer, everywhere.

Watch Google I/O live
From the comfort of your own home, office, secret lair, or anywhere you have a reliable Internet connection, you can stream Google I/O May 15-16 live. Brought to you by Google Developers Live (GDL), the Google I/O homepage will become the GDL at I/O live streaming hub starting on May 15th at 9:00 AM PT (16:00 UTC). From this page, you can:

Stream 4 channels of technical content on your computer, tablet, or phone. You’ll feel like you’re right there in the keynote and session rooms, listening to product announcements straight from the source. Live streaming will run on developers.google.com/io from 9 AM PT (16:00 UTC) to 7 PM PT (2:00 UTC) on May 15 and 16.
Watch exclusive interviews with the Googlers behind the latest product announcements. This year, GDL will be on site, broadcasting one-on-one product deep dives, executive interviews, and Sandbox walkthroughs from the GDL stage.
Get the latest news in real-time. We’ll be posting official announcements during I/O. You’ll be able to see the feed on the Google I/O homepage, in the I/O mobile app (coming soon), and on +Google Developers.
Never miss a session. All Google I/O technical sessions will be recorded and posted to GDL and the Google Developers YouTube channel. Subscribe to our YouTube channel for archived session updates.

Live blog the keynote
Grab our live blogging gadget to add the keynote live stream to your own site or blog. Customize the gadget with your site or blog name, live blog alongside real-time Google announcements, and share a dynamic Google I/O experience with your readers. Have questions? For more info, check out our live blogging gadget FAQ.

Get together locally
Experience Google I/O with your local developer community by hosting or attending an I/O Extended event. If you’re hosting, register here and learn how to hold a totally epic event with our handy Organizer Guide. Otherwise, with over 400 sites in 90+ countries, chances are good that there is an I/O Extended event near you. Find an event now!

And before I/O, tune in to Google Developers Live programming to connect with Google engineers, prep for this year’s event, and browse our archived content. For official conference updates, add +Google Developers to your Circles, follow #io13 for big announcements, join the Google I/O community, and keep an eye on the Google I/O site.

Mike Winton founded and leads Google's global Developer Relations organization. He also enjoys spending time with his family and DJing electronic music.

The Helping Hand of an Expert

Jarek Wilkiewicz — Wed, 17 Apr 2013 21:17:00 +0000

Have you ever been stuck working on a problem only to receive a solution from a friendly person you've never met? Some of the most helpful responses on Stack Overflow and open source code examples have been contributed by our YouTube API community members. The Google Developer Expert (GDE) program is designed to recognize the active and passionate YouTube API developers who make these outstanding contributions.

Each year, Google Developer Experts are selected for their existing accomplishments using Google technologies, their continued passion for these technologies, and their willingness to engage with and mentor other developers.

To learn more about what it’s like to be a GDE, check out this interview with two of our 2013 YouTube API GDEs, Matias Molinas from Argentina and Tim Wintle from the U.K.

If you’d like to share your knowledge, connect with us on +YouTubeDev, contribute to Stack Overflow, and find like-minded developers at your local Google Developer Group (GDG).

Cheers,

—Jarek Wilkiewicz and Jeremy Walker, YouTube API Team

No WebView required, with native YouTube Player API for Android

Jarek Wilkiewicz — Fri, 21 Dec 2012 22:19:00 +0000

Adding a high-quality video experience to your Android application just got a whole lot easier. Starting today, you can embed and play YouTube videos in your app using the new YouTube Android Player API.

The API, which was pre-announced at Google I/O 2012, offers these benefits:

High-quality video playback supported on Android 2.2 (Froyo) or newer
Easy integration with your Android application (no WebView required)
Fullscreen and orientation change support
Closed captions display
Support for YouTube ads
Programmatic access, similar to existing Player APIs, to most aspects of the YouTube video playback experience
Integration with the Android YouTube app using a standard set of YouTube Intents

We are launching the API as experimental, though we do not expect major interface changes going forward.

The Only Limit Now is Your Imagination (and ToS)

These instructions explain how to include the YouTubeAndroidPlayerApi.jar client library in your Android application. The library is supported on Android devices running version 4.2.16 or newer of the Android YouTube app.

You can use the YouTubeApiServiceUtil class' isYouTubeApiServiceAvailable method to confirm that a device is compatible.

For a simple embed, use the YouTubeStandalonePlayer. To build a more sophisticated user interface, try the YouTubePlayerView or the YouTubePlayerFragment. Fragments can help create an engaging experience as shown in the Video Wall app example.

Play With These Apps

Here are a few interesting apps available for you to explore:

See everything on Flipboard, all your news and life’s great moments in one place. Now you can watch YouTube videos from wherever you are in Flipboard without leaving the application, providing a more integrated and seamless experience.
BuzzFeed delivers original reporting, scoops, and the hottest social content on the web. Android users can now view their favorite BuzzFeed content featuring YouTube videos in the BuzzFeed app and share with their friends.
9x9.tv enables users to discover and watch curated, topical videos that are organized into TV-like channels. Their blog describes their experience developing with the API.
SoundTracking lets people use their mobile phone or tablet to share their music moments and favorite jams with friends and family. Users can now discover and play YouTube music videos of the songs within their music timeline.
Fitness Flow by Skimble helps you get in shape with high-quality exercise videos led by professional trainers. Skimble uses YouTube to stream workout content on your Android phone and tablets.

Check out a few screen shots below or download the apps from Google Play today!


Flipboard	BuzzFeed	Fitness Flow by Skimble

Learn More

If you would like to learn more about the YouTube Android Player API, the documentation is a great place to start. In addition, we have curated useful videos in this playlist. Please subscribe to the YouTube for Developers' channel to keep up on the latest.

Check Out The Sample Code

We’ve prepared several code examples to make it easy for you to get started with the new API. You will find them on code.google.com. The description of the examples is available in our documentation. If you need additional help with the API feel free to use our support resources.

Cheers,
-- Ross McIlroy, Anton Hansson, and Horia Ciurdar, YouTube Mobile Team

The Simpler, Yet More Powerful New YouTube Data API

Jarek Wilkiewicz — Fri, 14 Dec 2012 22:07:00 +0000

Since its initial launch in 2007, the YouTube Data API has become one of Google’s most popular APIs by request volume, thanks to the awesome apps from developers like you. To help you make better integrated video experiences, you can now use the YouTube API version 3.0. The new API is easy to use thanks to rich client library support, improved tooling, reference documentation and integration with Google’s common API infrastructure. Version 3.0 only returns what you ask for and is using JSON rather than XML encoding for greater efficiency. The API introduces new core functionality including Freebase integration via topics, and universal search. If you develop social media management apps, you’ll love channel bulletin post and full subscriber list management, also new in this release. Version 3.0 of the API constitutes the API's biggest overhaul to date and we’re eager for you to try it today!

New Functionality: Topics, Universal Search, and Audience Engagement Support

Have you ever tried to search for YouTube videos only to find out that keyword search can produce ambiguous results? With the new Topics API, thanks to the power of Freebase, you can find exactly what you’re looking for by specifying Freebase topic IDs rather than search keywords.

For example, if you’re reading this post from outside of the US and would like to search for content related to football, /m/02vx4 is probably the topic ID you're after. The API's universal search feature lets you retrieve channels, playlists and videos matching the topic with just one request like this one. Find out more in our Topics API Guide.

Version 3.0 introduces better tools to engage and interact with one’s YouTube audience. Social media management apps can now help content creators communicate with their channel subscribers using buletin posts.

Efficiency, Client Libraries, Better Tooling and More!

To help you reduce your app’s bandwidth requirements version 3.0 only returns the information you ask for as specified by the “part” parameter.

While the default JSON encoding in version 3.0 is more efficient than XML in version 2.0, if parsing JSON isn’t your thing, check out the client libraries for .NET, Dart, Go, Java, JavaScript, Objective-C, PHP, Python and Ruby. The libraries use OAuth 2.0 authorization and work with the YouTube API as well as other modern Google APIs thus simplifying your application.

The familiar Google API tools such as the API console work with YouTube API version 3.0 without any extra hassles. Additionally, our API reference documentation now allows you to scroll down to the bottom of any reference page to try the API. You can also or visit the standalone API Explorer to browse a list of supported methods.

App Examples

Even though version 3.0 is still experimental, a number of exciting new apps are already using it. Let’s look at a few examples:

Showyou, an app that makes it easy to watch the Internet, integrated the Topics API to enable users to discover related videos after tapping on topics associated with the Showyou feed.

Argentina-based Interesante integrated the Topics API to determine the Freebase topic of videos being shared. Interesante used this to serve interest-based video recommendations.

FanBridge, a company specializing in growing and managing one’s fan base, recently introduced channel bulletin post functionality with scheduled posts support.

Tubular Labs, which focuses on YouTube audience development, uses subscriber list to help content creators develop a better understanding of their audiences.

Pixability, a company specializing in YouTube marketing software, was able to quickly port their Online Video Grader to the YouTube API version 3.0 thanks to the new Python client library.

Learn More

If you would like to learn more about the YouTube API version 3.0, in addition to the API documentation, the material curated in this playlist is a great place to start. Please subscribe to the YouTube for Developers' channel to keep up on the latest.

Use The Source, Luke!

Since the most fun way to work with it is to try it, we’ve prepared a few code examples in Python and JavaScript to get you started. For a more comprehensive client-side app using the Topics API, try the Topics Explorer. You can find its source code on code.google.com.

Cheers,
-- Raul Furnică, Vladimir Vuskovic and Pepijn Crouzen, YouTube API Team

All Good Things Must Come to an end=

Jarek Wilkiewicz — Fri, 29 Jun 2012 22:50:00 +0000

If you enjoy the ability to easily start video playback at a specific time using the start parameter, you may also like being able to stop it early. Here’s an example:

end=119" frameborder="0" allowfullscreen>

The end parameter is a positive integer, and it represents the number of seconds from the beginning of the video. If your friends are not into merengue dancing canines, you can now tease them with short clips of videos like the one below:

Cheers,
--Jarek Wilkiewicz, YouTube API Team

Minimum embeds: 200px x 200px

Jarek Wilkiewicz — Thu, 29 Mar 2012 16:15:00 +0000

If you're a careful reader of the YouTube API Terms of Service as well as the YouTube Player documentation, you may have noticed that while embedded players smaller than the minimum size might not support all player features, we haven’t defined what that size is.

As a part of our spring cleaning, we've tidied up our documentation to specify a minimum player size, which is 200px by 200px.

This change will take effect beginning late April 2012, so please check your application to avoid surprises. If you have any questions or comments about this, or any other YouTube API feature, please let us know on the API forum.

Cheers,

-Jarek Wilkiewicz, YouTube API Team

Upcoming YouTube API Events

Jarek Wilkiewicz — Fri, 28 Oct 2011 04:14:00 +0000

It was a pleasure meeting YouTube developers at the recent GDD, DevFest and GTUG sessions in São Paulo, Buenos Aires, Moscow, Prague, Paris and Warsaw. We would like to let you know that our around-the-world API tour continues and we hope to meet you at one of our upcoming YouTube API presentations. Here is the list of currently planned YouTube sessions:

GDD Tokyo, Nov 1^st: “HTML5, Flash and the Battle for Faster YouTube Cat Videos”
GDD Sydney, Nov 8^th: “Take a sneak peek at YouTube Live Streaming APIs”
DevFest Singapore, Nov 12^th: "Create Magical Apps and Engage Your Audience Using YouTube APIs"
GDD Tel Aviv, Nov 13^th: “HTML5, Flash and the Battle for Faster YouTube Cat Videos”
GDD Berlin, Nov 19^th: “HTML5, Flash and the Battle for Faster YouTube Cat Videos”

We will also be speaking at local GTUGs; for the most up to date information please check the event schedule of a GTUG near you. As always, upcoming event information can be found on our Google Developer Events Calendar available at http://code.google.com/events/.

Cheers,

--Jarek Wilkiewicz, YouTube API Team

Introducing Google Account support and YouTube API v2.1

Jarek Wilkiewicz — Fri, 07 Oct 2011 22:46:00 +0000

Update (December 2011): The YouTube API now supports associating an unlinked Google Account with a YouTube channel as well as providing username suggestions.

Authenticated access to YouTube APIs lets your app offer many features that are unavailable to logged-out users. By authenticating user actions, your app can allow users to manage subscriptions, create playlists, and upload videos. Until recently, users could only perform any of these operations if they had YouTube accounts. (A YouTube account provides a user with a YouTube channel.)

We are pleased to announce that we have also started to give Google Account holders who don’t already have YouTube channels access to certain YouTube features on YouTube.com and in the YouTube API. We call these unlinked Google Accounts since they haven’t already been linked to a YouTube channel. For example, a user with a Gmail account or an Android device is certain to have a Google Account but may not have already linked that account to a YouTube channel.

What this means for your application is that with a few relatively simple changes, you should be able to allow authenticated access for users who have unlinked Google Accounts. Thus, those users will be able to log in to YouTube without having to create a YouTube username.

In a moment, we’ll dive into the details of how to use the API with unlinked Google Accounts and also offer a few user experience recommendations for your YouTube API application. First, though, a quick note about the new minor YouTube API revision that we’re introducing.

Say "Hello!" to YouTube API v2.1

When designing this feature, we decided to take a conservative approach toward backward compatibility. The set of write operations supported for Google Accounts is currently a subset of API operations available to YouTube account holders. Rather than expose existing applications to accounts with potentially restricted functionality, we’re explicitly requiring that an application prepared to handle unlinked Google Accounts tells us so by using the API version 2.1, a new, minor version of the API. Our documentation explains that you can specify an API version by appending v=2.1 to the API request URI or by using the GData-Version: 2.1 request header.

HTTP response codes for authenticated operations

API v2.0 supports all authenticated operations for users with YouTube accounts, which could also be called linked Google Accounts, but doesn’t support any authenticated operations for unlinked Google Accounts. If the authentication token for a v2.0 API request identifies an unlinked Google Account, the API will return a 401 NoLinkedYouTubeAccount error.

In API v2.1, however, a number of operations that require authentication are supported for users with unlinked Google Accounts, and the API will return a 200 response code for those operations. For operations that aren’t supported for unlinked Google Accounts in v2.1, the API will return an HTTP 403 Forbidden error with a youtube_signup_required error code.

The table below shows how API v2.1 changes response codes when different types of users try to execute operations that require authentication:

	API v2	API v2.1
YouTube Account	200 OK	200 OK
Unlinked Google Account	401 NoLinkedYouTubeAccount	200 OK or 403 Forbidden youtube_signup_required

Handling the youtube_signup_required error

We do not recommend that you try to modify your application to provide a different experience for users with YouTube accounts than for unlinked Google Accounts. That approach would require you to constantly update your application as YouTube expands the list of features that we support for unlinked Google Accounts.

Instead, we recommend that you prepare your application to gracefully handle the youtube_signup_required error, preferably by associating the unlinked Google Account with a YouTube channel using the API, or presenting an option for the user to navigate to https://www.youtube.com/create_channel. If you are building a mobile application, you can bypass a redirect by using https://m.youtube.com/create_channel instead. The API documentation lists the operations that are and are not currently supported for unlinked Google Account holders.

The XML below shows a sample youtube_signup_required error:

 
  
    yt:service
    youtube_signup_required

User profiles for unlinked Google Account holders

A user profile entry for a user with an unlinked Google Account differs from a user profile entry for a user with a YouTube account in two ways:

An entry for an unlinked Google Account holder contains a tag. (This tag is not present if the user already has a YouTube channel.) It is useful if you choose to disregard our advice about the youtube_signup_required error and modify your application to provide a different user experience for users with unlinked Google Accounts.
An entry for an unlinked Google Account holder contains only a few tags as those users can not customize their profile data without first creating a YouTube channel. The tag definition lists the different tags that may appear in a profile entry depending on whether the user has a YouTube account or an unlinked Google Account.

Displaying an email address for unlinked Google Account holders

In addition to handling the youtube_signup_required error, your application should also be prepared to display an email address for users with unlinked Google Accounts.

In Closing

If you have reached this point in the blog post, thanks for being a dedicated reader. We recognize that unlinked Google Accounts do introduce a certain level of complexity, but, at the same time, they can also open your application to a much larger audience of users who use Google services but haven’t created YouTube channels yet.

We also want to note that v2.1 does not deprecate v2.0 since it is a minor revision. Going forward, new features unrelated to unlinked Google Accounts will be added to both v2.0 and v2.1 but not to the (deprecated) v1.0 of the API.

Version 2.1 of the API is now available for testing on stage.gdata.youtube.com, and will be released to production in mid-October.

Cheers,

—Jarek Wilkiewicz, YouTube API Team

YouTube API and the News

Jarek Wilkiewicz — Wed, 28 Sep 2011 19:23:00 +0000

If you love to follow the news as much as you love to code, then Hacks/Hackers, an international organization that sits at the nexus of journalism and technology, is for you. Its mission is to create a network of journalists (“hacks”) and technologists (“hackers”) to rethink the future of news and information. Recently, YouTube and LinkTV hosted a Hacks/Hackers meetup at Google’s San Francisco office. Together with four developer partners, we demoed web applications used by reporters and built using the YouTube API. The presentation started with a YouTube API overview, followed by demos of the following:

YouTube Direct is an open source, user-generated content video submission and moderation platform.
Storyful was founded by journalists to discover the smartest conversations about world events and raise up the authentic voices on the big stories.
Storify lets users make stories using social media. With Storify you can drag-and-drop tweets, YouTube videos, Flickr images, Facebook updates, etc. and add your own narrative to tell a story.
Shortform is a new social entertainment medium, delivering continuous channels containing the best videos from anywhere on the web, curated by our community of video DJs (VJs).
GoAnimate was founded to provide an outlet for everyone's creative ideas. In just 10 minutes, you can make fun animated videos without having to draw.
Link TV recently launched Link News, an international news website that sifts through YouTube's library of news content to deliver breaking news and hidden stories to a wider audience.

We would like to share the video recording of the event with you so that you can learn more. If you want to discover more about Hacks/Hackers, you can find the list of local chapters here.

Cheers,
—Jarek Wilkiewicz, YouTube API Team

Getting 3D Content on YouTube

Jarek Wilkiewicz — Fri, 09 Sep 2011 05:47:00 +0000

Over the last few months, we've been steadily rolling out features for YouTube 3D. Early this year, we announced support for the LG Optimus 3D and NVIDIA 3D Vision, and this month we announced support for Samsung 3D TVs. And we'll keep rolling out to more platforms to make it easier for everyone to get access to user-generated 3D content.

Many readers have been asking how to upload content. 3D uploads to YouTube will work across all supported devices, from red/blue glasses to the latest 3D televisions.

There are two ways to upload content to YouTube in 3D. If you're just uploading one or two videos, upload content in any supported format and then edit the video settings to tell us that it's 3D. From a video's watch page, select "edit info", then "3D Video". This will only work on videos you've uploaded yourself.

If you're using the API to upload 3D videos, you'll want to format your video in a certain way. YouTube supports automatic detection of 3D content with certain file formats. If you upload with a format that supports automatic detection, we'll automatically set the correct settings so that your video shows up automatically in 3D and shows up properly on phones, TVs, and PCs.

In both cases, YouTube requires that content be uploaded in Side by Side L/R with each frame squashed 50% and preferably with a 16:9 aspect ratio. The following formats are automatically detected when uploaded:

WebM with the StereoMode setting set to STEREOMODE_TYPE_LEFT_RIGHT.Note that other modes, including alternate track, are not supported.
H264 AVC with Supplementary Enhancement Information, Frame Packing Arrangement set.If you are using x264, the argument --frame-packing=3 will set this correctly. In Handbrake you can set this in "x264 Advanced Option String".

Be sure to get the squashing and positioning exactly correct. 3D content won't look right if video formatting is off by even a pixel or two.

We're excited to see what you'll show us! Here's an idea from a favorite webcomic of ours.

Cheers,

—Jonathan Huang, YouTube 3D Product Manager

P.S.—We recently worked with some folks to help them get 3D Mars footage from 1979 restored from the Viking landers. Check it out!

YouTube @ Google I/O: Your Game + YouTube = Instant Community

Jarek Wilkiewicz — Thu, 28 Jul 2011 20:01:00 +0000

If you have ever wondered how to generate excitement around your video game using YouTube, we would like to share a few hints from the makers of Call of Duty: Black Ops. They included the ability to upload gameplay video clips directly from the game to YouTube using the YouTube upload APIs. This fourth, and final installment of Google I/O 2011 session videos covers a game-focused presentation entitled “Your Game + YouTube = Instant Community” by Jarek Wilkiewicz from the YouTube Developer Relations team, Doug Muir, Technical Director from Activision, Cliff Samaniego and Kenji Arai from the YouTube Strategic Partner Management team.

The presentation gives an overview of YouTube platform features relevant to the gaming audience and highlights the benefits that integrating gameplay video uploads can bring into your title. The session also covers the good, the bad and the ugly of the integration project that Black Ops team had undertaken on a compressed timeframe. Finally, we show a couple of examples of user-generated gameplay video clips from Blacks Ops.

Since hindsight is 20/20, especially as it relates to software projects, the presentation also features a small demo of OAuth 2.0 for Devices authorization flow. OAuth 2.0 for Devices streamlines authorization process for embedded devices such as gaming consoles. While the technology was not yet released at the time of Activision’s integration, it is now in Beta. Another example of technology not initially introduced in the integration is WebM/VP8 encoding. If you watch the video you will learn about why the video clips were restricted in size and how WebM helps with solving this issue.

The full video of the session is embedded below, and you can find the slides here.

Cheers,

—Jarek Wilkiewicz, YouTube API Team

Man vs. Machine: Curating with YouTube APIs

Jarek Wilkiewicz — Mon, 04 Apr 2011 19:19:00 +0000

If you are reading this, chances are you are building an app which includes video. Given that over 35 hours of video is uploaded to YouTube every minute, finding the best of it can be challenging. In this post we’ll discuss some interesting approaches and illustrate them with applications recently submitted to our YouTube API Project Gallery.

Use the feed

To get started quickly, API developers will find that using standard feeds is a great way to find content. In case you have not noticed, we have added two new experimental feeds: “most shared” and “trending videos”. They provide more of a real-time pulse of YouTube and expose some of the functionality behind YouTube Trends so that it can be accessed programmatically.

Storytelling apps

While standard feeds provide a convenient mechanism, content curation around common narratives calls for more complex apps. Let’s take a look at a few examples. Storify [1] and Memolane are two interesting applications addressing different aspects of creating a social media narrative around a story (the former) or chronologically-organized series of life experiences (the latter). History of Jazz is a good example of a mobile app using YouTube built around the concept of curation. The application uses iOS video playback techniques described in our earlier blog post on the topic and is a great learning tool for those of us who like to discover new music. Shortform is a curation platform for video DJs (VJs), where users can organize interesting content for their viewers to enjoy across a wide range of topics. And yes, you too can be a VJ!

Searching for a deeper meaning with semantic analysis

The apps presented in the previous section focus on empowering users to organize content. Another approach worth highlighting is a hybrid of curator’s selections and related content recommended by an algorithm. To achieve this, ViewChange.org by LinkTV, a non-profit committed to improving the world with storytelling, utilizes semantic analysis. As shown in the screen shot below, top-level categories are decided upon (or “bootstrapped”) by curators, however, while navigating the site users are presented with automated recommendations as well.

ViewChange.org

Wow, how did they do that?

To learn more about these applications, check out the project gallery. Additionally, some of these developers made more information available about their API experience so we’d like to take this opportunity to highlight it as well. Memolane put together a blog post about their usage of YouTube API, which you can read here . Shortform also blogged about their use case; follow this link to learn more. If you would like to understand how ViewChange integrated semantic processing in their video site, you can find their blog post about the topic here.

As always, if you have an interesting YouTube API project you would like to share with the developer community, please submit it to the gallery. We would love to hear from you.

Cheers,

—Jarek Wilkiewicz, YouTube API Team

[1] At the time of this writing Storify was still in Beta, but we have arranged for a special invite code for our readers. Use youtubeapirocks and you’ll be able to create your own stories.

Introducing JavaScript Player API for iframe embeds

Jarek Wilkiewicz — Fri, 21 Jan 2011 00:59:00 +0000

If you have been enjoying our embed announced back in July we have some good news for you. Starting today, the embed code is the default way to share videos on YouTube.com. We are also introducing an initial beta version of the embed JavaScript Player API, making it a viable alternative for developers who previously used the API exposed by the ActionScript players. Let’s look at an example of the API usage:

This example will play a video for several seconds and then stop playback. An instance of YT.Player is used to control the player, defined by script loaded from http://www.youtube.com/player_api . For more information about the API usage, as always, please consult our Player API documentation and let us know what you think on our Developer Forum.

Cheers,
-Jarek Wilkiewicz, on behalf of the YouTube Player Team

Introducing JavaScript Player API for iframe embeds

Jarek Wilkiewicz — Fri, 21 Jan 2011 00:59:00 +0000

Resources for Mobile Development with YouTube

Jarek Wilkiewicz — Fri, 24 Sep 2010 22:02:00 +0000

The importance of mobile applications in our day-to-day lives continues to grow. We can now do so many things with our phones that would have been impossible not too long ago. While watching videos on mobile devices has been popular for quite some time, mobile uploads to YouTube grew by 160% last year. Mobile application developers can take advantage of this growth by incorporating different types of functionality. Many interesting YouTube projects combine video capture, uploading, sharing and playback, with application logic executing both on the mobile device and in the cloud. With that in mind, we've compiled this article to help developers quickly get up to speed on what is involved in building one, please let us know what you think!

Update: article translations are now available in Chinese, Japanese, Korean, Portugese, Russian and Spanish ! Here are the links :

Thanks,

-Jarek Wilkiewicz, YouTube API Team