Rotation-to-scroll mapping must stay consistent
Aliases: crown direction · CD mapping · rotary stereotype
What it is
Which way content moves when the crown turns clockwise must be one rule across the system and every app. The stable mapping in most consumer watches is: clockwise moves a list down, makes a value larger, advances time—aligned, in body coordinates, with the common desktop-wheel habit that away-from-self moves content up / increments. An app that maps clockwise to “previous item” or “quieter” will not be read about; people will turn the wrong way and turn back. This entry is about a stable directional convention. It is not about occlusion while turning, and not about which objects deserve to be turned.
Why it happens
Rotation has no on-screen arrow as a label. Direction is guessed from control–display compatibility and learned stereotypes. A watch makes the guess brittle: the crown sits on the side, and clockwise relative to the dial, the forearm, and the ground are three different frames. During a raise, people use the “dial facing me” frame. Once the system fixes clockwise in that frame as “down / increase,” every UI borrows the same muscle memory. Exceptions turn memory into a conditional rule: “in this app, reverse.” Conditional rules do not load in a few seconds of wrist work; the error is on the first turn. Inertial scrolling amplifies a first wrong turn: overshoot, then turn back, both wasted on the wrong mapping.
Studying it
Combine a population-stereotype questionnaire with an action task. Give no instructions, only a rotatable crown and a list or a numeral. Ask what clockwise will do, then have people “scroll to item X / set volume to Y.” Record first-turn direction and corrections. Contrast the system default with a deliberately reversed mapping.
Independent variables: mapping (system-consistent / reversed), object type (list / value / time), crown on left versus right wrist. Dependent variables: first-direction accuracy, correction count, completion time, verbally reported rule.
Left- versus right-wrist wear flips what “clockwise” means in the body; split those analyses. Do not measure only seated with the dial square to the eyes—the mapping is invoked on a walking raise.
Where it stops holding
Specialist hardware (dive bezels, aviation watches) may carry an industry direction that conflicts with the consumer-system mapping. Follow the industry on that bezel; do not let it contaminate system lists. For zoom, “clockwise in or out” is more contested than for lists; pick one inside a product and give instant visual follow-through, rather than a caption. An accessibility reverse-direction option is a deliberate break for the people who need it; the default should still follow the system. Games and decorative faces may play with mapping; the moment a system list appears, the system rule returns.
Applying it
- Write the system’s three promises for clockwise (list, value, time) and keep them on every wrist UI; new apps do not get to flip the sign.
- The first turn must move content in the promised direction. Do not play a directionless animation before the scroll.
- If a piece of content has a physical convention opposite the system, give it its own bezel or control; do not reuse the system crown.
- Verify with people who have not read the instructions: say only “go to X,” never the direction. Any UI whose first turn is reversed is fighting the system or the stereotype. Fix those until first turns are right, then check that corrections fall near zero.