Browser games have an unusually clean history. They were born with a plugin, they grew up during a standards war, and they were reborn when the browser learned to draw.

The plugin era

In the late 1990s the browser could render text and images and not much else. Animation meant GIFs; interaction meant forms. Flash changed that by offering a single runtime that could draw vector graphics, play sound, and stream a game in a few hundred kilobytes.

The result was an explosion of small games built by individuals: portals, sponsorship deals, high-score tables, and a whole culture of one-week productions. Flash also created the first real distribution channel for independent games — no publisher, no console certification, no shelf space.

The technical cost was invisible until it mattered: the games lived inside a proprietary runtime, they were indexed poorly by search engines, they did not work on the phones that arrived in 2007, and they needed a plugin that crashed, drained batteries and needed constant security patches.

The gap years

When mobile devices arrived, they shipped without the plugin. For several years the most interesting browser play happened inside apps rather than the open web — a strange detour where a game you could link to became a game you had to install.

The web standards community answered with two things: better JavaScript engines, and the canvas element. Canvas gave developers a blank bitmap they could draw into with a simple 2D API. No plugin, no runtime, no installation. A game became a page.

What Canvas changed

Three things mattered more than the drawing API itself.

  • It was linkable. A canvas game is a URL. It can be shared, bookmarked, indexed, embedded.
  • It started fast. A few hundred lines of JavaScript and an image-free art style can load in under a second on a phone.
  • It was inspectable. View source works. That sounds trivial, but it made the whole scene teachable; you could learn by reading other people code.

The last one is why there is still a healthy culture of tiny, handmade games. The barrier to learning is a text editor.

What got lost

The plugin era had a genuine toolchain: a timeline, vector art tools, an animation model that non-programmers could use. Canvas has none of that by default. You draw with code, which is powerful and also a filter.

The other loss is the portal. The old portals aggregated thousands of games and gave them a shared audience. That role is now spread across app stores, video platforms and search, and none of them is quite as good at surfacing a strange little game.

Where we are now

Modern browsers can do nearly everything the plugin did, plus push the work onto the GPU. The interesting consequence is that the cost of making a small game has collapsed again — a single HTML file can be a complete game with sound, saves and touch controls.

That is roughly the bet behind this site: a canvas game does not need an install, an account or a store. It needs a link and a spare three minutes.

The browser game did not die when the plugin did. It went back to being what it was at the start: a page that plays.