Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Building Chromecast Apps

Building Chromecast Apps

Maxwell Da Silva, video architect, covered the entire Chromecast application workflow, including registering your app and developing, debugging, and publishing it. Attendees find out how the Chromecast user model works and learn more about the design principles of the platform. Get insights into the sender and receiver technology, which displays the content and metadata, and the mobile device or laptop, which controls the playback. Finally, using HTML5 and JavaScript, attendees see how easy it is to build a simple video player and, using Chromecast SDK, filing the content to receiver.

(Presented at Streaming Media West 2014.)

The New York Times Developers

November 18, 2014
Tweet

More Decks by The New York Times Developers

Other Decks in Technology

Transcript

  1. What platform do I use to develop my apps? •

    iOS • Android • Chrome In order to publish an application, you need to subscribe to Chromecast. There’s a $5 fee.
  2. Design apps for Chromecast • Your app is the remote

    • Cross platform => (Design your app to be easy to use) • Second screen experience • Connect and Play or Play and Connect • Don’t make your UI on TV look interactive
  3. What is a Receiver app? It’s an application written in

    Javascript/HTML/CSS that runs on the receiver (Chromecast)
  4. Styled Media Receiver It’s a pre-built app hosted by Google

    that was built to playback audio or video content. You can provide a CSS file to customize the appearance of your app.
  5. Styled Media Receiver You can define a background style for

    your application: .background { background: #000000; }
  6. Styled Media Receiver You can add your logo: .logo {

    background-image: url(timesvideo_logo.png); }
  7. Styled Media Receiver You can add an transparent watermark image:

    .watermark { background-image: url(times_watermark.png); background-size: 57px 61px; opacity: 0.5; }
  8. Styled Media Receiver You can also define a splash image:

    .splash { background-image: url(splash.png); }
  9. Custom Receiver: Why? • Build a second screen game •

    Video application that require DRM • Image gallery, Audio gallery • All kinds of second screen experience
  10. Supported media types Video Codecs: H.264, VP8 Audio Codecs: MP3,

    HE/LC-AAC, Vorbis, WAV Subtitles: WebVTT, TTML, CEA608 DRM: PlayReady, Widevine Adaptive Streaming: HLS, DASH, Smooth Streaming
  11. Receiver limitations • Limited memory/CPU power • Single concurrent playback

    experience • No video compositions or manipulation such as, zooming or rotation.