Problem
A game project needs both a public entry point and a playable client.
Work
W04
garden0
A game project with Unity work, mobile controls, release checks, and a web landing page.
Story
garden0 moves from a landing page into a playable browser preview.
Constraint
The public case is limited to owned captures and progress evidence from the project folder.
Approach
Show the landing page as the entry point. Show the Unity menu and gameplay capture. Keep browser preview evidence tied to the same game project.
Outcome
The case carries a small game from public page to playable preview.
Human stake
For a game, the interface promise only matters when the world can be entered.
Blocked person
A player who needs to know whether the world is more than a landing page.
Confusion
A game can look public before the playable client is visible.
Made visible
The progression moves from landing capture to Unity client and browser preview.
Evidence
Unity gameplay and landing captures show the project moving from public page to playable client.
Problem
The landing page has to lead somewhere.
The landing capture sets the outside face, but the case needs a playable client behind it.
Landing still / Owned captureOperate
The reel crosses into the client.
Owned captures move from public page to Unity and browser preview.
Playable capture / Owned captureDecision
The playable client carries the case.
The Unity capture carries the case because it shows the project as a game client.
Playable capture / Owned capture
Receipt
Landing to gameplay stays connected.
The result is a small authored progression from public page to playable evidence.
Browser preview / Owned captureResult
What changed
- garden0 shows the public page, Unity client, and browser preview as one game project.
Claims
Public claims kept inside the available evidence.
- Unity menu capture
- Landing page capture
- Browser preview capture
- Progress log with lint, build, iOS export, and mobile checks