Choose a software keypad layout that matches the device type users know in that scene

What it is

An on-screen number pad can be drawn in either row order. The choice should follow which device class users already know in this scene, not which class the designer knows. Dialing, entering a one-time code, or an elevator-style lock mostly evoke a telephone pad (1 on top). Bookkeeping, changing a menu price, or scientific calculation mostly evoke a calculator (7 on top). The wrong choice does not make keys unusable; it aims an existing motor program at the wrong surface.

Why it happens

Familiarity comes from occupation and daily devices, not from “numbers are numbers.” A cashier's right hand remembers 789 on top; a phone-only user remembers 123 on top. A software pad that draws telephone order for changing an order total will concentrate errors on 1/7 swaps. Matching is not a generational guess: older adults may still know 1-on-top from landlines and feature phones. System default pads (telephone-like on iOS/Android, calculator-like on desktop numpads) leak into the Web's numeric input mode; a page that draws the opposite stacks a second conflict on that habit.

Studying it

Survey which devices the target population used for digits in the past week (phone dialer, ATM, POS, computer numpad), then run a matched versus reversed software pad. Dependent measures: time, row-swap errors, and “the keys feel inverted.” Stratify by occupation; do not let a student sample stand in for cashiers. An A/B that only watches overall conversion can wash the matching effect into other variables; pre-register an error-type analysis.

Where it stops holding

True novices trained on neither layout may show a slight reading-order advantage (1 on top), but the task's resemblance to dialing still matters. ATM standards are not globally unified; match local hardware, not headquarters desks. Entering amounts on the QWERTY number row is a third spatial map and does not use the nine-key matching rule. If an OTP can be pasted, row-order weight drops.

Applying it

• Use 123 on top for dialing, OTP, and door-lock entry; 789 on top for money, quantity, and calculator-like tasks.
• When invoking the system number pad, check that platform's default row order; if it contradicts the scene, draw your own and label it.
• Title the pad “dialer” or “calculator” so the model has a name, rather than nine anonymous squares.
• Verify by showing target users static pictures of both row orders and asking which looks like everyday use, then completing a real task on the chosen picture and confirming row swaps stay below the reversed group.

Related

• Same group: C6.23.1 Calculator keypads run 789/456/123 top to bottom; telephone keypads run 123/456/789 · C6.23.2 The two layouts' muscle memories conflict, and mixed use raises entry errors · C6.23.4 If digit positions are not unified across platforms, experience becomes inconsistent
• Adjacent: C6.07 Keyboard types and task fit · C6.29 Dedicated password keyboards
• Search: numeric keypad mapping · task-device fit · PIN pad layout