Otherchess

Development

Roadmap, dev log, and community input

Development

Otherchess is in active beta.

Otherchess is developed by a solo developer. Progress is paid for by Patreon and by backers of Kickstarter campaigns for specific milestones. This page is the governance hub: development goals you can comment on, and a dev log of what’s shipping. Your input shapes what we build next — especially from active players, super testers, and Patreon donors.

Beta focus

  • Ops stability — the app should stay up, deployments should be clean, and no game should be lost to an infrastructure failure.
  • Core functionality — move generation, game resolution, ratings, and history must all work correctly and reliably.
  • Bug reports from super testers — if you play and find something broken, that feedback goes directly into the queue. Paid super tester role here.

Development Goals and Dev Log are below. We weight input from active players, super testers, and Patreon donors more heavily.

Development Goals

Click to see details and join the conversation.

  • Ops stability & core functionality (beta priority) — Service reliability, clean deployments, no bugs.
  • UI/UX — Game summaries, profiles, ratings clarity, alternate piece sets.
  • Tournaments — Online first; over-the-board when ready. Prizes and structure shaped by Kickstarter and community.
  • AI & Evaluation — Stronger play and search in a high-branching game where humans still have the edge.
  • Mobile — Playable on phones and tablets without losing the precision board interaction requires.
  • Cryptographic Game Certificates (CGR / CWT) — Signed certificates for completed games so players can prove outcomes and recover history if the database is lost.
  • Advanced Multiplayer & Board Theory — Fairness scoring, cabal-free configurations, the draw pact mechanism, and mapping the design space of playable boards.

Development is funded by Patreon (steady iteration) and Kickstarter campaigns for concrete milestones (tournament prizes, OTB kit, etc.). Links coming when campaigns are live.

UI/UX

The interface is where the game lives or dies. We’re working on making every page feel clean and intuitive — game summaries, player profiles, ratings clarity, alternate piece sets, and general polish. But we need to hear from the people actually using it.

What we’re focused on

  • Playability feedback — What makes the game feel good to play? What feels clunky, confusing, or slow? We want to know what’s getting in the way of you focusing on the board.
  • Spectator experience — We’re interested in how much people are watching other players’ games. Is spectating something you do? What would make it better — better navigation to live games, spectator chat, game analysis overlays?
  • Chat & social — What do you want from chat? In-game messaging, post-game analysis discussion, lobby chat, direct messages? How important are social features to your experience?
  • In-game streaming — We’re exploring the idea of live video chat during games — you could talk to your opponent while you play, and spectators could watch the stream. This would be opt-in and would make Otherchess feel more like sitting across a table from someone. Is this something you’d use?
  • Alternate piece sets & themes — Different visual styles for pieces and boards. What aesthetic do you want?
  • Game summaries & profiles — Better post-game breakdowns, richer player profiles, and clearer rating displays.

Tell us what matters: The best UI feedback comes from people who play regularly. If something annoys you every time you use the site, that’s exactly what we want to hear about.