A mismatched keyboard type forces repeated panel switching
Aliases: keyboard mismatch · wrong inputmode · layer-switch burden
What it is
When the character set a field actually needs does not match the plane that appears, the keyboard type is mismatched. A one-time code that raises a full alphabet, a username that needs underscore raising the email plane, an amount that needs a decimal raising an integer pad without a point—each missing home-plane character costs a layer switch and another to return. Mismatch turns a switch count that should have been zero into the main action of the task.
Why it happens
A specialized keyboard is a narrowed character table. When the table is narrower than the task, missing characters can only be fetched from the next layer; when it is wider, the first layer is crowded with unused keys, targets shrink or are pushed to a corner, and people still switch to the plane that “looks more like digits.” Mismatches often come from stretching HTML type: type="number" pops a dial pad without minus or point in some browsers; type="email" is reused on arbitrary account fields; a verification field is left on the alphabetic keyboard. Each switch re-aims at a new keymap, so a motor program cannot continue inside the field. If adjacent fields bounce (email → digits-only → letters again), layer switches stack on a visual interruption of the whole keyboard.
Studying it
Run an A/B of deliberate mismatch versus a correct match. Record layer switches, time spent on the wrong layer, and format errors that follow. Independent variables include declared keyboard type, the field’s actual character set, and whether neighbouring field types jitter; dependent measures include switch count, completion time, and extra or omitted characters caused by switching. Distinguish “switched to symbols for a legal character” from “switched the wrong way and back.”
Where it stops holding
When users occasionally need characters outside the type (a text extension note in a phone field), locking the other layers is worse than a switch; allow leaving, and do not treat mismatch as “they should not be able to switch.” The same field may need different characters by region (decimal comma, phone extensions): one type is a match in one locale and a mismatch in another. Hardware keyboards have no layers to switch; mismatch then shows up as missing convenient symbols, not as repeated taps on “123.”
Applying it
- Pick the type from the character set the field truly produces, not from “this box somewhat resembles an email.”
- Do not bounce adjacent fields between types without reason; if they can share a primary plane, do not replace the whole keymap on every focus.
- In session replay, if high-frequency characters keep arriving from the second layer, change the type before teaching people to find the symbol page.