The Design Customizing every detail of a videosite ‣ The Player Using and customizing video players ‣ The API Mash up, extend and integrate the product ‣ The Community Getting more info and keeping updated (We'll do the nitty-gritty details and end off each part with plenty of examples and an overview of our roadmap.) The developer introduction to the product– or merely 23 Video for geeks… AGENDA
http://film.hjv.dk ‣ Ecommerce Unisport | http://webtv.unisport.dk ‣ Ecommerce Unisport | http://webtv.unisport.dk ‣ Archive Byen I Byen| http://byenibyen.frederiksberg.dk ‣ Internal sharing (No links, unfortunately) ‣ Events TedX | http://video.tedxcopenhagen.dk ‣ Media Bilmagasinet | http://www.bilmagasinettv.dk ‣ Campaigns Carlsberg Sport | http://tv.carlsbergsport.dk ‣ Video section The Royal Danish Theater | http://video.kglteater.dk Some examples of how people are using 23 Video
with automatic search integration. ‣Internationalize content by adding captions and subtitles. ‣Also a beginning requirement in public sector project to ensure accessibility. ‣Support for current subtitle formats, but build for html5 around WebSRT ROADMAP
and quick delivery of bytes. ‣Built-in content delivery network, but not just for video. ‣Handles all the asset of a videosite including the custom design elements and resources. ‣Currently in 5 locations around the world, covering 3 continents. ‣Expanding with more nodes. ROADMAP
per day. SQL and traditional RDBMS systems become a bottleneck. ‣Building next version adding in new variables such as user sessions, geography, screen size, content source and player events. ‣Dedicated service with scalable routines to handle the data. ‣On Air: Live data view as reporting immediately when visitors are playing your clips. ROADMAP
site: “the layout block” ‣A generic container for information ‣Positioned anywhere within the layout grid ‣A wide variety of blocks available About the site Channel list Comments form Contextual video player Download videos Footer HTML Block Import HTML from URL Link to login Links to pages List of comments Menu Name and logo New videos Open upload Play list Popular videos Rate object Search box Sections Share Subscribe Tag cloud Users Video overview Video thumbnails Web analytics THE DESIGN DNA
requiring multiple sites with same layout ‣Let users pick and choose specific data types ‣Colors ‣Graphics ‣Fonts ‣Text ‣A custom value (justification, inset etc.) GOING ADVANCED
configs as needed ‣ A configuration can both change the SWF file behind the player and the settings for displaying ‣ One player is default and can be changed at any time. This player is used for the video site. ‣ Other player configs can be use by admin from the backend. ‣ Configs are loaded dynamically, so embed codes won't change when a configuration does Setting up players and embedding
isn't available to handle the video playback. Here, we fall back automatically to html5. Currently, we'll be using the browser's standard player design for the video; but this is changing. With the transition of styling to Liquid and control of all html, we want to use the same templating model for customizing the html5 player. Cross-browser support mixing WebM and H.264 files: Safari 5, Chrome, Firefox 4, Opera 10, Internet Explorer 9. If you embed correctly, html5 is supported out of the box – including on mobile devices.
&tag=demodemo "/> WHAT TO SHOW IN THE PLAYER? flashvars=" backgroundColor=yellow &showTray=0 &autoPlay=1 &start=120 "/> HOW TO SHOW THE PLAYER? (explicitly overrides the config for the player) * http://www.23developer.com/design/player-embed has a full list of options. // Which video should be played? // If the video is unpublished, a secret token is needed // Which channel to include videos from? // Which tag to include video from? // Make sure the player background is yellow // Don't show the player controls in the tray // Start playing immediately on load // And start the video 2 minutes in
be hacked $ git clone git://github.com/23/videoplayer.git VideoPlayer Initialized empty Git repository in VideoPlayer/.git/ $ cd VideoPlayer $ git branch MyPlayer $ git checkout MyPlayer Switched to branch "MyPlayer" $ git branch * MyPlayer master * You can get the code https://github.com/23/videoplayer and http://www.23developer.com/design/player-build goes into details
23 Video standard players, but: Custom players are just SWF files reading the embed and using the API … and you can create a really custom player simply by uploading a SWF. But I want to build my own player…
you don't want to – since the player is just an ordinary API consumer. ‣Read in embed parameters Which videos from which domain has been requested? ‣Get videos through the API Ask for detailed information about the videos to be played with /api/photo/list ‣Support sections+subtitles? Requires further requests to /api/photo/subtitle/list and /api/photo/section/list ‣Report back to analytics Make sure your custom player is sending information back to our analytics api. Will usually reuse the 23 analytics component. … and still enough control to do whatever you want
allow yourself to be kept up- to-date $ git fetch origin $ git merge master Merge made by recursive. * If you make sure to keep the git repository intact when you download the source code, you can always retrieve and merge in new additions and features from the player automatically.
? document[appName] : window[appName]); } Event.observe(window, 'load', function({ getFlexApp(playerName).play(); }); * You can find a list of all available methods for this kind of interaction at http://www.23developer.com/design/player- javascript START PLAYING ON LOAD
? document[appName] : window[appName]); } function playVideoFromSecond(sec, playerName){ playerName = playerName||'videoplayer'; var v = getFlexApp(playerName); if (v) { var state = v.getPlayState(); v.playVideo(); window.setTimeout(function(){v.setPlayheadTime(sec);}, (state==='playing' ? 0 : 1000)); return(false); } else { return(true); } }; Event.observe(window, 'load', function({ playVideoFromSecond(65); }); JUMP TO A SPECIFIC TIME IN THE PLAYER
now. ‣This week we're switching to Flash Builder 4 as the supported platform. ‣In this release, we'll also have support for Sections & Subtitles. ROADMAP
‣Methods available under http://domain.tld/api/... ‣Responses available in common formats ‣XML ‣JSON ‣All documentation available on http://www.23developer.com/api/ COMMUNICATION
‣Anonymous access ‣Methods are categorized in six levels of access ‣none – just go ahead, we don’t care who you are! ‣anonymous – you’re allowed, if you have basic access ‣read – read access to the API ‣write – read and write access to the API ‣admin – access to all but critical API calls ‣super – full access to the API AUTHENTICATION
SHA1 signature signing ‣Loads of great libraries ‣Signing requires tokens for an application ‣Consumer key and consumer secret ‣Access token and access token secret AUTHENTICATION
the tag “23video” in JSON http://sample.23video.com/api/photo/list?tag=23video&size=20&orderby=created &order=desc&format=json ‣Breakdown ‣/api/photo/list – the API method ‣tag=23video – the tag we want ‣size=20 – the number of videos we want listed ‣orderby=created – the sorting mechanism used for selecting videos ‣order=desc – descending sorting ‣format=json – we want the response in JSON USING THE API
THE API Get token Method: /api/session/get-token Returns: access token Permission level: super Redirect the user Method: /api/session/redeem-token Returns: signs the end user in and redirects them to a desired URL Permission level: none … and the user is in!
USING THE API Get token for upload Method: /api/photo/get-upload-token Returns: upload token that can be used for uploading Permission level: write Post the upload with the token Method: /api/photo/redeem-upload-token Returns: accepts the upload and returns the user to a specified URL Permission level: none Viola! Present the user to an upload form Style and create an upload form as you need.
usage ‣Most new functionality will be exposed through the API ‣Sections and subtitles are newly additions ‣Development is developer driven – your input matters ROADMAP
in C# 3.5 ‣ Official implementations We have an official implementation for signing sessions as a Microsoft SharePoint Webpart ‣ Sample code Using something else? No problem! We have sample code for both PHP and Ruby readily available for you to use Libraries, samples and implementations
design on a 23 Video site, how to design it and how to build players. ‣ API documentation All the information about accessing and using the API, including sample scripts and libraries. ‣ Github Open sourced code from 23, including the video player, libraries and sample code. ‣ Forums/Community Asked and answered question for developers. Resources for getting more information, code examples, modules and more