Designing Bloom Blocks: Making a Falling-Block Puzzle Cozy
The world did not need another falling-block puzzle. It has had a perfect one since 1984, and ten thousand imitations since. So when we started Bloom Blocks, the question was never "can we build one?" — the genre's mechanics are famously well documented — but "who is being left out by the way these games usually feel?" This is a diary of the answer we landed on: a falling-block puzzle designed to be cozy, and what that one word ended up changing about the palette, the pacing, the fail state and the touch controls.
Who we were building for
Watching people play our other games, we noticed a pattern: plenty of visitors loved short puzzle sessions but bounced off anything that looked like an arcade cabinet — dark backgrounds, neon glow, sirens of urgency. The falling-block genre is mechanically gentle (no enemies, no aiming, no timer except gravity itself), yet it is almost always dressed in stress. We wanted the opposite dress: something you might open to wind down before bed, not to spike your pulse. We deliberately aimed at casual players, and especially the players — disproportionately women, if industry surveys about puzzle audiences are to be believed — that arcade styling quietly tells "this is not for you."
Pastel is a mechanic, not a coat of paint
The first decision was the garden metaphor: pieces as flowers and petals, the board as a plot you tend, line clears as blooms with a soft sparkle instead of an explosion. The pastel palette followed from a practical constraint as much as a mood: seven piece types must stay instantly distinguishable while none of them may shout. That is genuinely hard with soft colors — desaturate too far and pieces blur together, keep saturation and you are back to neon. We ended up nudging hue spacing wider than a classic block-puzzle palette to keep pieces readable at low saturation. We also banned screen shake entirely and kept the clear animation to a gentle glimmer, because a cozy game that flinches at you isn't cozy.
Zen mode: deleting the fail state
The heart of the game is a mode with no game over. In Zen mode, pieces fall at a constant, relaxed 850 milliseconds per step — forever. There is no level counter ticking up (the level display literally shows ∞) and the speed never changes. And when the stack does reach the top, the garden is gently cleared and play simply continues, with a soft message rather than a failure screen. Your score keeps counting. The board resetting is framed as the garden being replanted, not as you being judged.
This was the most argued-over decision in the game's development. Doesn't removing failure remove the point? In practice, no — it relocates it. Zen mode still scores lines, and Zen keeps its own separate best score (stored under its own key in your browser, apart from Classic's), so there is still something to beat; you just can't be punished while trying. What surprised us in testing was session length: people played Zen longer than Classic, not shorter. It turns out the tension of an approaching top-out was pushing players to quit "before dying." Take away the death, and people stay in the garden.
Classic mode: familiar numbers on purpose
Next to Zen, we kept a Classic mode that is deliberately conventional, because a cozy skin should not mean unfamiliar rules. Scoring follows the traditional table — 100, 300, 500 and 800 points for one to four lines, multiplied by the current level — and you level up every ten lines. Speed starts at 700 ms per step and tightens by 55 ms per level down to a floor of 90 ms, so around level twelve the game is as fast as it will ever get. Anyone who has played any falling-block game in the last four decades can read those numbers with their hands. The two modes share one board, one piece set and one control scheme; only the pressure differs.
The hard part: touch controls
The genuinely difficult engineering in Bloom Blocks was not the game logic — line clearing is a solved problem — it was making one finger do the work of six buttons. On a keyboard you have arrows for move, rotate and drop. On a phone screen we had to disambiguate: a quick tap should rotate, a horizontal drag should step the piece sideways, a downward swipe should drop. The failure modes are maddening: set the drag threshold too low and every sloppy tap becomes an accidental sideways move; too high and the piece feels glued. A downward flick read too eagerly slams a piece you were still positioning.
We tuned thresholds by feel over many rounds, and then did something less proud but more honest: we added on-screen buttons anyway. Gesture purism is lovely until you watch someone play one-handed on a bus. The buttons and the gestures both work, all the time, and each player gravitates to their own mix without being told. If there is one transferable lesson from this project, it is that redundant controls are not a design failure — on mobile they are a courtesy.
What we would do differently
If we revisit Bloom Blocks, the wishlist is short: a daily-garden variation, an even slower "evening" Zen speed, and perhaps ambient sound — the one cozy ingredient we left out to keep the page light (the whole game is about 21 KB of JavaScript, the largest on the site but still smaller than most single images). Until then, the garden is open: Classic if you want the old pressure, Zen if you have had enough of it today. No install, no account, and nobody watching you top out.