Pachinkremental

Most incremental games generate their currency from an abstract number going up. Pachinkremental generates it from an actual physics simulation: drop a ball into a real pachinko board, watch it ricochet off pegs on its way down, and whatever slot it lands in pays out. The payout buys upgrades that change the board itself — more multipliers, better slot values, new machines entirely — which loops back into better runs. It's a clever, well-executed idea, and the incremental-games community has treated it that way: separate release threads for v1.0 and v2.0, two years apart, each drawing over a hundred comments. This is not a proof-of-concept; it's a maintained project with real staying power.

The click works. The board doesn't fit.

The instinct going into this review was to check whether Pachinkremental's single required action — clicking to drop a ball — actually fires from a touchscreen, since the author's own README already admits the mobile experience is rough. It does fire: a real simulated tap on the game's canvas correctly triggered OnClick, dropped a ball, and flipped the game's internal game_started flag exactly as a mouse click would, through code with no touch/mouse branching at all. That part of the author's engineering holds up.

What doesn't hold up is what happens to the board itself. Measured directly rather than guessed from a screenshot, the pachinko canvas renders at roughly 90 by 138 CSS pixels on a 390-pixel-wide phone viewport — and the identical page, loaded in a desktop browser window, renders the same canvas at roughly 470 by 760. That's better than a twentyfold difference in usable area for the one thing this entire game is built around. Pachinko already asks for some precision — aiming a drop to land in a specific scoring slot between rows of pegs — and asking for that precision inside a target smaller than a postage stamp is a different, much harder game than the one the desktop version offers. Confirmed testing also found that only the top strip of that already-tiny board accepts a drop at all, which is correct to how pachinko works but leaves an even smaller functional target once you account for it.

The upgrade panel makes the mobile story worse rather than better. Reading upgrades.js confirms every upgrade's description is wired to onmouseenter/onmouseleave with nothing else backing it up — no touch listener, no tap-to-toggle, no long-press. A phone player sees an upgrade's name and its cost and nothing about what it does, which matters a great deal in a game whose entire second half is deciding what to buy next.

Should you play it

On a desktop, yes — this is a smart, well-loved take on the incremental genre with real community-tested depth behind it. On a phone, the exact device class this shelf exists to serve, the core interaction survives but the board it happens on doesn't, and that's enough on its own to keep this off the list until the layout gets real mobile attention.