Roku Voice Remote Pro v2
Imagining a remote that could be used in any environment — even a dark living room during movie night. By adding intelligent backlighting that responds to movement, a smarter shortcut launcher, and refined aesthetics, we elevated usability and delight while keeping the remote simple, intuitive, and true to Roku's design philosophy.
2nd Edition
The wand that activates the magic.
If the Roku 10-foot UI is the magic, then the remote is the wand that activates it. The Voice Remote Pro v2 — internally codenamed Oso — was Roku's next evolution of its best remote: slimmer, rechargeable, backlit, and smarter about how users interact with their entertainment setup.
UXDR 1
Scope & Vision
UXDR 2
Mild–Wild Concepts
Research
In-Lab Study
UX Spec
Eng Handoff
Ship
Fall 2024
In compliance with my non-disclosure agreement, I've omitted confidential information from this case study. The insights shared here are my own and don't necessarily represent the views of Roku.
Premium by every measure.
Oso inherited Roku's trusted design language but pushed it meaningfully further — slimmer, cleaner, more considered — without losing the approachable familiarity that users already knew.
Three Design Directions
Mild — Evo Concept
Evolutionary update. Smaller form, lower profile buttons, maintains concave/convex topology.
Medium — Frame Concept
Plastic accent frame wraps the upper housing. Familiar silhouette, meaningfully more premium. The form that shipped.
Wild — Metal Accent
Metal band wraps the housing — premium feel but raised questions about button comfort and manufacturing.
Not a feature — a behavior system.
Backlighting was the most-requested improvement from Voice Remote Pro post-launch survey users. Every interaction state needed a defined LED response, with downstream impacts on battery life, firmware, hardware, and user expectations.
12+ distinct LED states to define
Backlight ON, HOLD, Fade to OFF, Hands-Free Listening, Find My Remote, Out of Box Experience, Status Indicator — each needed a Mild/Medium/Wild variant explored.
Three competing activation methods
Proximity sensor (Azoteq cap touch), Realtek cap touch, and Accelerometer — each with different cost, feel, and hardware constraints.
Battery life as a hard constraint
Every brightness level, hold duration, and fade curve had a direct impact on battery drain. UX ambitions had to stay within engineering-validated bounds.
No prior Roku baseline to reference
Roku had never shipped a backlit remote. We built physical prototypes — Gazelle housing with tunable RGBW LED key mats — to study competitive references and validate our approach in-lab.
Mild to wild, validated in-lab.
Every backlighting behavior was explored across three levels of ambition — then tested with 12 participants in a controlled UXR study across light and dark room conditions.
Cool White · Button Press
All buttons lit cool white. 2s hold, re-triggered by button press only. No user settings control. Mimics competitor defaults at lowest cost.
Proximity · 4.5s Hold · Ramp
Cap touch proximity triggers smooth ramp-on (1s to 75%). 4.5s hold, then asymmetric fade off (2.5s). Settings control exposed. Lit D-pad.
D-Pad Bloom · Voice Control
Accelerometer activation with D-pad blooming alive in stages. Full voice control of brightness. Always on while held. Maximum expressivity, highest battery cost.
Backlighting signals premium
After completing tasks, the prototype was rated higher on "The remote is premium." Backlighting was cited as the primary driver of the upgrade perception.
P0: Re-triggering must be consistent
In Mild, button presses sometimes re-triggered backlighting and sometimes didn't. Users assumed the remote was broken. Consistency is table stakes.
Lit D-pad strongly preferred
9 of 11 participants preferred the illuminated D-pad. "Easier to see" and "more vibrant" were the most common reasons cited.
White voice button beat purple
White was "easier to see" and aligned with Roku speaker products. Purple didn't sufficiently differentiate the voice button.
Proximity felt magical — cap touch won
Proximity was preferred for its "just wave your hand" quality. The Azoteq cap touch sensor was recommended for its ability to detect both held and not-held states — preventing false triggers when the remote rests on a couch or table.
Balancing delight with engineering reality.
- Proximity cap touch felt magical — backlighting appears as you reach for the remote, without a button press needed
- 4.5s hold matched what research participants felt was the right duration for backlighting to stay illuminated
- Asymmetric ramp (1s ON, 2.5s OFF) benchmarked as best-in-class against the Xfinity XR16
- Settings control (Dim / Normal / Bright / Off) gave users agency without overcomplicating the default experience
- Wild's D-pad bloom required an LED PCB configuration that wasn't feasible at EVT2
One button. What should it do?
Oso moved to a single Personal Shortcut button that invokes an on-screen HUD offering multiple shortcut options — no more juggling two buttons for two apps.
Icon Selection: Rocket vs Bolt
Single-function legacy behavior
Previous shortcut buttons each launched a single assigned app, limited to two choices.
New: Contextual HUD launcher
One button, multiple configurable shortcuts. Endless flexibility without the clutter.
Design goal: Fast and forgettable
The HUD needed to appear quickly, feel responsive, and disappear cleanly using familiar Roku UI patterns — zero learning required.
Red and white. Two colors, many messages.
Oso moved to a bi-color White/Red LED — a cost adder the UX team justified by demonstrating meaningful user value across critical states.
A single-color LED only tells users the remote is "doing something." A bi-color LED tells them what it's doing and whether they need to act. The UX team demonstrated this in stakeholder review — and it shipped in Oso.
What this project taught me
A remote is a system, not a list of features
Each work track had to feel like one coherent product decision. Coherence was the design goal, not individual features.
Timing is a design material
The difference between a 2s and 4.5s hold, or a 1s vs 2.5s fade, is what made the remote feel premium vs broken. Research gave us confidence to spec exact values.
Physical prototypes unlock research that wireframes can't
Building a hardware prototype with tunable RGBW LEDs was essential. The fidelity of the prototype directly determined the quality of the research findings.
UX can justify hardware cost adders
The bi-color LED and proximity sensor both had real BOM cost implications — approved because the UX team demonstrated concrete user value in research.