Skip to content
nuggetof joy

Post · November 17, 2026

Original Video Game Concept and Prototype

AMDE 457 / 447 · Advanced UI/UX Design

Design a playable sequence

Design the interface and player experience for an original video game. Start with a game idea, map what the player does, and use Figma Make to build a playable sample of how the game looks and responds. Your final prototype should let someone follow one complete gameplay sequence, from entering the game to seeing the result of an action.

Signal Garden puzzle board showing a beam reflected toward a plant.

Mini-lesson · Start with the player

Pick one action the player will repeat. What are they trying to do? What information do they need before acting? How will they know what happened afterward? Use those answers to decide what appears on each screen.

Example · Signal Garden
In a cozy puzzle game, the player redirects a beam of light to grow a plant. On the gameplay screen, the player sees the beam, the target plant, and how many moves remain. When they rotate a mirror, the beam changes direction. The result screen tells them whether they completed the puzzle and offers a next step.

Signal Garden · Sample user flow

The player has three moves to redirect a beam toward a plant. Each turn uses one move and updates the beam and the move counter.

Six-screen flow from Title to Level selection, Gameplay, and Updated gameplay. Success leads to Puzzle complete. Running out of moves leads to Out of moves. Continue returns to Level selection. Retry resets Gameplay.
Current screenPlayer action or game eventNext screen
01 · Title screenSelect Start.02 · Level selection
02 · Level selectionSelect Puzzle 1.03 · Gameplay
03 · GameplaySelect Rotate mirror.04 · Updated gameplay
04 · Updated gameplayThe beam reaches the plant.05 · Puzzle complete
04 · Updated gameplayThe beam misses and no moves remain.06 · Out of moves
04 · Updated gameplayThe beam misses and moves remain.03 · Gameplay, with the new mirror angle and remaining moves
05 · Puzzle completeSelect Continue.02 · Level selection
06 · Out of movesSelect Retry.03 · Gameplay, reset to its starting state

For your own user map: Draw one box for each numbered screen. Draw an arrow for each row and label it with the action or event in the middle column. In Figma, you can demonstrate the success and retry paths with linked frames that show each outcome.

Use Figma Design for your screen designs, Figma or FigJam for your player map, and Figma Make to build one playable sequence. Keep the scope to one level, round, or encounter.

1. Submit your game proposal

Write a short proposal that explains the game you want to design. Give it a working title, identify the genre, intended player, and platform, and describe the main gameplay activity. Explain what the player is trying to accomplish, what they do repeatedly, and how they know whether they succeeded. Identify the gameplay sequence you plan to prototype.

Self-driven criteria. Include two specific goals you want your design to meet and submit them for instructor approval with your proposal. For example, “A first-time player can find the number of moves remaining during gameplay” or “A player can retry from the results screen in one action.”

2. Submit your user map

Make a player flow map in Figma or FigJam. Draw a box for each screen or meaningful state and use arrows to connect them. Label each arrow with the player action or game event that causes the transition, such as Select Start, Rotate mirror, or Run out of moves.

Show the main route into gameplay, the core interaction, and the outcome. Include at least one meaningful branch or return path, such as retrying a puzzle, closing an inventory, or returning from pause. Use the same screen names in your map and your final Figma frames.

3. Submit your UI/UX style guide

Create a dedicated Figma page or frame that shows both the game’s general look and feel and the rules for its interface. A classmate should be able to use the guide to design another screen that feels like part of the same game.

  • Look and feel. Include a few visual references or your own studies. Describe the mood and how it supports the game idea.
  • Visual vocabulary. Show your color palette, type hierarchy, icon style, and image or illustration treatment. Label where each is used.
  • Interface components. Show the buttons, cards, menus, or heads-up display (HUD) elements your game needs. Include relevant states such as selected, disabled, focused, or pressed.
  • Feedback and readability. Show one example of how the interface responds to a player action. Use readable text and pair color with labels, icons, or shapes when communicating important information.

4. Submit 5–10 game screens and a clickable prototype

