Articles
Playfield Journal
Editorial notes on playing in a browser: how to judge a build before you commit to it, why a load behaves the way it does, how the common control schemes work, and what changes when the screen is a phone.
From the desk
Notes on browser games
Four short pieces on playing well and choosing better.
How to tell a well-made browser game from a thin one
Nothing vets what gets published in a browser, so the sorting falls to the player. This piece sets out the signals that separate a carefully built game from a thin one: whether the loading screen admits it is working, whether the control is stated before you need it, whether the goal is named within half a minute, and what advertising behaviour should make you close the tab.
Why browser games load slowly, and what actually helps
A long load is the most commonly misdiagnosed thing about browser games. You are downloading an application, not a page, and big engines carry a fixed startup cost whatever your connection is doing. This piece explains where the time goes, why reloading usually restarts the clock, and why clearing your cache tends to make the second visit slower rather than faster.
A plain guide to browser game controls
Nearly every browser game is built on one of six inputs: the single tap, the drag, the swipe, the press and hold, the two-part press, and the keyboard or pointer build. Knowing which one you are looking at tells you how a game will feel before you have any skill at it, and applying the wrong habit is the most common reason a first session feels harder than it is.
Playing browser games on a phone: what works
Most people now meet a browser game on a phone rather than a desk. Touch play suits tapping, dragging, and swiping, and fights anything that assumes a keyboard or a precise pointer. This piece covers orientation, thermal throttling, the real cost of a long session, and a short checklist to run before you commit.