In October 2015, Roku introduced our new user interface programming API, Roku SceneGraph (RSG). Since then we’ve seen great adoption from our developer community, leveraging the framework’s ability to build beautiful, custom-designed channels.
In order to modernize the Roku experience, we will be ending support for the visual screen components that were part of our legacy SDK On January 1, 2019, these visual screen components will be removed from Roku OS. Developers who wish to remain on the Roku platform are asked to update their channel UI using SceneGraph.
There is a two-year roadmap for developers to transition to RSG. Below are key dates:
- Effective immediately: No new features will be added to our legacy SDK visual screens
- July 1, 2017: All new channels must use RSG or Direct Publisher
- January 1, 2018: All channel updates must use RSG or Direct Publisher
- January 1, 2019: Legacy visual screen components will be removed from Roku OS
What’s going away?
Below is a complete list of the legacy SDK visual screen and associated event components that will be deprecated. By removing these components from your app, you will ensure your channel is unaffected by the deprecation process.
To be clear, only the visual components of our old SDK will be deprecated. The 2D APIs will persist for use in gaming channels and other similar uses.
How to transition?
There are a variety of ways to update your channel to RSG.
Roku Direct Publisher
Roku Direct Publisher provides the fastest option for updating your channel. To convert your channel using Direct Publisher, you’ll first need to create a content feed that accords with the Direct Publisher specifications. You can either configure the feed yourself, or work with one of our preferred Direct Publisher feed partners.
Channels built using Direct Publisher are automatically kept up-to-date with the latest feature updates to Roku OS. Read the complete list of benefits for Direct Publisher channels.
Follow the SDK1 to SceneGraph migration guide
Many channels built using legacy SDK followed our “VideoPlayer” template channel. As such, we’ve built a SceneGraph template that mirrors the VideoPlayer template’s UI and functionality. By swapping your image locations, making some changes to the Manifest, and properly fetching your feed, you can quickly convert your channel to RSG.
Redesign your channel in SceneGraph
SceneGraph offers many opportunities for custom design. Developers can drive engagement and provide a brand refresh by redesigning their channel UI in SceneGraph. For an overview of the key concepts of how to build an RSG channel, see our SDK Development Guide.
For professional help building a Roku channel, consider engaging with a development shop on our recommended developer list. See the “Additional resources” section below for smaller contractors with reviews on Upwork.
- Direct Publisher overview: developer.roku.com/publish
- Direct Publisher feed specifications: github.com/rokudev/feed-specifications
- Recommended Direct Publisher feed partners: roku.box.com/v/roku-feed-partners
- SDK1 to SceneGraph migration guide: github.com/rokudev/videoplayer-channel
- SDK Development Guide: developer.roku.com/develop/sdk-development-guide/sdk-guide-index
- Roku SDK documentation: sdkdocs.roku.com/display/sdkdoc/Roku+SDK+Documentation
- Roku Developers GitHub page: github.com/rokudev
- Recommended SceneGraph developers: roku.box.com/v/channel-developer-list
- Roku freelance developers on Upwork: upwork.com/o/profiles/browse/?q=roku
- BrightScript freelance developers on Upwork: upwork.com/o/profiles/browse/?q=brightscript