06 / Desktop product / collaboration
Building four versions of chess with a friend
A collaborative Electron game with four themed editions, more than 11 variants, reactive procedural audio, custom mechanics, and a packaged Windows build.
Starting point
Where it started
The goal was to make each version of chess feel distinct without depending on a server or bundled audio library.
What I did
What I worked on
- Collaborated on four editions with separate mechanics and visual identities.
- Built synthesized soundtracks that react to captures, checks, pressure, and game state.
- Added variants, analysis labels, achievements, and optional Discord presence.
- Used smoke tests and build scripts to prepare a desktop release.
Result
What changed
The shipped app demonstrates collaboration, product polish, state-heavy front-end work, testing, and release discipline.
What I learned
What I took from it
- State bugs hide in the interactions between systems.
- Procedural audio can create identity without a large asset footprint.
- A launcher has to explain the product before the first move.
Next case study / 01