4 posts tagged with roadmap.
A game spectate feature has sat on our wishlist since the first gomoku match went live. Here is the honest plan: what watching a match has to do, why it is a privacy question first, how a commentator seat stays out of the way, and the order we would build it in.
Most of our traffic arrives on a phone and the board was drawn for a mouse. This is the mobile game optimization list: touch targets, board scaling, what happens to a live match when a call comes in, and the things we decided not to build.
Nobody asks for performance work, and everybody notices when it is missing. This is the YiBoard list: four numbers from a mid-range Android phone, why the board moved from 225 DOM nodes to one canvas, how the 500ms engine budget stopped freezing the board, and the optimizations we turned down.
Go sits last in our build order, behind gomoku, xiangqi and reversi. Not because it matters less, but because it costs the most to do properly. Here is the go development plan: the hard parts, the order we are building in, and what has to be true before it ships.