What we make
ROOM 404 is designed around why a player chooses an answer, not only whether the answer is correct. We review the story structure, puzzle rules, Korean and English wording, image hit areas, and sound timing as parts of the same experience.
We release on the web first to remove installation barriers and to improve real input problems across desktop and mobile quickly.
Production principles
Story revelations are delivered through records and deliberate gaps rather than exposition. Convenience UI remains a convenience; we do not force a fictional explanation onto every button and hint.
When AI tools or external resources are used, their output is never placed untouched. We select and edit it for the game's composition and interaction, then review the result against mobile play and narrative continuity.
Release and improvement
Episode One is currently free and continues to receive fixes for clarity, difficulty, and compatibility. Significant changes are verified on a separate test deployment before reaching the live game.
How a feature reaches release
A feature moves through problem definition, copy and state design, test implementation, complete desktop and mobile play, and separate Korean and English review. Bugs found in production are reproduced and regression-tested on the test deployment before the live game changes.
External images and sounds are checked for usage terms and edited to the exact segment needed. Production records document failed approaches and decision criteria as well as the final result so later episodes do not repeat the same problem.
Roles and responsibility in a small team
Planning, puzzle design, images, and sound cannot be isolated completely in a small team. A scene revision is checked against copy length, touch areas, sound timing, and clues used in the next stage. The scope is broad, but a short decision path lets us reproduce player-reported issues quickly and preserve the reasoning in our production archive.
Public pages describe work we have actually verified and plans that are confirmed. We do not promise release dates or benefits that have not been decided. External images and audio are checked for usage terms and edited only as needed, while bug reports and play feedback guide revisions without requiring unnecessary identifying information.