Amazon · Case study
Platform UX for Fire devices.
- Platform UX Guidelines
- 10-foot UI · Fire TV
- Fire Tablet
- Production Design
- Design QA
- Cross-team Coordination
- Role
- UX Production Designer · Devices
- Timeline
- Jun 2015 — Oct 2015
- Platform
- Fire TV · Fire Tablet
- Surface
- 10-foot UI · Tablet UI · Guidelines
Overview
Two devices, two interaction models, one quality bar.
Fire TV and Fire Tablet shared a brand and a developer ecosystem, but interaction was a world apart: a remote control at ten feet versus touch at arm’s length. The team’s job was to keep both honest to their context, without letting either drift from Amazon’s broader quality standard.
The work split between authoring platform UX guidelines and running production design on partner-facing flows that had to hold up against them.
Strategy
Guidelines that respected the device.
- 01
10-foot UI, on its own terms
Fire TV patterns built around D-pad navigation, focus states, and reading distance, not borrowed from mobile or web.
- 02
Tablet patterns that earned the touch surface
Fire Tablet leaned into structure mobile users already understood, with Amazon-specific patterns around content, store and reading layered on top.
- 03
Guidelines partners could actually follow
Documentation, examples and review templates that turned design intent into something an external team could implement without ambiguity.
Design
Patterns, partners, production.
Fire TV: focus and rhythm at 10 feet
Leanback flows for partner channels had to read clearly across the room. Focus states, row rhythm, and content density were tuned to the remote control as the only input, with sign-in and search treated as first-class screens.
Search as a TV-native experience
Search on Fire TV had to work without a keyboard, with focus that didn’t trap the user, and result rows that scanned at a glance. Treating it as a TV problem, not a web problem, was most of the work.
A remote-mapped reference for partners
A controller diagram documented the D-pad mapping for every primary action. It became the alignment artifact for partner reviews and onboarding.
Fire Tablet: content surfaces that earn the screen
Music, newsstand and reading flows on Fire Tablet treated the device as a primary surface, not a stripped-down phone. Density, art treatment, and category browsing were tuned to long sessions at home.
Outcome
Guidelines and production, on two device families.
2
device families: Fire TV and Fire Tablet
Authoring
and QA across platform guidelines
Partner
-facing flows shipped to production
Reflection
Production design is principled craft.
The role wasn’t to invent the system; it was to keep the system honest where it met real partners and real content. Most of the value was in the review, the redline, and the documentation that told the next team why a pattern existed.
Authoring guidelines and executing against them in the same quarter is a useful discipline. It keeps a system from hardening into something that only its authors can hold.