Journal · Entry 03
The quiet HTML5 renaissance
Browser games never went away. They stopped being marketed, kept getting better, and are now the most underrated corner of the medium.
Everything starts in a tab
There was a period, somewhere between the arcade and the app store, when a game could be a page. You opened a link, waited eleven seconds, and played. No account, no install wizard, no fifteen-gigabyte patch arriving the moment you wanted to start. The whole ritual was: click, play, close the tab.
That ritual never disappeared. It simply stopped being the centre of the conversation. Browsers became dramatically more capable while the industry's attention moved to storefronts, and the result is a strange gap: the technology to play instantly got better while the expectation of playing instantly got worse.
Why the renaissance was quiet
Three things changed under the surface. Canvas and WebGL became fast enough for real action. Audio APIs became reliable without plugins. And the tooling for building a small game shrank to the point where one person could ship one in a weekend.
None of that produced a marketing moment, because browser games do not have a storefront pushing them. They spread by link, by forum post, by a friend sending a URL. That makes the scene quiet and durable at the same time. Nobody is spending a budget to convince you it exists, so the only thing that travels is the game itself.
A console is a machine that plays games without asking you to become a customer first. On that definition, the browser has been the most popular console for twenty years.
The cost of installing
Installing is not free, even when the download is. It costs a decision, a quantity of disk, a permission, a background process, and — increasingly — an account. For a game you intend to play for six minutes, that is an absurd exchange rate. You are paying a long-term administrative cost for a short-term entertainment.
There is a subtler cost too: the install creates an obligation. A game sitting in your library is a thing you have not finished. A game in a tab is a thing you did. The browser's disposability is a feature, not a flaw — it lets a short game stay short without feeling like an incomplete commitment.
This is not an argument against large games. A forty-hour game is a fine thing to install. The argument is about match: the size of the commitment should fit the size of the experience.
What the browser is good at
The browser is exceptionally good at five things, and a game that leans into them feels native rather than compromised:
- Instant starts. No install step means the first interaction can happen in the same second as the intent.
- Input you already own. A pointer, a keyboard, a touchscreen. No pairing screen.
- Disposability. Closing a tab is a complete exit. No save management, no sync prompt.
- Sharing by URL. A game is a link. Sending it is the same gesture as sending a sentence.
- Small surfaces. A tab is a bounded space, which suits games with a single clear loop.
Where the browser struggles is equally clear: long-form progression, heavy simulation, and anything that needs to keep state across weeks. A guide that pretended otherwise would be lying to you. The catalogue is organised around what the format does well, which is why the shelves are short and the session lengths are printed on every entry.
Start with the catalogue, pick a shelf that matches the time you actually have, and open one entry. Read the loop, play a round, close the tab. That is the whole ritual, and it has worked for twenty years.