Shortcuts should match the desktop ones people already know

What it is

People who attach a keyboard bring the chords they already play on a desktop. Shortcuts matching the desktop means copy, paste, undo, save, select-all, and find still land on the same modifiers and letters on the tablet, rather than a freshly invented “tablet set.” What must match is that small public skill, not the whole desktop shortcut architecture: which system chords are reserved, how modifiers map across operating systems, and how conflicts are customized are desktop problems of their own. This entry only asks whether the same hands, moved from a laptop to a keyboarded tablet, still hit the same intents with the usual chords.

Why it happens

Shortcuts are muscle memory. Ctrl/Cmd+C is already bound to copy; pressing it on a tablet is skill transfer, not a new lesson. If the tablet remaps Cmd+C to “insert a comment” and hides copy under another chord in a menu, transfer fails and the keyboard looks broken or unconnected. Tablet apps often grow from phone code. Phones have no modifiers, so developers invent new chords, and desktop users press air. Consistency also has an in-family reading: if this tablet shares a family with a desktop OS, modifiers should follow that desktop (Cmd or Ctrl), not the other family’s desktop. Full keyboard navigation is what puts focus on the right object so a shortcut can act on it; navigation itself is not the shortcut.

Studying it

Take people who are already fluent on a desktop, attach a tablet keyboard, give no cheat sheet, and ask for copy, paste, undo, save, and find. Record the first chord pressed and whether it hit.

Independent variables: whether tablet shortcuts match the same-family desktop app, whether chords are written in menus or key hints, whether a system chord ate the press. Dependent variables: first-press hit rate, times the task was finished by touch instead, other commands fired by mistake.

Participants must actually know the desktop set, or the study measures learning rather than transfer. Do not test an entire shortcut map; the small public set is the scope of this entry. Obscure app-private chords may differ.

Where it stops holding

Chords the tablet OS itself uses (app switch, home, screenshot) cannot be stolen by the app; “match the desktop app” then yields to “match this device’s system.” The same app already uses different modifiers on Windows and Mac desktops; the tablet should follow the computer those hands came from, not invent a third unification. With no keyboard attached, shortcut badges can stay off; write them in menus once a keyboard is present. Games and instruments have their own binding traditions and need not match an office desktop.

Applying it

• Wire copy, paste, cut, undo, redo, save, select-all, and find to the same chords as the same-family desktop app, and write those chords beside the menu items.
• Do not invent a parallel set of keys for public actions on tablets. New features may take new chords; they may not occupy keys that already belong to public actions.
• Leave system-reserved chords to the system. Use a neighbor key or the menu in the app rather than failing silently.
• Verify by asking someone to copy, paste, and undo on a keyboarded tablet using only desktop habits, with no manual. List every first-press miss or dead key, and change those chords to match the same-family desktop app.

Related

• Within the group: K3.04.1 An attached keyboard requires full keyboard navigation · K3.04.2 Dismissing the software keyboard changes the visible area
• Adjacent: K2.04 Desktop Shortcut Systems · K2.03 Menu Bar · C6.22 Focus Order and Keyboard Navigation
• Search terms: shortcut transfer · keyboard accelerators · cross-device consistency