Skip to content

rokudev/deep-Linking-samples

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 

Repository files navigation

Deep Linking

Overview

This sample demonstrates how to launch content with deep links. It provides video content items that you can use to test deep linking via cURL commands and the External Control Protocol (ECP). It also shows you how you can design your application to deep link into content when both launching a channel and while the channel is already running.

Components

The FeedParser component retrieves the video content items used in this sample from an XML feed and then indexes and transforms them into ContentNodes so they can be displayed in BrightScript components. This process is useful if you do not have a web service for pulling content IDs from your feed (for example, your feed is maintained in an Amazon S3 bucket).

Specifically, the FeedParser component stores the stream URLs and other meta data for each content item in the feed in an array of associative arrays. The captured meta data includes a thumbnail image (used for the channel's poster and background images), description, and title. Importantly, it stores the items' GUIDs as content IDs and links them to the metadata. This enables you to pass the GUIDs in ECP cURL commands and deep link into the associated content. To display the content items on the screen, it formats the items into ContentNodes and then populates them in a RowItem.

The HomeScene component creates the scene used by the sample (a RowItem with four rows of Posters displaying the content's thumbnails), and it plays the video content item linked to the deep link it receives. The module contains an observer that listens for when a deep link is received. Upon receiving one, it validates the stream URL, content ID, and media type, and then launches the channel and plays the video specified by the content ID in the deep link.

The InputTask component listens for roInputEvent events to check whether a deep link has been received while the channel is already running. When one is received, it updates a global variable being monitored by the HomeScene module, which cues and plays the specified content.

Installation

To run this sample, follow these steps:

  1. Download and then extract the sample.

  2. In the extracted DeepLinkingSamples-master folder, expand the Basic_DeepLink_roInput_Sample folder. Compress the contents in this folder to a ZIP file.

  3. Follow the steps in Loading and Running Your Application to enable developer mode on your device and sideload the ZIP file containing the sample onto it.

  4. Optionally, you can launch the sample channel via the device UI to view the scene and video content items. The sample channel is named FirstApp (dev).

  5. Run the following cURL commands to test deep linking into the video content items n your development channel via ECP POST requests:

  • Deep linking upon channel launch: curl -d '' 'http://<Roku Device IP Address>:8060/launch/dev? contentID=2c4e8ea1ad2f4a8d9d244f5dd4cc47b6&mediaType=movie'

  • Deep linking while channel is running: curl -d '' 'http://<Roku Device IP Address>:8060/input? contentID=2c4e8ea1ad2f4a8d9d244f5dd4cc47b6&mediaType=movie'

    When testing deep links on your production channel, replace "dev" with your channel ID. The syntax to use is therefore: curl -d '' 'http://<Roku Device IP Address>:8060/<command>/<channelId>?contentID=<contentIdValue>&mediaType=<mediaTypeValue>'

  1. You can go to the feed URL used in this sample to view the content IDs that you can pass into the ECP commands. Alternatively, you can launch the sample channel and use the developer console to view a list of the content IDs. For convenience, a few of the content IDs are provided:
  • Twitch. 2c4e8ea1ad2f4a8d9d244f5dd4cc47b6
  • Paula Dean. 6c9d0951d6d74229afe4adf972b278dd
  • TED. 7405a8c101ee4c9da312c426e6067044

About

Sample apps demonstrating Deep Linking and roInput Messaging

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published