Design five to ten polished screens or distinct screen states in Figma at a size appropriate to your platform. Choose screens that demonstrate how your game works. Your proposal, map, and style guide are separate deliverables.

For example, a six-screen puzzle prototype could include a title screen, level selection, gameplay before an action, gameplay after that action, a success screen, and a retry screen. A role-playing game could use some of those slots for inventory, dialogue, or a quest decision instead.

Before rotating the mirror, three moves remain and the beam misses. After rotating, two moves remain and the beam reaches the plant.
Two gameplay states from the sample prototype. Show what changes after a player action, including the move counter and the result.
  1. Sketch rough layouts first. Decide what each screen helps the player do.
  2. Apply your style guide to the screens. Name each frame so it matches your player flow map.
  3. Build the main gameplay route and its branch or return path in Figma Make. Use your designed screens as the visual reference and check that the prototype starts on the intended screen.
  4. Ask a classmate to run through the prototype with minimal guidance. Where do they hesitate? What feedback do they miss? Revise one issue you observe.

Build your game in Figma Make

Write your first prompt outside Make. Use your proposal for the game rules, your user map for the actions and transitions, and your style guide for the look and feel. Every prompt you send uses AI credits. Cost varies with the model, task complexity, and amount of context you include.

Before you send the first prompt

  1. Choose one playable slice. Name the starting screen, the main player action, the success and failure conditions, and what Retry resets.
  2. Decide what the player sees. List your 5–10 screens or states. For each, identify the main control and the feedback it gives. Specify your target device and input.
  3. Give Make a focused visual reference. Summarize your colors, type, and controls. If you attach designs, choose the key frame or compact style guide that shows the rules Make needs to follow.
  4. Write a pass/fail test. Describe the exact actions you’ll take in Preview and the result you expect. Save some credits for fixes after you test.

Copy and adapt this first prompt

Replace the bracketed text with details from your project before sending it.

Build a playable prototype of [game title] for [device and input].
Scope: one [level, round, or encounter]. The player’s goal is [goal].

Screens and states: [list your 5–10 named screens or states].
Start on [screen]. When the player chooses [control], go to [screen].
During play, [main action] changes [game state] and visibly updates
[HUD, board, or feedback]. Success happens when [rule]. Failure happens
when [rule]. Retry restores [list what resets].

Visual direction: [colors, typography, and control styles].
Use [specific reference, if attached] to match the layout and styling.
Keep this build to the screens and interactions listed above.

Test: From the start screen, [actions]. Expect [result].
Then test [failure path]. Retry should restore [starting state].

Test first, then fix one issue

Play through the main route and Retry before asking for changes. Write down the screen, what you did, what happened, and what you expected. Fix a broken interaction before spending another prompt on visual polish.

Signal Garden follow-up prompt
On the Out of Moves screen, Retry returns to Gameplay but leaves the counter at zero. Make Retry reset the counter to 3 and restore the starting mirror angle. Keep the existing layout and other transitions. Test by using all three moves and selecting Retry.

For a small project, decide whether you need Make’s Plan mode before using it. Generating the plan and building it are separate credit-consuming actions. Read Figma’s credit optimization guide.

What to submit in D2L

  1. Proposal with your game concept and two self-driven criteria for approval.
  2. User map with labeled screens, transitions, and a branch or return path.
  3. UI/UX style guide showing the visual direction and interface rules.
  4. Figma Design and Figma Make links. The Design file shows your 5–10 screens. The Make link opens the playable game sequence. Include a separate FigJam link if your map is there. Check that the instructor has view access and that the prototype opens at its starting screen.

See D2L for submission details and due dates.

How the work will be reviewed

  • Concept and scope. The proposal explains what players do and identifies a sequence you can demonstrate in 5–10 screens.
  • Player flow. The map and prototype agree, and the player can tell what to do and where to go next.
  • Visual and interface design. The style guide informs the screens, and the interface is consistent, readable, and suited to the game.
  • Functionality and feedback. The prototype shows the main interaction and makes the result of the player’s action clear.
  • Self-driven criteria. The final work demonstrates the approved goals from your proposal.