Defining the experience:

1. The player starts at the bottom, hop to the top into the pond, and repeat until three frogs make it across to win.2. Player progression is blocked by blinking mines; if green you can jump on them, if red they explode.3. There are patrolling guards that will shoot at player if they see him/her.4. There are searhlights that will alert all guards to player location if caught and order them to shoot.5. There are trains running across the screen which will kill the player instantly if it hit. (cars from original "Frogger")

Shapes:
Based on the defined experience a full asset list was created to determine what the full scene consists of.Scaling:
Simple sprite geometry was created and put in place to define objects scale and placement in the scene.Simple Logic:
Enemy behavior tests turned idle guards into patrolling ones after balancing issues—player detection disrupted
look \patterns, creating exploitable gaps in patrol coverage.Pacing:
Level flow was experimented upon by moving around objects and playing around with spawn time for the train.

Grayboxing: Initial planning using simple shapes and color.

Custom made tool: dynamic AI-Behaviour.

AI-Behaviour:

"HOW MIGHT WE CREATE EASY TO USE AI-BEHAVIOUR TOOLS?"

Dynamic:
To streamline development I created a node based ai tool that could be updated during runtime. To figure out interesting patrol patterns quickly.Scalible:
The tool supports unlimited nodes in the scene, each with
its own behavior script, enabling complex AI behavior chains.Easy to use:
Simple Usability: place a prefab node into the “next node” slot—its instructions play automatically when reached.

Main Menu:

"HOW MIGHT WE PREPARE THE PLAYER FOR THE EXPERIENCE?"

Concept:
Using a "living” background from the actual level I tried to prime the player and set expectations of what to come.Tone:
I aimed for an exaggerated, playful tone that would intrugie a younger audience — from a reactive ustom cursor to slightly moving menus that gave clear feedback.

Player Feedback:

"HOW MIGHT WE CONVEY DAMAGE TAKEN TO THE PLAYER?"

Context - Stunned:
When the player takes too much damage, they become stunned and frozen in place.Visual cues:
I tried to include as many conventions as possible to convey a "stun" effect. By turning the character blue I could suggest that the player was cold/frozen and thus "stuck" in place" while quick camera shake and chromatic aberration effect suggested impact and dizziness.Audio cues:
A playful bird chatter together with animated sprites of birds that circled the player emphasized the effect while keeping in line with a lighthearted, cartoon-style “dazed” effect.

Showcasing the finalized stun effect.

Showcasing the finalized button prompt to recall shield.

Button Prompts:

"HOW MIGHT WE TEACH THE PLAYER TO RECALL THE SHIELD?"

Decision:
Button prompts were chosen for their simple yet direct nature in communicating information.Placement:
The prompts needed to be noticible at all times. Early on, I placed them above the player’s head but testing showed that players rarely looked there.Iterations:
Based on User Research I decided to place the prompts near the cursor and added a slight animation to try and draw player focus and suggest interaction.

Fallback: traditional UI-Design.

Deagetic implementation in scene.

Simple tool I created for the designers.