BUILDING IN PUBLIC

DEV
LOG.

BeatMyScroll started as a tiny “how long can you keep scrolling?” prototype. This page documents the real changes that turned it into a competitive browser game, including the experiments that were replaced when they did not feel good enough.

2026

THE BUILD SO FAR

OCT 24

BeatMyScroll 2.0 becomes a mechanics benchmark

The project expanded beyond the original scroll event into a mouse-first esports mechanics lab. Added six benchmark events: Reaction, Flick Acquisition, Tracking, Target Switching, Micro Precision and Click Burst. Results combine into a weighted 0–2000 BMS Rating with persistent local profiles, Cloudflare-synced personal bests, public player pages, an overall leaderboard and individual event leaderboards. Classic Scroll moved to its own preserved event.

BMS 2.0ESPORTSBENCHMARKPROFILES
OCT 17

Daily objectives and Overdrive

Added rotating Daily Challenges, local completion streaks, sustained-speed OVERDRIVE and post-run achievement medals. Overdrive is intentionally a visual/progression objective rather than a score multiplier so existing competitive records remain comparable.

REPLAYABILITYOVERDRIVEDAILY
OCT 17

Live data becomes part of the site

Added public statistics, expanded records and a community benchmark API derived from the existing opt-in leaderboard. The site now separates “submitted leaderboard runs” from anonymous plays instead of inventing a total-play count we do not collect.

STATSBENCHMARKSCONTENT
OCT 17

The tunnel stops pretending to be 3D

The first corridor used CSS perspective and looked more like stacked wireframe rectangles than a space the player occupied. It was replaced with a projected canvas renderer that takes 3D coordinates, projects them into screen space and moves corridor rings, particles and a rotating wireframe object toward the camera.

3DCANVASPERFORMANCE
OCT 17

PB Ghost racing

Personal bests stopped being just one number. New PBs now save a lightweight local score timeline. During the next run, the game can show whether the current player is ahead of or behind the old run at the same elapsed time, including a PB OVERTAKE moment.

REPLAY DATARIVAL SYSTEM
OCT 17

Arcade feedback pass

Added D through SSS live ranks, score zones, CLUTCH SAVE feedback, run grades, post-run titles and escalating RUSH streak callouts. These systems were intentionally layered on top of the existing scoring formula so old leaderboard results stayed comparable.

GAME FEELRANKSRUSH
OCT 8

Legacy-device performance mode

Older devices were struggling with filters, speed-line transforms, eager media loading and high-frequency DOM updates. The game gained lazy audio/media loading, adaptive rendering, HUD throttling, static asset caching and a Lite Mode that can activate automatically when frame timing drops.

OPTIMIZATIONLITE MODE
OCT 8

AdSense rejection changes the homepage

An early monetization layout treated the start/results states too much like ad-adjacent utility screens. Advertising was restricted to the content-rich landing page, gameplay and game-over were made completely ad-free, and the site gained real navigation, privacy, legal and explanatory content.

MONETIZATIONUXPOLICY
OCT 7–8

Global leaderboard

Added an opt-in username system backed by a Cloudflare Durable Object. Each registered browser can maintain best raw score, best average speed and best max speed, with separate Top 15 boards shown after runs.

CLOUDFLARESQLLEADERBOARD
OCT 7

Audio stages and reliability work

Speed milestones gained music and visual moments. The first audio implementation was unreliable on some phones because playback permission could be lost between a gesture and asynchronous element creation. Audio elements were moved to deterministic first-gesture unlocking with retry logic and lazy loading for large tracks.

AUDIOMOBILE
OCT 6

BeatMyScroll goes live

The original static prototype was connected to GitHub and deployed through Cloudflare. The earliest version already had the core idea: continuous input, an inactivity death timer, raw score and speed acceleration. Everything since then has been built around making that tiny loop feel worth replaying.

LAUNCHGITHUBCLOUDFLARE
NEXT

WHAT STILL NEEDS WORK

The project is intentionally not “finished.” Device normalization can always improve, the projected 3D scene still has room for stronger solid geometry, and the community-data layer will become more informative as more people choose to submit runs.

Changes that alter competitive scoring are treated more cautiously than visual changes because maintaining comparability with existing records matters. When a future mechanic genuinely changes scoring, it should be versioned clearly rather than silently moving the goalposts.

REPORT A BUG OR IDEA →