Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

When I walked through Quiet Museum, I found myself watching how you handled silence and space, and that lens shapes my entire reading of your project.

Fun 

You built something that leans away from twitch mechanics entirely, opting instead for a quiet, contemplative pace where I wandered through spaces relying on environmental cues and spatial audio. As an atmospheric experiment, I found it engaging, though the moment-to-moment interaction loop is intentionally sparse, which keeps it from feeling like a traditional, high-energy game.

AI Use 

I appreciated how transparently you leaned into AI, using Gemini to generate versions of public-domain paintings and Claude to handle code architecture and build assistance during the week. It struck me as a pragmatic, well-scoped deployment that acted as a true solo-dev crutch rather than an incoherent asset flood, successfully supporting a tight browser build.

Polish 

You built this in Three.js with custom voice work and focused audio design, and the whole experience holds together with surprising neatness for a solo jam entry. Your strict adherence to zero on-screen text, aside from basic control prompts, gives it an austere, gallery-like finish, though the visual assets inevitably carry that distinct AI-generated sheen.

Theme 

You tackled the gallery concept and the strict no-text restriction by turning the entire interactive space into a silent exhibition. While playing it safe by sticking literally to the museum metaphor rather than finding a more subversive angle is a choice, you respected the core constraints of the prompt down to the letter.

(+1)

well , i was trying to play human nature that they won't be quiet.

so someone who don't follow the cue will be stuck in a loop.

i know atlas got out and you too.

DG never got out😅