I was brought on before any designs existed, which meant the hardest part wasn’t execution—it was discovering the product’s design shape. There was no UI to inherit and no precedent to follow, so we needed momentum fast.

The name of the game was getting high-quality shots on the board: different ways to frame creation vs. consumption, different flows from prompt to prototype, and different models for publishing, discovery, and remixing.

Instead of perfecting one idea too early, we treated early design like a search problem—explore widely, compare options side by side, and let clarity emerge through contrast.

The team believed we’d recognize the right direction when we saw it; my job was to accelerate us to that moment, then expand the winning concept into a cohesive, scalable foundation.

We started by focusing on the feed because we wanted it to be the main entry point into Spawn—where people could immediately discover what was possible, then jump into remixing or creating their own game/app.

It felt like the fastest surface area to generate signal: if the Feed didn’t make you want to click, play, and build, nothing else mattered.

So early exploration centered on different feed models—how to showcase creations, how previews should work, and how quickly someone could go from inspiration to action.

Once the Feed direction felt solid, we shifted to the creation flow: how someone goes from “I want to make something” to a playable/usable first version with as little friction as possible.

We intentionally leaned into a guided, option-based starting point as a strategic differentiator from other text-to-app platforms, which often push users into a single generated result and expect them to wrestle it into shape.

Instead, Spawn generates four distinct directions up front, so you can quickly pick what resonates rather than debug an interpretation you never wanted.

From there, creation becomes iterative instead of intimidating: refine the prompt, regenerate specific parts, and evolve the build in tight loops.

Spawn started as a prompt-to-product platform for games and apps — but early usage showed us that users weren't coming to build utilities or productivity tools. They were making games. The strongest signals showed up in what people chose to build, what they shared, and what others actually spent time playing.

So we made the call to pivot.

We narrowed the narrative to gaming, reworked onboarding to get users to a game-specific "first win" faster, and doubled down on the creation-to-sharing loop that was already working. The feed redesign was key — large, immersive previews let the content speak for itself, making each game instantly legible without relying on titles or metadata. This lowered cognitive load while browsing and worked even when the library quality was uneven.

The product grew from private beta to 12K monthly active creators with 34% week-1 retention. More importantly, the pivot validated that Spawn's real strength wasn't breadth. It was making game creation feel fast, shareable, and fun.