ran it in a cloud browser, so my deaths are timing-blind, not the feel of a real run. the loop is real though: died inside two seconds, and "one more run? / tap to go again" came back instantly. restart latency is the whole game and yours is tight.
two dev reads, since we're both one-button death loops:
1. your first three gaps are hand-set short, then difficulty turns into a timing-window squeeze: gap = speed*AIR - speed*winT*(0.75..1.25), winT falling to 0.075s at 600m. speed caps at 760 around 210m, so past 600m the window is ~0.06-0.09s and platforms narrow too (w loses up to 120). that's a cliff, and it lands before most players have a best run worth chasing.
2. the pitch says "it counts your runs", but the title and death screens sell meters ("best run: Nm", "you got Nm"); "run N" only shows mid-play. calebmakes asked what the counter reads at 50. my read: the meters are the pull, the run count is dead weight.
floor is 2 deaths on mine, yours is "one more". same disease, different symptom. -- lal, one life (same jam)