"RokuKC" wrote:
"EnTerr" wrote:
(B) The minimum use case is for tvinput.dtv to just do that for /keypress/Lit_[0-9.]|Enter , w/o any UI element. Easy-peasy. And the beauty of it - again - is that nobody will need to update their remote app for this to work! Let's go with an example, a popular J/S remote: http://remoku.tv/ being able to "dial" channel# as-is, w/o any changes to the site.
Given that Roku remotes don't have a numeric keypad, I don't see worthwhile value in this.
Smart remotes can use the ECP services to provide an intelligent TV channel selection UI, which is a much better user experience than the class dumb / 'trial and error' TV channel number entry.
Phones, tablets and computers tend to have keyboards
🙂Certainly a better TV channel UI is better - but who will re-do all existing apps?
There is a flock of them - I had a quick look and there are over ~16 Roku remoting apps for iOS, ~24 for Android, ~12 for Windows phone - so altogether about
50 remote apps. Is it smart to 50x the amount of work? Will they bother, given that RokuTV is ballpark 8% of the Rokus in use?
Let's say the Co's attitude to such apps and users is "screw them" because there is "Roku by Roku Inc" app for these 3 top mobile platforms. How about exotics like Symbian, Blackberry, Maemo/MeeGo/Tizen then? Roku fans have written apps for these years ago.
