Downset started with a simple question from a kid who loves video games: "How do they make these?"
His dad, a software engineer in San Francisco, decided the best answer wasn't a lecture. It was a project. Instead of explaining how games get built, they'd build one together and find out firsthand. The idea was small at first: a grid of numbers, a tap mechanic, a matching rule. Just enough to see something happen on screen. Just enough to make his son say "wait, do that again."
That first prototype took an evening. It barely worked. The numbers were too small, the colors were wrong, and nothing felt fun yet. But it was theirs, and that made all the difference.
What followed was weeks of after-school tinkering, weekend play sessions, and conversations about what makes a game feel good. The kid had opinions. Strong ones. "The locked cells should shake." "This is too easy." "What if the cleared ones came back?" Every idea got tried, and most of them made the game better.
There were late nights spent adjusting the way Zombie mode plays, tweaking infection timers and zombie HP until the difficulty felt right: hard enough to lose, fair enough to keep trying. There was the morning they missed their bus stop on the way to school because they were deep in a conversation about how to make Matchbox work. The win condition is inverted in that mode, and getting the logic right took more napkin sketches than either of them expected.
Every mode in the game has a story like that behind it. Downset mode came from asking "what if you could predict every outcome?" Strict mode came from "what if nothing matched at the start?" Each one began as a "what if" and became something real through trial, error, and a lot of gameplay testing on the bus, at the kitchen table, and during lunch breaks.
The original goal was to show a kid how online games work. What actually happened went further than that. He learned that building something people use takes patience. That the first version is never the good version. That you have to play your own game dozens of times to find the parts that don't feel right, and then you fix those parts, and then you play it again.
He learned that a bug isn't a failure. It's just something you haven't figured out yet. He learned to describe what he wanted clearly enough for it to become code. And he learned that the best ideas often come from playing the game, not from planning it.
Right now, Downset is a web game. You can play it in any browser, on any device. But the goal has always been bigger than that. Father and son are working toward making Downset a native iOS and Android app, designed and built specifically for those platforms. Not a port. Not a wrapper. A game that feels like it belongs on your phone.
There are more modes coming. There are adjustments to the ones already here. The zombie timer might get meaner. Matchbox might get a new wrinkle.Classic will always be Classic, but that doesn't mean it won't get better.
If you've played Downset, thank you. If you've come back to play it again, that means more than you know. This game started as a way to answer a kid's question, and it turned into something a father and son build together every week. We hope you like it as much as we do.
— T. and O.
Made in San Francisco, CA.