About the project
Why BitReach exists
BitReach is an independent English browser game for one durable educational task: understanding how raised and lowered fingers can represent binary numbers. It combines two directions that are often separated. A player can construct a displayed decimal target by selecting weighted fingers, then read a displayed gesture back into decimal. Starter, eight-bit, and ten-bit ranges carry the same rule from zero through 1,023.
A complete practice loop, not a camera demo
The game intentionally avoids camera recognition. On-screen fingers make the whole experience deterministic, private, keyboard operable, and available on a phone without asking for hardware permission. Each short run begins with a setup choice, continues through multiple generated questions, gives a result, and supports immediate replay. A wrong answer identifies every incorrect place value instead of providing only a total score.
Original clean-room direction
Discovery began from evidence that people searched for a binary finger counting quiz. The resulting implementation was specified and written independently. It does not reuse the discovered Windows tool's name, executable, source code, camera logic, art, tutorial copy, screenshots, or challenge sequence. Binary place values are mathematical facts. BitReach's visual identity, generated production illustration, HTML/CSS hands, adaptive counter, question generator, feedback text, and page copy are original to this project.
Scope and limits
BitReach is casual practice, not a validated assessment, course grade, certification, or promise of learning outcomes. The adaptive review is deliberately simple and transparent: missed bit positions gain priority and correct bit decisions reduce it. The site stores only aggregate local counters and the last setup. It does not create accounts, upload answers, or request a camera.
Ownership and contact
The project operator publishes a support route through the public GitHub profile. Use it for reproducible bug reports, accessibility barriers, factual corrections, privacy questions, or licensing concerns. Do not post passwords, precise location, payment details, private student records, or other sensitive information. Runtime library and generated-asset notices appear in the project’s THIRD_PARTY_NOTICES file.