Sliders suit approximate values, not exact ones

What it is

A slider maps a continuous (or densely discrete) quantity onto a position on a track. A finger or pointer moves, the value changes—good for approximate goals such as “about this bright” or “volume is fine.” Landing on a particular integer—188 yuan, day 365—is the wrong job: the position-to-value map is too coarse to stop stably on that cell. The issue is whether the task wants approximate or exact, not whether a number sits beside the track, and not how long the track is.

Why it happens

Slider input is spatial position. Motor control is good at parking a thumb where it “looks about right,” not at “exactly the Nth pixel.” If the goal already has tolerance (brightness, volume, map zoom), tolerance covers localization error and the interaction is fluent. If the goal is a unique legal point, localization error becomes right versus wrong. The continuous feel also tempts people into thinking they can tune finer, so they micro-adjust and stall on exact tasks. A slider’s gift is seeing at a glance where a quantity sits in its full range; that gift serves comparison and trend, not typing a known number.

Studying it

Give the same numeric task as a slider, typing, and a stepper; compare time to a specified value, final deviation, overshoot. Factors: whether the target allows tolerance, number of legal values, whether participants know the exact number. Outcomes: absolute error, deviation when they say “good enough.” When the exact number is known, sliders reliably get slower and more biased. Do not prove a slider “isn’t precise enough” on a brightness task—the task never asked for that cell.

Where it stops holding

With only a handful of legal notches, a slider is used as a segmented control, exactness drops, but discoverability is worse than segment buttons. On a log scale (volume, frequency) the visual midpoint is not the numeric midpoint, and the sense of “about” is lied to by the map. Keyboard arrows on a slider restore exactness per key if the step is sane; that does not change the pointer and finger conclusion that sliders suit approximation. Money, quantities, and dates with one correct value should not take a slider as the primary input even if one can be dragged.

Applying it

• Use a slider when the goal has tolerance and people need the quantity’s place in the full span (volume, brightness, rough ends of a filter range).
• When the goal is a known exact number, type or step; do not impersonate a numeric field with a slider.
• If the business needs both, let the slider do approximate and give a numeric inlet for exact; do not make people pick a digit off the track.
• Verify with a must-hit integer (188) and a “close enough” quantity. Repeated overshoot on the first and a clean stop on the second means the task match holds.

Related

• Within the group: E2.12.2 The current value must be shown as a live number · E2.12.3 Track length sets reachable precision · E2.12.4 The thumb is often below a usable hit size
• Adjacent: E2.11 Numeric input and steppers · E3.09 Rating controls
• Search terms: slider for approximate values · range input · precision versus approximation