Experiment Setup: Hi Fi Snake

Source Concept

This experiment is based on the approved Phase 5 Implementation Briefing for Hi Fi Snake. The first playable target focuses on demonstrating the core loop: a player controls a robot head, collects pellets to grow a tail, navigates a single room, uses the tail to unlock a gate (triggering a visual burst), and transitions to a second room where they choose between two simple upgrades.

Prototype Validation Goal

To learn if the core tension of using the tail as both an obstacle and a progression resource (to unlock gates) is immediately readable and satisfying to the Web Gen-Z Drifter persona without causing early frustration or confusion.

Primary Hypothesis

* Hypothesis: Players will intuitively understand that growing their tail is necessary to unlock the gate, and they will find the risk-reward loop of navigating their own self-generated obstacle satisfying rather than frustrating.

* Why it matters: If players find the self-generated obstacle frustrating or fail to understand how to open the gate within the first 10 seconds, they will trigger the exit conditions of the Web Gen-Z Drifter persona (confusion, no immediate reaction).

* Derived from: Phase 5 Core Loop, Known Risks (Tail Navigation Frustration, Visual Clutter), and Attribute 1 (Immediate Visual Readability) & Attribute 2 (Self-Generated Obstacle & Difficulty).

Secondary Questions

* Does the visual feedback of the gate-burst explosion clearly communicate that the tail was consumed to progress? (Derived from Attribute 4: Visually Satisfying Collection & Progression Feedback, and TikTok Moment).

* Do players feel in control of their movement while navigating the self-generated tail obstacle in a confined room? (Derived from Experience Goal: "feel_in_control" and Known Risk: "Tail Navigation Frustration").

* Does the transition to a second room with an upgrade choice successfully create a feeling of constant progress? (Derived from Experience Goal: "feel_constant_progress" and Attribute 3: Frequent Run-Based Upgrades).

Prototype Scope

* Gameplay Capabilities:

* Player-controlled robot head movement (exact control scheme and camera perspective to be defined by user feedback).

* Pellet spawning and collection that increases tail length.

* Tail collision detection triggering a run reset.

* A locked gate requiring a specific tail length to open.

* A gate-burst visual effect when the gate is unlocked and the tail is consumed.

* A transition to a second room.

* One upgrade selection event (e.g., speed boost or smaller tail segment size).

* Excluded:

* Persistent progression systems.

* Daily return hooks and rotating cosmetic rewards.

* Cosmetic customization systems.

* Advanced upgrade pools and complex room layouts.

Evidence Supporting the Hypothesis

* Players immediately begin collecting pellets and moving toward the gate once the required length is reached without needing text instructions.

* Players voluntarily play through multiple room transitions.

* Players replay after failing.

Evidence against the Hypothesis (failure signals)

* Players hesitate or stop moving for more than 5-10 seconds upon entering the first room or reaching the gate.

* Players ignore the pellets and try to bypass the gate immediately without growing their tail.

* Players express frustration or immediately quit after colliding with their tail once or twice.

* Players ask how to open the gate or what the tail is for.

Observations To Record

* Time elapsed before the player collects the first pellet.

* Time elapsed before the player unlocks the first gate.

* Number of tail collisions before successfully clearing the first room.

* Player comments or visible confusion during the upgrade selection event.

* Device/browser performance or loading issues on low-end setups (if tested on target platforms).

Decision Rules

* Continue as planned: If players easily understand the gate mechanic, navigate the tail obstacle with minimal frustration, and express interest in the upgrade choice.

* Iterate before expanding scope: If players struggle to navigate the tail (requiring tuning of tail growth rate or room size) or if the gate-unlock requirement is visually unclear (requiring better visual cues).

* Pivot the tested loop: If the self-generated obstacle is fundamentally frustrating to the target persona, requiring a shift away from classic Snake collision rules.

* Stop or park the concept: If the core loop fails to engage playtesters or causes immediate exit triggers across multiple iterations.

Non-Goals

* Do not try to prove long-term retention systems (like the daily return hook).

* Do not build or test the cosmetic expression system.

* Do not optimize performance for high-end graphics or implement complex audio systems.

Ideation Sources Used

* Phase 1 Setup (Persona, Experience Goals)

* Phase 2 Reference Trinity (Snake, Archero, Pac-Man 256)

* Phase 3 Elevator Pitch (Core Conflict, TikTok Moment)

* Phase 3.5 Value Attributes (Attributes 1-6)

* Phase 4 Value Curve + ERRC (Preserve/Create/Raise decisions)

* Phase 5 Implementation Briefing