--
title: "Why Board Games Are the Perfect Web App"
description: "Why Board Games Are the Perfect Web App"
tags: ["games", "chess", "webdev", "gamedev"]
canonical_url: https://yiboardgame.com/blog/board-games-browser-revival
Last week a college roommate and I played Gomoku over a video call, him in Shenzhen, me in Hangzhou, nothing installed on either side. One link, fifteen minutes. Mid-game he said it out loud: ten years ago this meant a 300MB client. He's right, and the reasons go deeper than convenience.
Board games have a technical profile that matches the web almost perfectly. They're turn-based, which means input density is tiny and latency requirements are nearly irrelevant. You move, your opponent thinks for two minutes, and a few hundred milliseconds of network jitter changes nothing. Compare that to an action game where latency is the product, and you see why the browser never feels limiting here.
The ruleset is also cheap. Go, Xiangqi, and Gomoku have rules that fit in a few hundred lines of logic. Special cases like forbidden moves, ko fights, and stalemate detection run fine in a browser engine. No GPU work, no asset pipeline, no giant bundle. A page and some state management are the entire tech stack.
The device story compounds it. A web game opens on an office laptop, a living-room tablet, or a phone browser with the same URL and no save-file sync. Every device is the same board. That's a property native apps have to engineer around, and the web gets it for free.
The part that surprised me as a developer is where the difficulty actually is. It's not the code. It's three product problems that online board games inherit from offline play.
Etiquette is the first. Offline, the table enforces it: you don't talk after placing a stone, you don't rush a thinking opponent. Online, nobody is watching, so the product has to stand in. Move sounds and "opponent is thinking" indicators are how good platforms recreate that ritual.
Resignation is second. Offline you push your stones over. Online you need an explicit resign button, plus handling for the standoff where one player refuses to resign and also refuses to move. Timeout losses and clean resign flows are the answer, and they only work if the awkwardness is designed for openly.
Timing is third. Offline clubs have clocks. Online you need countdown with no increment, plus friendly games with no clock at all, and both need to be adjustable because a hard countdown is a wall for beginners.
The web-specific advantages over an app come down to three things. Zero install: open a link, play, no storage taken, no update prompts, and the psychological gap between clicking a link and downloading software is real. Link equals game room: one URL puts both players on the same board, no friend system, no room codes. And sharing: a finished game generates a replay link in one click, which is the entire loop for review and bragging, and the web does that natively.
For beginners, the browser adds features a physical room can't provide: undo, AI hints, full replays, and no-timer friendlies. That set of affordances is why web board games can onboard new players where offline clubs grind them down.
Classic games are the best fit because they're old and pure. Simple rules, endless depth, and a cultural weight that makes them worth preserving. A link, a board, two people. That's the whole pitch.
More on why we built this in a browser, and how the features work: https://yiboardgame.com/blog/board-games-browser-revival
