UI and control prompts must follow the player's actual platform

What it is

Platform-specific UI prompts map icons, button locations, text metaphors, menu gestures, and voice commands to the device and system language the player is using now. A shared codebase that says "press A" in a PC or PlayStation context adds a small avoidable cognitive tax to every action.

Why it happens

A prompt carries two layers: action semantics (open inventory, interact, sprint) and motor path (which physical key, stick direction, or touch gesture). Cross-platform differences include button order and colour, reserved system keys, licensed controller glyphs, desktop/controller dual mode, on-screen keyboards, and wake words. A robust implementation separates a semantic action layer from presentation: logical actions are not hard-coded to keys; runtime generates prompts from active device, player remapping, accessibility settings, and platform rules. When input switches, prompts re-render immediately. Layout must also respect safe areas, resolution, touch reach, and controller thumb arcs so hints do not cover critical play.

Where it stops holding

Custom remapping breaks the idea that a "correct icon" equals a default physical key; prompts must either follow remaps or offer icon and name modes. Mixed-device couch play—one controller, one touch—requires per-player generation. Platform glyphs may be trademarked, so third-party ports need licences or generic symbols. Teaching also cannot rely on icons alone: new players need name, location, and feedback, while touch benefits from one visible guide rather than a small corner icon. Localisation length can squeeze out button labels, so German, Japanese, Arabic, and other layouts and directions need testing.

Applying it

• Drive every prompt from logical actions: button icon, text label, remap value, and accessible alternative text should come from one data source and update together when input changes.
• Cover default prompts for desktop keyboard/mouse, each controller family, touch, and assistive input; show the active input in menus and allow icon, name, or both.
• Verification: screen-record tutorials, combat, menus, and post-remap scenes on real platform/input combinations; check correctness, occlusion, and truncation, then measure time-to-action and misclicks during device switching.

Related

• Same group: W9.08.1 Platform input methods create natural precision gaps · W9.08.2 Cross-platform matchmaking must decide grouping to balance the gap · W9.08.4 Cross-platform progress-sync failures create serious trust problems
• Nearby: H2.03 Input devices and control mapping · J1.02 Multimodal and alternative input · K1.03 Screen and interface adaptation
• Search terms: button prompts · input remapping · platform conventions · controller UI