I built my first Unity game with Claude

FrogPop is the first game I’ve ever built. It was inspired by Bubble Trouble, an old Flash game I played as a kid. You control a frog that pops bouncing bubbles with its tongue, and the bubbles split into smaller ones. I eventually added roguelite upgrades, relics, shops, hazards, and boss fights.

I used Claude throughout most of development. I’d describe how I wanted a mechanic to work, let Claude inspect the relevant Unity scripts, and then have it write or change the C# code. It helped with things like the tongue and bubble mechanics, the wave system, upgrades, the shop, and several bosses.

A lot of the process was me testing changes in Unity and then going back to Claude with errors or things that felt wrong. For example, one boss emerges through the walls and exposes different weak points. Claude could build the attack states and hitbox logic, but I still had to test it repeatedly because parts of the boss would appear in the wrong place or remain active after the attack ended.

Later in development, I focused more on code cleanup, debugging, tests, controller support, and preparing the browser and Windows builds. I used PixelLab for some of the artwork, then edited and integrated those assets myself.

It wasn’t a case of asking Claude to “make a game” and getting a finished result. I handled the game design, balancing, art direction, and Play Mode testing, while using Claude to help turn those decisions into something playable.

The free demo includes the first ten waves and two bosses. It runs in the browser or can be downloaded for Windows:

I also have a Steam page if anyone wants to follow its development: https://store.steampowered.com/app/5067810/FrogPop/

I’m curious how other people using Claude with Unity handle visual testing, since that was still the most manual part for me.