"yogamerge" wrote:
So let's say my current channel is version 1.0 and runs on legacy devices, when I update it I will just have to submit a package with minimum firmware that excludes legacy devices as version 2.0?
I suspect, once this goes into effect, it won't matter what you set the minimum firmware to. Roku will be blocking the updates at that point, so you shouldn't need to enforce it yourself.
"yogamerge" wrote:
The below statement makes it sound like if your current channel runs on legacy devices that after May 30th, you will no longer be able to issue updates or a firmware update, but using your logic, you could as long as it was as a new version excluding legacy devices?
"...we will no longer launch new channels, update existing channels, issue firmware updates or provide developer support for channels that run on these older devices."
They just mean you won't be able to explicitly target legacy devices anymore, and any end user who has a legacy device will no longer receive any updates for it. Any channel that runs on a legacy device will also run on a current generation device, so there's no way they'd block channels just because they're compatible with legacy devices. They just won't make them available to the legacy devices anymore.
Ultimately, they just don't want you wasting your time trying to make your channel compatible, which has become increasingly more tedious over the past couple of years. Dropping legacy device support, while it probably alienates a small subset of their current users, is a good thing for developers.
My Channels: http://roku.permanence.com - Twitter: @TheEndlessDev
Instant Watch Browser (NetflixIWB), Aquarium Screensaver (AQUARIUM), Clever Clocks Screensaver (CLEVERCLOCKS), iTunes Podcasts (ITPC), My Channels (MYCHANNELS)