Complications are tiny, so readability is tightly limited

What it is

A complication is that small patch in a corner or on a ring of the face, often a few millimetres to a centimetre or so. What it can stably yield is one or two digits, a spare icon, a short arc—not a label, and not a shrunken app home. Readability here is set by visual angle and contrast, and on a raise the patch often sits at the rim, less face-on than the time at center. This entry is only about what still reads at that size. It is not about whether the face is the main entry, and not about how often the value refreshes.

Why it happens

Acuity is an angle. The closer the slot sits to the rim, and the more the face tilts, the smaller the angle for the same pixels; strokes below critical print size collapse. Corners and bezels cut usable height, so a line of type often has room for two or three Latin letters or one Chinese character. People will not lift the watch to the eyes to read a slot—the slot has to be takeable in the periphery of the same look that reads the time. Peripheral vision is poor at detail and better at open versus closed rings and color blocks, so “the ring still has a gap” fits this location better than “428 kcal left.” Trying to cram an app name, a unit, and four digits into the slot forces type below the readable line. The slot is there; the information is not.

Studying it

Measure threshold readability at real raise distance and angle. Encode the same datum as two digits, four digits plus unit, a short word, an icon, an arc, and see which a walking raise can report. Include people with typical acuity and people who use larger system type.

Independent variables: physical size and position of the slot (corner / ring / near a lug), encoding (numeral / word / icon / arc), contrast, raise tilt. Dependent variables: accuracy on one raise, reading the neighboring slot by mistake, subjective effort.

Sitting with the dial square to the eyes overestimates. Measure under the target user’s correction, not only young normal acuity. Do not convert desktop type scales—viewing distance and tilt are not a phone’s.

Where it stops holding

A large face, or a modular face with only one or two slots, can grow a slot large enough for a short word. Thresholds move with slot area; do not cut them all with data from the smallest corner. Low-vision users who enable system zoom crop or overlap slots until readability collapses; they need a “few slots, large type” face, not the same set of slots hoped to survive magnification. Outdoor glare drops thin low-contrast arcs before numerals. Always-on at low luminance drops contrast another step; rim slots go first.

Applying it

• Pick one encoding per slot: two digits, or one icon, or one arc. Do not put label plus numeral plus unit in the smallest corner.
• Encode the most-asked quantity as completeness (ring or color), and leave the exact numeral for the screen after the slot is tapped.
• Accept contrast on the rim slot, always-on, and outdoors—not only in a bright indoor preview after the screen was off.
• Verify by having people walk and raise and speak each slot’s meaning. If they stably report “there is something” but not the value, or they name the neighboring slot, reduce encoding. Reduce until one raise yields the value, then decide whether the exact numeral belongs after a tap.

Related

• Within the group: K4.06.1 The watch face is the highest-frequency information entry · K4.06.3 Complication update rate is bounded by battery
• Adjacent: A1.03 Visual Acuity and Minimum Legible Detail · K4.01 Wrist Raise and Glance · K4.05 Information Compression
• Search terms: critical print size · complication · glanceable glyph