Runner

Late jumps clear more than early ones

Runner gives you two verbs (jump and duck), and the hard part is timing, not reaction speed. Your character sprints forward on its own at a pace that keeps climbing, and nerves push most players to jump the instant they spot a block ahead. Jump too early and you land right on top of the next hazard; the safer habit is to wait a beat and jump late, so you clear the obstacle on the way down rather than clipping the one behind it. Ducking is for the flying obstacles, and the trick there is to hold the duck a fraction longer than feels necessary, since standing up early into a low-flyer ends the run just as fast.

Watch the horizon

As the speed ramps up, obstacles arrive faster than you can consciously react to the one in front of you. The players who go furthest read the spawn point at the edge of the screen and pre-plan the next move, treating the game as rhythm rather than reflex. When a ground hazard and a flyer come close together, decide early whether you are jumping or ducking through the pair. Hesitating between the two is exactly what catches people at high speed.

• Commit to late, clean jumps instead of nervous early ones.
• Hold your duck until the flyer has fully passed overhead.
• Read the far edge of the screen, not the obstacle right in front of you.

The two-obstacle problem

Most deaths at speed come from pairs, so it is worth rehearsing the two shapes they take. Block then flyer: jump the block late, and start your duck the moment your feet touch down, so you slide under the flyer with no wasted upright frame. Flyer then block: duck early, hold it until the flyer is fully past, then release and jump in one motion. In both cases the killer is indecision, switching from jump to duck mid-approach and doing neither cleanly. Decide at the screen edge which pattern is coming, and say it in your head if that helps. At high speed you are not really reacting anymore, you are executing a call you already made half a second ago. Making that mental shift is the difference between dying at the first pair and treating pairs as free distance.

Riding the ramp-up

Every run has three phases, and each one asks for something different. The opening stretch is slow enough to play on pure reaction, and its real job is to let you settle, so use it to practise deliberate late jumps instead of coasting through it. The middle is where the reading starts. Somewhere in this phase your eyes should drift off your character and up to the spawn edge, and players who never make that switch all die at roughly the same speed, right where reaction time runs out. The late game is close to a trance: obstacles arrive on a beat, you call the pattern, execute, and reset. Thinking about anything else, your score, your record, the near-miss two seconds ago, is what breaks it. Runners choke at the exact distance where their record sits because the moment feels different, so they play different. Treat the record line like any other stretch of road and run straight through it.

One button, endless road

The endless runner grew out of a wave of minimalist auto-running games around 2009, when titles like Canabalt proved you could build real tension from a single input and a rising speed dial. Canabalt was put together in a matter of days by designer Adam Saltsman for an experimental game-making challenge, and its one-button rooftop sprint ended up defining a genre. Temple Run carried the formula to phones in 3D, and Google hid the most-played runner of all inside Chrome: the little dinosaur that appears when your internet dies, jumping cacti and ducking pterodactyls with the same two verbs you have here. Google's engineers said in 2018 that the dinosaur was being played around 270 million times a month. The core never changed through any of it: the game runs itself, you just handle the obstacles, and one mistake is the end. There is no finish line. The road keeps unspooling and getting faster, and the distance you rack up before a single collision is the only number that counts.