Posted at 2026-09-12 05:25:27 — Link

There's a specific kind of game that ruins your evening plans without ever raising its voice. No timers screaming at you, no boss health bars, no tutorial character explaining what a button does for eleven minutes. Just fruit. Falling, slowly, into a box.

If you've spent any time on streaming platforms or gaming forums in the last couple of years, you've probably seen someone hunched over a screen full of cherries and grapes, muttering about a strawberry that landed two pixels off course. That's the watermelon puzzle — most widely known asSuika Game, where "suika" is simply the Japanese word for watermelon. It became a phenomenon partly because it's charming, and partly because it's the kind of thing you can explain to someone in fifteen seconds and then watch them lose an hour to.

I want to walk through how it actually works, and then share a few things I only figured out after a lot of embarrassingly low scores.

How the Game Works

The setup is almost insultingly simple. You have a container, roughly the shape of a wide bowl or a box with walls. Above it, a piece of fruit appears. You move it left or right along the top, then drop it.

When two identical fruits touch, they merge into the next fruit up the chain. Two cherries become a strawberry. Two strawberries become a grape. Grapes become a dekopon, then an orange, an apple, a pear, a peach, a pineapple, a melon, and finally — the goal — a watermelon. Two watermelons merging is the rare, glorious moment that makes the whole thing feel worthwhile.

Every merge earns points, and bigger merges earn considerably more. So the scoring naturally pushes you toward building large fruit rather than just clearing space.

The catch is physics. The fruits are round, they roll, they wobble, they settle into gaps you didn't intend. A perfectly reasonable plan can collapse because an orange rolled three centimetres to the left and wedged itself between two apples. There is no undo. There is no pause-and-reposition. The container fills up, and if fruit spills over the top line, the run ends.

That's the entire game. No unlockables, no upgrade trees. Just you, gravity, and an increasingly cramped bowl of produce.

Things I Wish I'd Known Earlier

Sort your fruit by size, not by convenience. The single biggest improvement to my scores came from treating the container like a shelf. Big fruit goes on the bottom, small fruit stays near the top. If you drop a cherry into a deep pocket underneath three apples, that cherry is effectively lost — you'll never get a second one down there to merge with it. Building large at the bottom gives you a stable foundation and keeps the small stuff accessible.

Pick a side and commit to it. Many strong players keep one wall as their "big fruit" side, gradually stacking larger fruits there, and use the opposite side as a working area for cherries and strawberries. It sounds fussy, but it prevents the worst outcome: a random scatter of medium fruit with no clear merge path anywhere.

Watch the preview. The game shows you what's coming next. Ignoring it is the most common beginner mistake. If you know a strawberry is coming, don't drop your current cherry in a spot that will block it. Two seconds of planning is worth more than fast reflexes here.

Use the walls. Dropping fruit hard against a wall makes it roll less. Dropping it in the middle of a crowded field is a gamble. When you need precision — and you often do — the edges are more predictable than the centre.

Chain reactions are free points. When you set up a stack where one merge triggers another, and another, the score climbs fast without costing you any space. Look for opportunities where two merges are one fruit away from lining up. This is where the game shifts from reactive to genuinely strategic.

Don't panic-drop. When the container gets full, the instinct is to shove fruit anywhere just to keep going. This almost always accelerates the end. Slow down. There's no clock. Find the one gap that helps, even if it takes you ten seconds to spot.

Accept the bad runs. Sometimes the game hands you five oranges in a row when you needed cherries. Sometimes a melon rolls into exactly the wrong crevice. The randomness is real, and no amount of skill makes every run good. The point isn't to win every time — it's that the failures take ninety seconds and you can immediately start again.

Why It Sticks

I think the appeal comes down to how honest the game is. It never pretends to be more than it is. There's no story trying to make you care, no progression system engineered to keep you logging in. You play because dropping fruit into a box and watching it turn into bigger fruit is quietly, stupidly satisfying.

It also sits in a nice spot difficulty-wise. Anyone can get a watermelon eventually. Almost nobody gets two on their first day. The gap between "I understand this" and "I'm good at this" is wide enough to stay interesting but never feels punishing.

If you've never tried it, give yourself twenty minutes. Drop some cherries badly. Watch a pear roll into a spot that ruins everything. Then do it again, slightly better. That loop — small failure, small adjustment, small improvement — is the whole experience, and it's a surprisingly pleasant way to spend time.

Fair warning, though: your first watermelon will not be your last attempt.