Why we build cozy games
Relaxing is harder to build than exciting, not easier. That sentence took us a while to believe, and a few prototypes to prove.
There is a quiet assumption in game design that intensity is the hard part, while calm is what you get when you stop trying: build a tense game, remove the difficulty, and you have a relaxing one. We think that is backwards. A few years of watching players bounce off our prototypes convinced us of it, though I should admit that most of the evidence was people quietly closing the tab.
Excitement hides flaws. Calm exposes them.
A fast game with a rough edge gets away with it. The player is moving quickly, the stakes are immediate, and there is no time to notice that a collision sound is two frames late or that a button has no hover state, because there is no moment in which the player sits still long enough to be annoyed by any of it. Adrenaline is a very effective mask. I have shipped things with exactly those flaws in them and heard nothing from anybody.
Take away the pressure and every one of those rough edges becomes the experience, because if a player is meant to spend twenty minutes inside a calm loop then the feel of that loop is the game. There is nothing else to fall back on. No scoreboard. No countdown. Nothing to hide behind.
This is why most of our development time goes into things players never consciously register: how long a stone keeps moving after it lands, how far a merge bounces, whether consecutive sounds sit in key with each other, or whether the fifth chime in a row lands a half step off, which sounds like nothing and feels like sandpaper.
Nobody writes a review about that. They just stop playing.
The awkward part is that none of it shows up in any metric you would normally track, since a player who leaves because a bounce felt wrong does not file a bug report: they close the tab and think, vaguely, that the game was fine but not for them. We have learned to read that sentence as a technical complaint.
Calm needs a reason to continue
Tension is a cheap progression engine. If the player is afraid of losing, they will keep playing, and you barely have to design anything else, which is why so much of this industry runs on fear and why taking it out leaves a hole you can only fill with real work. Remove fear and you have to replace it with something, which in our experience means one of two things: curiosity, or craft.
Curiosity is the pull of “what happens if I keep going”. The next stone shape, the next colour, the next thing that unlocks. Craft is the pull of “I could do that better”, the sense that the last run was winnable and that you know exactly how you threw it away.
Pebble Merge leans on both: an eleven-step ladder of materials to discover, and a placement skill that is obviously improvable. I like that pairing because the two motives run out at different times, and when discovery is exhausted mastery usually is not, so the handover between them is what decides whether somebody plays for a week or for a month.
What we deliberately avoid is the third engine: obligation. Streaks, daily rewards that punish a missed day, notifications framed as loss. These turn a calm game into a chore wearing a calm art style. The mechanics matter more than the palette, and I am mildly irritated that this still has to be said out loud.
The five-minute test
Our practical test is simple. Open the game, play for five minutes, close it, and ask how you feel. Not “was it fun”, because that is far too easy to answer yes to. Ask whether you feel calmer or more agitated than when you started, and answer honestly, because the honest answer is often that you feel neither and merely notice that five minutes went somewhere.
A surprising number of games fail this while being genuinely well made: losing that should feel like a full stop instead feels like a setback, a reward animation that should feel satisfying instead feels like a demand to keep going, and an ad break arrives at the exact moment the player was winding down. None of these are bugs. All of them are decisions, and most of them were made by somebody looking at a retention chart.
We run the test badly sometimes. If I have been staring at a build for hours, I cannot tell calm from numbness, and my answer is worthless. So we try to do it in the morning, or not at all.
What cozy is not
It is not a palette. Soft colours and rounded shapes do not make a game restful, and we have played plenty of pastel things that left us tense. Cozy is a contract about what the game will not do to you. It will not punish you for leaving. It will not surprise you with a timer. It will not pretend that a missed day was a mistake you made, which is the specific trick that turns a game you liked into an appointment you resent, and it works so reliably that I understand why nearly everyone reaches for it.
It is not slowness for its own sake either, since a calm game can run at a brisk tempo and some of the most restful loops we know are fast ones. What makes them restful is that the outcome was never unfair and that stopping was always allowed, every time, with no penalty screen and no guilt message and no countdown you cannot pause. That is a design property, not a tempo.
What we gave up
Choosing calm means giving up the mechanics that retain players most reliably: no energy systems, no timed events, no social pressure, no loss-framed notifications, none of the machinery whose entire purpose is to make a retention graph bend upwards. Our retention numbers will be worse than a game that uses them. We are fine with that trade, or at least we are on the days when we are being honest about why we started doing this.
We would rather be the game someone returns to because they want to than the one they return to because they were told to.
Whether that is commercially sustainable is an open question we are still answering, and we will publish what we find, including if the answer turns out to be no. I genuinely do not know which way it goes, and I would rather find out from numbers than from conviction, since conviction is the thing that got us into this position in the first place.