Custom Interface
We are in the R&D stage of developing an application on Roku. Our main goal is to keep a consistent look-and-feel with other platforms we've already developed on. It seems like there are several o...
Forum Discussion
The standard roPosterScreen is not significantly different than the ASCII art you posted. The biggest hurdle is probably the Menu Buttons.
I suggest trying a simple roPosterScreen
You LOGO is "<company logo>" and your "SEARCH BTN" and "three "BTN" can be <Categories>. You will lose the Menu BTN, but perhaps they can be implemented as part of an roSpringboardScreen
Your list overlay is a simple (non-transparent) roListScreen, or you can reimplement using an roSpringboardScreen.
You can stack each of the screens (non-transparently) on top of each other as deep as you need, where the top screen gets the user interaction. It will be relatively straightforward if you don't need to exactly copy your UI. Just substitute with available components as needed.
I suggest trying a simple roPosterScreen
You LOGO is "<company logo>" and your "SEARCH BTN" and "three "BTN" can be <Categories>. You will lose the Menu BTN, but perhaps they can be implemented as part of an roSpringboardScreen
Your list overlay is a simple (non-transparent) roListScreen, or you can reimplement using an roSpringboardScreen.
You can stack each of the screens (non-transparently) on top of each other as deep as you need, where the top screen gets the user interaction. It will be relatively straightforward if you don't need to exactly copy your UI. Just substitute with available components as needed.
