NexusTimer is an advanced speedcubing manager built around hierarchical statistical analysis,
with independent metrics tracked at both the category and the individual cube level.
Report Bug
·
Request Feature
NexusTimer is a speedcubing timer and analytics tool. It started as a project inspired by Twisty Timer and grew into a full environment for timing solves and studying performance in depth. The interface keeps your data in the foreground: times, averages, and trends are the content, and everything else stays out of the way.
Speedcubing is the practice of solving the Rubik's Cube as quickly as possible. The clip below shows a solve by Feliks Zemdegs.
Most timers only track statistics by category. Every 3x3 solve lands in the same pile no matter which cube you used, so the moment you switch mains the history of the old cube dissolves into one shared average. There is no way to look back and ask what you actually achieved on a specific cube.
NexusTimer keeps statistics at the individual cube level as well as by category. Each cube holds its own records, averages, and full solve history, and that record stays intact as the years pass. When you think back to an old main you retired long ago, you can still see the bests you set with it, the averages you held, and every solve you logged on it. The category view remains for the aggregate picture, but the per cube history is what turns a retired puzzle into something you can actually revisit.
Every account generates a public profile, and it is one of the most complete a speedcubing app exposes. It brings together your personal bests by category, your solve history and trends, the cubes you own, and your trajectory over time, so a profile reads as a full picture of a cuber rather than a single headline average.
That depth is what makes the social layer worth using. You can open another cuber's profile and compare it against your own metric by metric, connect with other people, and measure yourself on community leaderboards. Data analysis is the core of the project, and these features give that data a purpose.
The diagram below outlines the infrastructure and the main components that sit behind NexusTimer, from the client and its offline first persistence layer to the services that handle accounts, solve storage, and the real time features. It is meant as a high level map rather than an exhaustive specification, enough to understand how the pieces fit together before reading the source.
NexusTimer is translated into seventeen languages, with English as the default fallback and every other locale deep merged on top of it, so a missing string in one language quietly falls back to English instead of breaking the interface. The application is currently available in English, German, Spanish, French, Hindi, Japanese, Korean, Portuguese, Russian, Chinese, Ukrainian, Italian, Polish, Indonesian, Vietnamese, Thai, and Filipino.
Contributions are welcome, whether a bug report, a translation, a fix, or a new feature. Please read the Contributing Guidelines before opening a pull request so your change matches the project conventions.
This project is licensed under the GNU General Public License v3.0. See the LICENSE file for the full terms.