How these games are built, and why they are built that way.
Notes on canvas rendering, input, sound, saving and performance — written from building and publishing original browser games since 2017.
What we write about, and why
These articles are written for people who build games for the browser. That is a narrower audience than "game development" and the writing reflects it: the questions here are about frame timing, touch targets, metered data, save systems and file size, not about engines or funding.
Everything published here comes from building these games. Where a claim depends on our own measurements, we say so and use the numbers we actually took. Where a conclusion is a judgement rather than a measurement, it is written as one.
We do not publish filler, and we do not publish on a schedule for its own sake. We also do not publish a figure we cannot show the source of, which is why there is no retention chart anywhere on this site.
If you would rather read these somewhere else, the articles are also published as a feed at feed.xml.
Building something for the browser?
Tell us what you are making. If it plays in a page, we will tell you honestly whether it fits here.