Game UI Design

Core Workflow

Identify the game genre, platform, input devices, player skill level, session length, and whether the UI is diegetic, overlay, menu-driven, or hybrid.
Map the player's immediate decisions before drawing screens. Prioritize the information needed for action, risk, timing, navigation, and feedback.
Match UI density to play context: combat and real-time play need fast recognition; management, inventory, and strategy screens can support comparison and detail.
Bind UI to explicit game-state owners where possible, such as health, inventory, cooldown, quest, input, or interaction components, rather than reading a large player script.
Design complete states, not just the default state: empty, loading, disabled, locked, selected, focused, hover, pressed, error, cooldown, low-resource, warning, success, and paused.
Implement controller/keyboard/mouse/touch navigation deliberately. Define focus order, wrap behavior, cancel/back behavior, and input remapping access.
Verify in motion and at target resolutions. Check text fit, occlusion, contrast, safe areas, scaling, localization risk, and whether the UI remains readable over gameplay.