I have a web application (HTML5) which works well in Google Chrome with mouse navigation, and I am adding d-pad navigation support.
I have asked on StackOverflow about programming models for d-pad support. I am hoping UX folks here can point to best practices on adding d-pad support, the kinds of questions I have are:
- Is it better to provide a virtual pointer or to provide cues to the user as to which actionable item currently has focus? A virtual pointer is easier to implement, but it then requires the user to click more to get to the right spot and click, and also allows user to navigate to spots where a select click does nothing
- If in my layout of actionable items (e.g. buttons) I am at the rightmost button, what should the right arrow do? Should it then jump to the leftmost?
- If I am changing screens, and I include a "back" button at the top left, should I put focus there, or on the first non-back button?
- For modal and nonmodal new windows, how do I decide if I should put focus on the newly visible elements?
- For scrollable containers with content not currently visible, if I navigate downward, should that scrollable always scroll, is it acceptable to simply place focus (I am currently using a WebTV-style focus outline) on the next item.
That's a selection of the issues that come up. Any resources on this issue are most welcome.
UPDATE: Feel free to answer only sub-questions if there are no general resources out there on this issue. I'm sensing d-pad navigation is getting less attention since direct manipulation/touch seems to be available for many devices these days. I wonder if there are resources for implementing d-pads in gaming or television devices out there.