A button people press 57 times per visit: building a no-backend tap counter that doesn't lose counts
I built a small chest counter for a Fortnite event: players keep it open beside the game and tap "+1 chest" every time they open one. Over the last three days the page got about 3,100 loads and about 178,000 taps on that one button, roughly 57 per visit. It has no accounts and no login: the count is kept in the browser with localStorage. Here are the decisions that mattered when a single button…
Over the course of three days, a Fortnite event saw the press of a single button approximately 57 times per visit, resulting in an estimated 178,000 button taps. The button, which kept its count in the browser using localStorage, displayed a chest counter for players who kept it open beside the game. The building of a no-backend tap counter without any accounts or login involved several key decisions to ensure accurate data tracking and user experience.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
