Notes from the desk
The ranking has to stay short, so the reasoning lives here. These pieces cover how a score is set, what a progression curve owes a player, why a controller listing can mean six different things, and how a difficulty curve teaches without a single pop-up. Nothing below names a specific game — the ranking on the front page does that.
| Date | Title | Reading time |
|---|---|---|
| Day Thirty: What Actually Brings A Player Back Why our desk judges longevity by day thirty rather than hour one, and the three mechanisms that keep a player coming back. | 7 min | |
| What a Progression System Owes the Player Capability unlocks, content unlocks and magnitude unlocks, and how to tell a curve that gives something back from one that only asks for time. | 8 min | |
| Reading A Game's Controller Support Before You Commit To It A ten-minute audit for telling a finished gamepad implementation from a half-built one. | 7 min | |
| Teaching Without a Tutorial: What Good Escalation Looks Like How a well-built difficulty curve teaches through level order rather than pop-ups. | 7 min | |
| A Field Guide To Puzzle Subgenres Six puzzle families, what each asks of a player, and where each tends to fail. | 8 min |