Four Browser Games Built for One More Go

A run has to be short enough to lose twice

The games people keep open in a browser tab are not the ones with the most content. They are the ones where losing costs almost nothing. A run ends, and the next one is already there — no menu, no ad, no loading bar between you and the retry.

Four new games here are built on that idea, and each solves it with a different number. Below is what those numbers actually are, pulled from the rules the games run on.

Tap Fly — the clock does the balancing

A pipe arrives every 1.27 seconds at the start and every 0.90 seconds once you are past thirty points, because the world speeds up from 150 to 210 pixels a second. Ten pipes take about twelve seconds, which is the whole point: a run is over before you have decided whether you are enjoying it.

The gap starts at 130 pixels and narrows by 2 for every pipe you clear, stopping at 100 — about four times the bird. It reaches that floor at fifteen points, so from there the game stops getting harder and simply stays hard. Difficulty that keeps rising forever ends a session; difficulty that levels off invites one more.

Stack Tower — a comeback rule, not a death spiral

The block sweeps the 320-pixel board in 0.89 seconds at top speed, which it reaches at floor 50 (160 pixels a second at the start, plus 4 per floor). Land within 6 pixels of the block below and it counts as perfect: nothing is trimmed off, and the combo goes up.

Six pixels on a 200-pixel block is a three percent window, and that tolerance is the entire feel of the game. Most stacking games only take width away, so a bad tap in the first minute decides the run. Here five perfects in a row give ten pixels back per perfect, up to the original 200 — a narrow tower is a problem, not a verdict.

Bounce Ball — you gain one ball while the wall gains three

Every turn a new row drops in. Six of its seven columns each hold a brick with 45 percent probability, one in six of those bricks has doubled health, and every row is guaranteed exactly one pickup — so your ball count climbs by one per turn, on a line.

The wall does not. A row arriving on turn twenty is made of bricks worth twenty hits each, so the health arriving each turn averages about 3.1 times the turn number, while your ammunition equals the turn number. Each ball has to land roughly three hits just to break even, and that is why the game turns from aiming into geometry — you stop aiming at bricks and start aiming at the corridor that keeps a ball bouncing.

Fruit Merge — the only one with no clock at all

Eleven sizes, each pair merging into the next: cherry, strawberry, grape, orange, lemon, apple, pear, peach, pineapple, melon, watermelon. Built strictly from the bottom, one watermelon is 1,024 cherries and 4,017 points, which is a number nobody reaches on purpose.

Nothing here is timed. The pressure is spatial — the jar fills, and a fruit resting above the line for a second and a half ends the run. That inverts the other three: they punish a slow hand, this one punishes a slow plan, and it is the one that eats an hour without ever feeling fast.

Which one, and for how long

Waiting for a lift: tap fly, because a run fits in the wait. One song: stack tower. A bus ride: bounce ball, which is the only one of the four where a turn is worth thinking about. An evening you meant to spend otherwise: fruit merge.

All four run in the browser with nothing to install, keep their best score in your own device and send nothing anywhere. If you want the older set, there is a round-up of four classics in the browser and, before that, five games for a boring afternoon.