Web Dashers Update Log: Roadmap, Releases and What Comes Next

Web Dashers ships in the open: a public repository, a stated roadmap and releases that land where players can watch them. This page is our running log of that development — what the project has built, what it has publicly committed to, and how to read its momentum as a player deciding where to spend your browser hours.

The Public Roadmap

The project's own words are the best starting point: the goal is a fully working level editor, with all of the objects in Geometry Dash to choose from, and more. That single sentence tells you the priorities — editor completeness first, object depth second, and room for original ideas beyond parity. Around that anchor sit the quieter commitments every fan project makes by existing: level pool growth, stability, and keeping the whole thing free and instant in the browser.

Reading any fan roadmap deserves a specific mindset: treat it as direction, not dates. Volunteer projects move in bursts — a quiet month can precede a release that changes everything. The signal worth tracking is the repository's activity itself, which brings us to how releases actually land.

How Releases Land

Because Web Dashers lives on GitHub Pages, development and deployment are the same motion: changes merged to the project publish to the live site. There is no store approval, no staged rollout, no version gate — players see updates the moment they ship. The practical consequence for you: hard-refresh the page now and then, because the version you are playing is simply the latest one merged. When something feels new mid-week, it is not your imagination — it probably is.

What We Are Watching

Editor depth. Each expansion of the object set directly expands what community levels can be. This is the roadmap's center of mass and the single best predictor of the level pool's future quality.

Level search maturity. As the community grows, richer filtering and discovery decide whether the search stays navigable. Watch for any movement here — it quietly shapes the whole play experience.

Performance and input. Browser rhythm games live or die on input latency. Maintenance commits that touch performance are the unglamorous heartbeat of the project; steady pulses there mean the foundation is being kept honest.

Community momentum. Search interest in Web Dashers has climbed sharply through recent weeks — the flywheel of new players, new authors and new levels is visibly turning. Roadmaps are promises; a growing player base is proof.

How to Read Future Updates

When an update lands, ask three questions. What can the editor do now that it could not before? What changed in the search and discovery flow? And did anything move on performance or input feel? Those three answers capture almost everything that matters to a player, and they are exactly what this log will track as releases arrive — dated, summarized and translated into what-it-means-for-you.

FAQ

Where do updates get announced? Through the project's repository and its community channels; this log mirrors and summarizes them here.

Do updates wipe progress? Browser-based progress is tied to your local storage — major releases occasionally reset specifics, but the project treats player progress as precious.

How can I contribute? Fan projects grow on three fuels: playing, authoring levels for the search pool, and — because it is open — contributing directly. The first two need no permission.

Bookmark this log, hard-refresh the game now and then, and enjoy watching a fan project earn its momentum in public.