DESIGN BRIEF
FUI Instrument Design Brief
Create a fictional interface instrument around a single player decision.
Why it matters
Fictional user interfaces (FUI) can easily turn into decoration: moving lines and numbers that look impressive but don’t help the player decide anything. Starting from one player decision keeps the instrument readable while still feeling like part of the world, which is the balance strong sci-fi and simulation interfaces achieve.
Workflow
Begin with the player question, input data, units, usable range, warning state, and loss-of-signal behavior. Put the actionable value and state first, then detail for the player who has time to inspect it. Give warnings a text label and a perceptible visual change.
Worked example
A fictional rover terrain display answers whether the next slope can be crossed. It shows measured incline next to the rover’s illustrated limit. If sensor data drops out, label the last reading as stale and distinguish it from a current reading.
Try it
Sketch normal, near-limit, and unavailable states at final presentation size. Show each for a moment and ask what the player would do next. Record any interpretation that disagrees with the instrument’s intended meaning.
Common mistakes to avoid
Adding detail before deciding what the player must read first. Using animation that hides the actual value. Making warnings depend on color alone. Showing data with no units or range. Forgetting what happens when the signal is lost or the data is out of date.
Use it in your portfolio
Show the three states side by side and label the decision the instrument supports. Pair them with a short clip in motion. Reviewers want to see that your FUI looks great and communicates clearly.
Keep going
Pair this with the Game HUD design and the Motion Spec, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.