Six live games. Three weeks. No prior experience with Next.js, Supabase, or Vercel. This is the devlog — honest, unfiltered, updated as it happens.
If you're tired of Wordle and want something that tests a different part of your brain — here are six free daily browser games that require no account, no download, and no subscription.
RotatingAlsoPlay, StoopNav, one Umami dashboard for everything, cross-promo on every results screen. What it means to think about a group of small free games as a platform — and why that framing changes what you build.
The guessing games needed databases, APIs, and daily puzzle management. The arcade games needed none of that. Here's what changes when you remove the backend entirely — and what Delta-E scoring, flood-fill algorithms, and liquid sort actually are.
The "thin content" rejection isn't really about content quality. It's about whether a page makes sense to a bot that can't interact with anything. Games are the worst case for this. Here's how we fixed it.
Each game had its own domain, its own Umami instance, its own everything. It worked. It also didn't scale. The stoop.games decision, the self-hosted analytics rabbit hole, and what a DNS propagation failure at midnight actually feels like.
FlagGuessr launched the same day as DailyGuessr. Same codebase structure, same deployment pipeline, different mechanic. Here's what it looks like when the second project costs a fraction of the first.
I don't know how to code. I know what I want to make. This is the story of how that combination turned into six live games in three weeks — and what 31 document versions actually look like from the inside.