DP to SceneGraph wizard tool released
I've created a wizard tool that should alleviate some of the anxiety of converting a Direct Publisher channel to a SceneGraph channel. The tool can be found on GitHub. The tool will walk you through some steps to generate BrightScript code that uses your JSON feed file to create a SceneGraph grid-style channel similar to the UI of Direct Publisher. The code supports ALL content types including Series/Episodes. However, there are some caveats: The code generated is an "alpha" version. This means it is not fully tested and may contain bugs. It should NOT be used as the basis of a production channel. Use the generated code at your own risk. The code will NOT currently pass channel certification. I plan on continuing to develop the code and thought it was important to get it into the hands of DP channel developers. The tool assumes that your feed file specifies Categories that use Tags to "bucket" your channel content. Your feed file MUST contain Category objects and Tags. I'm looking for feedback and comments on the wizard and the code that it produces. Please use GitHub to discuss, comment, and ask questions. Please do not use this forum to ask questions, or, report errors. If you find a problem, open an issue on the GitHub site. If you want to be notified of future version releases, you should "star"/watch the GitHub project repository.Shared my frustration
I'd like to share a post I've submitted to Partner Success. I don't normally rant, but, I was frustrated enough to submit the following. I'm writing to express my dissatisfaction and frustration with the lack of support for the Direct Publisher platform. Direct Publisher has the opportunity to be a great vehicle for developers to create and publish their channels. However, the past several months have highlighted numerous problems that have negatively impacted channel developers. A simple scan of the Roku DP forum will show the displeasure of several developers who have run afoul of the DP system and have experienced “back end” problems that have negatively impacted their publishing efforts. Couple that with an inconsistent support system providing misleading and often incorrect information and you have the makings of a serious problem. For example, I recently reported some inconsistencies with the Roku JSON documentation and the responses I've received from support staff. I recently noticed that the 'releaseDate' field had been removed from the Episode object. When I asked about it, I was told that the field is no longer required. When I tried to submit a new feed file, it failed because I had removed the 'releaseDate' field. I was then told it is needed. Additionally, documents on Partner Success indicate that “Trick Play thumbnails are automatically generated by Roku's firmware for Direct Publisher channel content.”. When I asked a support person to verify this I was told that, no, they are not automatically generated for DP channels. To put it bluntly, it appears that one hand of Roku does not know what the other is doing. This ultimately impacts DP developers because we cannot count on accurate information or a stable DP platform. Please correct these problems. Or at a minimum, please monitor the DP forum to head off potential problems that end up causing numerous delays for developers.
Convert Direct Publisher (DP) to SDK in 5 minutes or less!
Questions this thread will answer: Can I convert my Roku Direct Publisher channel to SDK by myself? Do I need a developer to convert my Roku channel to SDK? How to ensure seamless Roku SDK conversion from Direct Publisher? Is there a guide for converting Roku channels to SDK format? What are the best practices for Roku Direct Publisher to SDK conversion? What’s required to upgrade from Roku Direct Publisher to SDK? Converting a Roku Direct Publisher channel into a Roku SDK channel can be approached in two ways, either by developing it yourself or by opting for a streamlined done for you ROKU SDK in less than 5 minutes. Below, we’ll guide you through both methods. Method 1: Develop Your Custom Roku Channel Yourself Please note that developing a custom Roku SDK channel requires programming skills and ongoing maintenance. If you are not comfortable with coding, go to the next method “Convert your direct publisher ROKU Channel to an SDK in minutes.” Step 1: Prepare Your Development Environment Before diving in, make sure you have the necessary tools and resources: Roku Developer Account: If you have a Roku Direct Publisher channel, then you have a Roku Developer account. Roku Device: You’ll need a Roku device for testing. Text Editor or IDE: Utilize a text editor like Visual Studio Code or an Integrated Development Environment (IDE). Basic BrightScript Knowledge: Familiarize yourself with BrightScript, Roku’s scripting language for channel development. Step 2: Create a Roku SDK Application Log in to your Roku Developer account. Within the developer portal, navigate to “My Channels” and click on “Manage My Channels.” Next to your Roku Direct Publisher channel, click on “Options” and select “Convert to Roku SDK” to change the channel type. Fill out the missing information for your channel. Step 3: Develop Your Custom Roku Channel Kickstart your Roku channel development by coding in BrightScript. This encompasses creating your channel’s user interface, navigation, and functionality. Leverage the Roku SDK documentation and sample code provided by Roku to construct your custom channel. These resources are available on the Roku Developer website. Host your content, such as videos and images, on a web server. Ensure that your content URLs are accessible and adhere to Roku’s content guidelines. Step 4: Testing Your Channel To test your custom Roku SDK channel, you’ll need to sideload it onto your Roku device. Here’s how: Obtain the IP address of your Roku device, which can be found in the Roku device settings. In your channel’s development environment, use the Roku Remote Debugger to deploy your channel to your Roku device by specifying the device’s IP address. Thoroughly test your channel on your Roku device to verify that all features and content function as intended. Step 5: Package and Distribute Your Channel Once you are satisfied with your custom Roku channel, it’s time to package it for distribution. Access the Roku Developer portal, navigate to “My Channels,” and select your channel. Options for packaging your channel for different Roku models (e.g., Roku Streaming Stick, Roku TV) will be available. Follow the on-screen instructions to generate a package for your channel. This process will result in a .pkg file. Distribute your channel to your intended audience. You can either submit it to the Roku Channel Store for public distribution or employ developer mode for private distribution. Step 6: Maintain and Update Your Channel Regularly maintain and update your custom Roku SDK channel to ensure its compatibility with the latest Roku firmware. Roku frequently releases software updates, and it’s essential to remain responsive to user feedback and implement improvements as necessary. Method 2: Create your own ROKU SDK within minutes!! Step 1: Go to SDKConverter.com Step 2: Click on convert your channel Step 3: Sign up Step 4: Click Create SDK Step 5: Fill in details Step 6: Click Create SDK Step 7: Upload your SDK to ROKU! Done! In under 5 minutes you have converted your Roku Direct Publisher channel to a Roku SDK, ready for future streaming! And if you want to monetize your channel, for a one-time fee of $199, you can activate vast tags for advertising, custom banners, backgrounds, logos, etc. This method will enable monthly revenue based on ads tied to your channel! So, head on over to SDKconverter.com and create your ROKU Channel today! ****** Roku SDK Converter Convert my Roku channel to SDK Convert SDK for Roku Roku Direct Publisher to SDKVimeo users check your thumbnails
For anyone using Vimeo hosting platform, yet likely hand coding json, check your channel & thumbnails. Seems they did a changeover which gave new urls for thumbnail images, and they old ones are now defunct, displaying only color bars. I had some trouble with the new ones not always showing either, and reached out to Vimeo support. There's a thread in the regular developers section as well.
Roku channels are removed by platform, due to unable to migrated to SDK version
Hi there, Unfortunately we missed the deadline to migrate the Roku channel to SDK, now channels are removed. We have good traffic and user base, can someone help us how to bring back our removed channel and push our updated SDK version Any help would be highly appreciated. Thanks in Advance.Seeking software testers for new software tool
I am the developer of the Json Feed Manager for Direct Publisher. JFM will be sunset in the near future as it has outlived its usefulness. As such, I am in the process of releasing a new suite of FREE software tools to replace JFM. I need several testers to test the software and provide feedback. If you are interested in helping out, please reply with your interest in this dicussion post. Please do not reply on this forum.List of Third Party Direct Publisher Solutions
Many of you have seen the topic "List of Third-party Roku Channel Developers for Hire". That list is primarily for those that create channels using the Roku SDK and BrightScript. The purpose of this post is to provide a similar mechanism for those that provide solutions/software for Direct Publisher channel developers. A formal list of those that help DP developers will allow new channels to publish quicker and cut down on the learning curve. If you provide a solution, software, etc. to Direct Publisher channel developers, please add to this post what you can offer including costs, contact info, and anything else that would help a new channel developer.Is There Still a Reason to Develop Games for Roku?
Hi everyone, - With ShowChannelStoreSpringboard() now deprecated (https://blog.roku.com/developer/springboard-api-deprecation) even for promoting other apps from the same developer, - with new games not being being automatically added to the Apps/Games category (to quote Roku support: “We do not provide additional information on the factors that determine the algorithm of the order or appearance…”) and instead users have to search for games by typing their name, it’s becoming difficult to justify game development on Roku beyond pure personal interest. - On top of that, every game must be ported using BrightScript, a language unique to Roku, adding extra overhead for cross-platform developers. Is there still any real incentive for indie developers to invest time and resources into the Roku platform? I’d really appreciate any suggestions or feedback from the community. Have a great day and stay safe! Best regards, STeN
