📓 The GameHanpan Blog
Dev notes from the people who actually build these games: difficulty-tuning postmortems with the real numbers, the math hiding inside classic puzzles, design diaries and technical essays. Everything here is first-hand — no reposts, no filler.
How We Tuned Space Canyon's Difficulty (A Postmortem)
The exact physics constants we changed after "too hard" feedback, and the autopilot simulation that took average runs from level 2.9 to 7.5.
🧩The Math Behind 2048: Why the Corner Strategy Works
90/10 spawn odds, why a win takes about 930 moves, the 131072 ceiling, and the monotonicity argument behind the corner strategy.
🌸Designing Bloom Blocks: Making a Falling-Block Puzzle Cozy
A design diary: the pastel garden theme, a Zen mode with no game over, and what mobile swipe controls taught us the hard way.
⚡Reaction Time by Age: Benchmarks and How to Improve
What happens inside your ~250 milliseconds, honest benchmarks by age, how our test measures you, and what training can really change.
🐍Snake: From Nokia 3310 to the Browser
Fifty years of the most durable design in games — plus our own grid, speed curve, and the tail rule most clones get wrong.
🧰Why We Build Browser Games With No Frameworks
Seven games, ~74 KB of hand-written JavaScript, zero dependencies, zero trackers. A technical essay on the case for vanilla.
Why this blog exists
Most game-site articles are interchangeable tips lists. We wanted the opposite: articles only we could write, because they come out of building and tuning the games on this site. When we quote a gravity constant, a spawn probability or a speed curve, it is the real value from our source code — and when we describe a mistake, it is one we actually made. If an article makes you want to test a claim, the relevant game is always one click away, free, with no install and no sign-up.