New certification checklist

No.
But if you insist.. 🙂

how about updating a package file for an existing channel

the new package file would have to pass the new checklist criteria in order to be published??

That's how it's usually done. Apple does that all the time for apps, like mandating support of certain versions of iOS/ARM/XCode/IPv6...
Old content is "grandfathered", new one (incl. updates) has to pass muster.

Note there is no strict requirement to satisfy the full list and there are priority levels or some such. Missing some is inexcusable, while others are just desirable. Of course if one satisfies 100% of them, can feel fairly certain there will be no delays in publishing...

yeah-- makes sense that the checklist would be applied to pkg updates

but now deep linking is a priority 1
this doesn't seem practical in all instances


for instance I have a small channel-- paid to subscribe to all content
content is less then 20 instructional videos
labeled lesson 1, lesson 2, lesson 3 etc

so to update my pkg file

i would need to recode my entire channel
to support deep linking
open a private channel to submit my channel content for roku search

and restructure my lessons so that they are no longer labeled lesson 1, lesson2, etc...
otherwise people would have to search for "lesson 1" to get my episode in the search results..


===========================================

I am not sure how "search" works on a roku device
my device has never had the search option available
even after having to reset the device to factory settings multiple times
--- if I do not access the dev through my device ip for about 2 weeks-- my device becomes reachable-
--- the only way I can access the dev features again is to reset the device and rekey it...


but i would think that deep linking on a smaller channel like the one i described above is not so practical

the name of the channel -- is basically the topic of the channel

if the search results returned the channel itself- rather then episodes
then that would be enough

I would not expect anyone to search for "lesson 1"

and if they did search for "lesson 1"
i doubt the search results would be anything practical to the user...

franklinf -
that's only if you support deep linking and participate in the Roku "unified search" program. If you don't - never mind, section 10 does not apply to you, nothing to see here - move along :). I just had a glance and admittedly, it's written rather unclear "between the lines", that part. Whoever wrote it has lost sight of the forrest for the trees.

I imagine it's a "great honor" and fuss to get included in the unified search and naturally in that case the deep-linking would have to be in tip-top shape. Mind you, search would bring lots of traffic so if one enrolls, they are unlikely to complain deep-linking should work

"EnTerr" wrote:
Admittedly, it's written rather unclear "between the lines", that part.

Especially when read in conjunction with this statement on the Roku Developer Blog under Checklist Requirement Updates/Deep Linking:

All channels on the Roku platform must support deep linking.

That post does go on to reference another blog post that states:

all Roku channels with indexed content are required to respond to deep link requests

although I haven't seen their definition of what constitutes "indexed content".

yes this is really confusing


it makes sense for only channels indexed for unified search to be required to support deep linking

but the recent post in the dev blog does state:

All channels on the Roku platform must support deep linking.

hopefully we can get someone from ROKU to clarify....

I think "tcharles" blogger is confused - but don't take my word for it, since my name does not start with "Roku".
Let's hear from the Co... RokuJoel, perhaps?

I am also amused by the claim that apps have to work on *all* supported models. If that were the case, 65 out of 130 games - poof! - out the window. Ha! I have a math problem: "how many times does one have to decimate the Games category to lose half of the games?"
(hint: decimate = "kill one in every ten of a group")

On a side note, it's cute to see the product codenames published. I have seen them leaked here and there - but now there is a table.

this is the confusing part--

if you read the checklist
section 10 -- deep linking
has the (when available) after each item
leading you to conclude that if this option is not available then it is ok

but on the blog post about the new guidelines:



they have in bold that
All Channels must support deep linking

and then clarified for other changes under the other items
All Paid Channels -- for channels that must use the Roku Billing Agreement
and All Advertising Supported Channels -- for channels that must use the RAF



Hopefully Roku Staff can clarify...
if ALL CHANNELS need deep linking enabled
or ONLY CHANNELS that will have the roku global search enabled and submitted need deep linking

Franklin

Since there has been no clarification on this issue and I really need to push an update (company logo change... nothing but images), I decided to go head and submit it.

Not completely sure if by checking the box saying I've "read and agree to the terms of..." was completely honest though since I don't fully understand what those terms are, very specifically in this deep linking issue.

AFAIK, my app supports deep linking if launched with the correct arguments since no one would know what those arguments should be!

I will post an update if/when I get some sort of response

edit:
EnTerr, yes that was me that posted on the blog site

edit2:
No "@" mentions? I'm too spoiled by github I guess