In order to understand what to include in the UI, we need to understand the game's UX and how best to deliver that experience to users. One of the most important UI features in games is the HUD.
What is the HUD?
The HUD (Heads-Up-Display) is the way players are kept informed about the main information needed in the current situation within the game. It is vitally important to share the necessary information in a clear, concise way so as not to overwhelm users while they play.
.png)
(Above: HUD elements highlighted in F1 23)
UX Discussions
I discussed the game UX with the client in order to understand what to include in the HUD and how to include it. For example, if we want a HUD for a fun children's game, then we might want to think of bright colours, big fonts and fun, bouncy animations.
The aim of the game is to provide an adrenaline-rush for users, which will be provided by:
- building strong rivalries with NPCs through storylines and challenges,
- creating a sense of pressure in races by emphasising the space (or lack of) between the player and other racers,
- bringing in a new points system for style, which will be powered up by driving with style (taking shortcuts, performing stunts better or breaking speed limits).
Results & Decisions for UI
In order to support the game's UX, the HUD (which is a vital part of the UI) will need to include:
- speed & current gear,
- map with other cars' location,
- style points gauge,
- control help (that can be disabled in settings),
- notifications which include overtaking & how close rivals are to you.
