Quick Brick TV Apps - Configure Auto Play Next Item

Play Next for TV

Introduction

The Play Next feature for TV Quick Brick apps is enabled by using the Play Next Plugin. This plugin is of a new type called player_overlay that at a general level is used to interrupt the player flow and present UI and actions over the top of a playing video. When the plug is active context is passed to the plugin (current item + full feed) and the plugin is responsible for presenting the next video.

Support:

• Android TV (SDK 0.1.0 and above)
• tvOS (SDK 10.1.0 and above0
• Samsung TV (SDK 1.0.0 and above)
• LG TV (SDK 1.0.0 and above)

Play Next user experience

The user experience flow is:

• A video is playing
• At a configurable time measured from either the start or before the end of that video an overlay with the next video in the DSP will render on screen with a countdown timer
  • SUPPORTED FORMAT: m3u8, mp3 
• The plugin takes control of the player until the player is closed down by a user exit action
• If there is no exit action by the user the next item will automatically play after the countdown
• The user can exit from the player to the UI with the device BACK function at any time

Plugin configuration

Add the "QuickBrick Play Next Overlay" plugin (use latest version):

Plugin Settings -

The following settings are configured in the plugin level:

Trigger configuration

• trigger point (OnEnd / OnStart)
• Define whether the trigger for the interrupt to the player is measured from the end or start of the video. For play next this is going to be ‘On end’
• duration (Seconds)
• The length of the time from end or start of the current video that the trigger will occur (allowed values from 0s)
• autoplay (if trigger is start)
• Disable if you don't want the content to continue playing whilst the overlay is being displayed. 
  • If set as Disabled, the "autoplay" can serve as an "alternative" banner.

 

Overlay UI configuration

The UI of the Play Next overlay can be configured with the following parameters via the plugin

This is the "Next up in 5..." message that comes from the DSP Font and colour (*1) Key= play_next_header	Font: System Font, ExtraBold,  Colour: Default 30pt rgba(239,239,239,1)
This is the Title sourced from the DSP Font and colour (*1) Key= text_label_1	Font: System Font, Bold,  Colour: Default 26pt, rgba(239,239,239,1)
This is the Subtitle sourced from the DSP Font and colour (*1) Key= text_label_2	Font: System Font, Medium,  Colour: Default 24pt, rgba(239,239,239,1)
This is the "press Back to exit" message. It is Hardcoded in the DSP Font and colour (*1) Key= message_text_label	Font: System Font, Bold,  Colour: Default 28pt, rgba(239,239,239,0.8)
This Overlay Asset is an image that can fill the screen over the video. Usually a semi-transparent and graduated background over the player Overlay Asset (*2) Key= overlay_asset	Asset: Overlay TV Type: png 1920x180

*Note:

• *1 - Notice that while the Font Type is Hardcoded, the Size and Colour can be changed
• *2- This is an image that can fill the screen over the video. Usually a semi-transparent and graduated background over the player
• The next item image, title and subtitle come from the DSP.

DSP configuration

In the DSP feed that you wish to be the source of your play next videos add the following extensions.

URL_string for source of feed and the trigger timestamp in seconds

  extensions: {

    play_next_feed_url: string,

    overlay_trigger_timestamp: ?Number // in seconds

  }

};

Analytics:

Analytics will register as a standard player event for live and VOD content but you won’t know it is tied to a play next event  (ie: Play VOD / Play Channel)