A game without writing is a demo
When we add titles, they arrive with a catalog entry, a thumbnail, a playbook, a guide, and a place in a skill family. Meteor Tap, Gap Drop, Color Path, Sum Ten, Keeper Dive, and Pin Bowl shipped as a set for that reason. A lone canvas with “Play now” and a generic paragraph is the wrapper pattern we are trying not to be.
Batches also force a spread of verbs. Six more runners would have been easier. They would have made the home page a pile of multiples. The latest six split action, puzzle, and sports on purpose. Play styles and the family blurbs on /games are how that spread stays visible.
Maintenance is part of the product
A finite catalog we can explain is better than three hundred pages we cannot. If a collision is unfair, we want to know which build. If a label is wrong, we want to change one file, not a generated swarm. Growing in batches is how editorial and engineering stay on the same list.
The journal, studio notes, and unique headings on each game page are slower than spinning up another clone. Slower is the point. AdSense’s “low value content” label is often what you get when you optimize for page count. We would rather optimize for a sitting you can describe.
What to expect next
New titles should arrive with the same supporting writing, not as a surprise iframe. If we cannot name the cut—the extra jump we refused, the timer we did not add—we should not ship. The inventory of cuts is already a journal essay. Future batches should be able to add a paragraph to that inventory.
Until then, the thirty-eight games now in the catalog are the product. Playing three of them well is a better use of the arcade than sampling all of them once. The writing is there so “well” has a definition besides a number in the HUD.