3 ms·
You raise a good question, and it's really annoying to read articles that tease out specific examples and never offer the alternative. However, I'd say you ans
by nemesisj 13y ago
You raise a good question, and it's really annoying to read articles that tease out specific examples and never offer the alternative. However, I'd say you answered your own question. The TV remote really needs to be nothing more than a D pad, select button, and back button (could probably even dispense with that). You then just work on the software which is context aware and presents you the simple 2-3 choices you need within each context.
- biot 13y agoIf you're offloading buttons from the remote into a context-aware software interface, the interface now becomes an integral part of the UX. And avoiding an additional button on the remote control in favor of a software menu may, in fact, degrade the experience. Having a "swap to previous channel" button is likely a better experience than making someone access that functionality via a software menu. Saying "just make it context aware" is a bit too much like "How to draw an owl": http://www.maniacworld.com/how-two-draw-an-owl.jpg http://www.maniacworld.com/how-two-draw-an-owl.jpg