Cross-platform mapping differences need separate design

What it is

Platform-specific controls recognize that touch, keyboard-mouse, controller, and assistive devices differ genuinely in input precision, how many simultaneous inputs they accept, whether they offer physical tactile location, and each platform's own system conventions. This entry completes a chain begun by the previous two: control mapping asks how a default should feel intuitive, customizable controls asks why the default also needs to be changeable, and this one asks why "changeable" is still not enough once the same piece of gameplay has to ship across several device types — a cross-platform release should not mechanically port a button layout designed for one device onto every device; each platform needs its own learnable, reachable, predictable way of carrying out the same core tactical intent.

Why it happens

Keyboard-mouse offers precise pointing and a large number of mutually independent discrete keys; a controller's operating space is bounded by how far a thumb can actually reach and the hierarchy among trigger buttons; touch has no physical location to rely on at all, and a finger covers part of the screen while touching it — these three device categories each have entirely different capability boundaries, and no single input method dominates on every dimension. Porting a mapping designed for one device straight onto another mistakes that one device's specific advantage for a universal capability every device shares, and the result is either noticeably worse feel or a genuine competitive disadvantage for players on a different device in ranked play. Genuine separate design keeps the same tactical goal fixed (the intent "quickly switch to a backup weapon" does not change) while changing the entire interaction grammar built around that goal — how it is triggered, how a target is selected, how aiming works, how it is signaled to the player. The goal stays constant; the path to it can differ completely.

Where it stops holding

What should stay consistent across platforms is the meaning behind an action, a player's saved progress and settings, and the rules of the game world itself — none of these should change arbitrarily just because a player switched devices; platform differences should live entirely in "how to operate," never bleed into "what the game world is." When keyboard-mouse, controller, and touch players are placed in the same competitive matchmaking pool, that needs an explicit matching policy and a defined assist strength per input method — not a single layout forced on everyone and then dressed up as "fairness," since genuine fairness has to account for the real capability ceiling differences between devices. Mobile "simplification" should also never be used as cover for content being cut or accessibility support being inadequate — simplifying operation and gutting content are two different things that should not be conflated.

Applying it

• For each target platform, separately list its frequent actions, the maximum number of simultaneous inputs it can accept, its actual precision requirements, and how much of the screen a finger or controller grip is likely to occlude, and prototype core gameplay loops separately for each — rather than perfecting one platform first and then simply porting it.
• Switch prompt presentation and menu information density dynamically based on the device currently in use; a touch version should have its layout redesigned specifically for touch, rather than simply overlaying a virtual button pad and virtual joystick to simulate a controller.
• How to check: test first-time learnability, fatigue over extended play, and success on consequential tasks separately, using each platform's genuine native device; passing on one platform cannot substitute for verification done separately on another.

Related

• Same group: W3.03.1 Mapping must match spatial and directional intuition · W3.03.2 Mapping must be customizable
• Nearby: W3.07 Touch-game controls · W3.09 Coexisting multiple input devices · K Platforms and device forms
• Search terms: platform-specific controls · input modality · control scheme · cross-platform UX