Date: February 3, 2016 Author: Henry Lee

The JW Mobile team is excited to bring you our latest update to the JW Player Mobile SDKs. Version 2.1 of the JW Player SDK for iOS now uses Apple’s AVPlayer as it’s native media playback engine. Not only does this give iOS developers some valuable features right out of the gate, but this will speed up the JW Mobile team’s delivery of future HLS updates & iOS features.

Both our iOS and Android SDKs now support ID3 timed metadata, a frequently requested feature that will provide developers more power and flexibility to build functionality on top of HLS live streams.

Read on for more details!


Read more

No comments

Date: January 27, 2016 Author: Allison Stone

JW Player Account Properties Settings

The JW Player Dashboard team has just released a set of advanced Account settings that now allow agencies or enterprises with multiple divisions to segment their content, players, and analytics into multiple “Properties” in the dashboard.  By adding Properties to an account, you can now consolidate billing, while slicing reporting of analytics for different publications, applications, or websites.  Conveniently, Usage data (including plays, ad impressions, and storage volumes) is viewable on the per-property basis and can be rolled up for the entire account.  Important account settings such as DNS masking and content protection are settable on the Property level and certainly may be different across Properties.  Your platform API keys are also unique to each Property, and can be found on the property detail page in the dashboard.  
Read more

No comments

Date: December 15, 2015 Author: Rohit Garg

Screen Shot 2015-12-11 at 3.51.19 PM

Over half a billion videos are watched on JW Player video player every day resulting in about 7 billion events a day which generates approximately 1.5 to 2 terabytes of compressed data every day. We, in the data team here at JW Player, have built various batch and real time pipelines to crunch this data in order to provide analytics to our customers. For more details about our infrastructure, you can look at JW at Scale and Fast String Matching. In this post, I am going to discuss how we got Hive with Tez running in our batch processing pipelines. Read more

No comments

Date: November 19, 2015 Author: Andrew Prelusky

We’ve been hard at work on JW 7.2 for the past few months. We’ve crushed quite a few bugs and gotten a lot of your feedback via our beta testing program. (Check our release notes for full details!) Today, we’re happy to announce that 7.2 is publicly available for all. This blog post explores its new features and improvements.
Read more


Date: November 18, 2015 Author: Danny Finkelstein

The major challenge with automated integration testing for a web player via browser automation tools is that these tools better serve the purposes of web applications such as e-commerce sites, single page applications, and social networks. How do you take a product like JW Player which is embedded on over 2 million websites where publishers are always coming up with unique ways to use the player, and build an automated testing framework that will ensure the quality of that player? I would like to walk through how we’ve taken on that challenge.

Read more


Date: November 17, 2015 Author: Paul Mandal, Rik Heijdens & Henry Lee, JW Mobile Mavens

Today we are releasing a major update to our JW Player SDK for Android. We completely rewrote the SDK to make it easier than ever for developers to add world-class media playback to any Android app. (Don’t worry though–we’ve provided detailed documentation of the API changes and code examples, so upgrading to 2.0 is a breeze.)


2.0 also marks a significant step toward our goal of “One JW Player.” One JW Player is a hybrid software design that we created while developing our JW Player SDK for iOS earlier this year. The developer-facing APIs in the SDK are native to the target platform, but they are wrappers around our flagship JW Player 7 JavaScript/HTML5 library (jwplayer.js). The core functionality of the SDK (player customization, captions, analytics, etc.) is powered by JavaScript, but all the developer-facing APIs in the SDK are native classes (Java, in the case of Android).


Here’s a diagram to illustrate:

Read more


Date: October 29, 2015 Author: Max Mikheyenko


This week, Apple started taking pre-orders for the new Apple TV. Previously, the devices had only been available to developers.

Shortly after the Apple TV announcement in September, I received my developer device from Apple. Like most people, I have been very impressed with the device and development environment, but have found some crucial functionality missing from the new tvOS. But more on that in a minute.

Read more

No comments

Date: October 15, 2015 Author: Brian Rifkin

Let’s get down to business: We know what it takes to excel with Google publishing solutions

As one of Google’s Certified Publishing Partners, JW Player can help your business thrive. Google selected us for this program based on our proven expertise in DoubleClick AdExchange and DoubleClick for Publishers Small Business. We’ll help you monetize your sites — and earn as much as possible from every ad impression — as we work with you to provide a great video ad experience.

Read more

No comments

Date: October 12, 2015 Author: Monica Parra



With the release of JW7, we had an exciting opportunity to leverage our new skinning model for a new skin design as well as to reassess the user experience of the player overall. Here I’ll recap the creative process that led to the new “seven” skin and what’s next for the design of the player in our upcoming releases.

Read more

No comments

Date: October 7, 2015 Author: Andrew Prelusky

There has been much ado in the news lately about Chrome and its active pausing of smaller Flash-based content. A recent post regarding this behavior was published when our VPAID 2.0 support was launched. We’re now happy to report that our latest release, JW Player 7.1.4, goes a step further. We’re now able to provide a better experience for viewers by intelligently reacting to Chrome’s Flash throttling.

Read more