Product · Mobile Game

I built a mobile game with AI — no dev team, no code, one good idea

If you still think AI is a chatbot that writes your emails, you're using maybe 5% of it. Here's my proof.

I built a fully playable mobile game. A real one — animations, levels, scoring, the kind of polish you'd expect from an app-store download. A few years ago that meant hiring a dev team, waiting months, and spending money I'd rather put toward a Disney trip. I did it alone — not because I'm a developer (I'm not), but because I've learned the one skill that actually matters right now: how to direct AI to build what's in my head.

What I built

STACKED is a match-3 puzzle game that teaches teenagers about money — without a single lecture. A 7×7 board of money-themed tiles (coins, cards, wallets, savings), and you swap them to build combos and cascades. The catch: 18 moves to hit a 900-point target.

The lesson hiding in the mechanic

That move limit is the whole point. 18 moves is your budget. Burn them on impulsive swaps and you lose; plan ahead, work toward the goal, make every move count, and you win. That's saving, budgeting, and delayed gratification — except nobody said those boring words, you just felt them while playing. Small consistent wins compounding into real progress. That's not only a game mechanic — that's how money actually works.

The prototype has everything: tap-and-swipe controls built for phones, cascading matches, animated counters, a level map with locked stages, streaks, stats, and an original visual identity that's bold and bright — not "educational app" beige.

How AI actually built this with me

This is the part I want you to pay attention to. My AI partner here was OpenAI Codex — not a fancy autocomplete, but my design collaborator and my hands on the keyboard. I brought the vision, the product thinking, and the marketing brain: who this is for, what it should feel like, what makes it addictive, what makes it teach. The AI brought the implementation — React and TypeScript for the game logic, Next.js for the architecture, a custom match-3 engine handling match detection, board refills, and win conditions. We iterated, tested, and published together, and it now runs in the browser on OpenAI sites. No backend, no logins, no game engine.

My job was never to write the code. My job was to make a hundred small decisions well — and that's a marketing and strategy job, not an engineering one.

Why I'm telling you this

Because I keep meeting smart, ambitious women who think building things is for other people. It's not. The gap between "I have an idea" and "I made a real thing" has never been smaller — and AI is the bridge. You don't need permission, a technical co-founder, or a bootcamp. You need an idea, taste, and the willingness to learn how to work with these tools.

That's what this is: me building things with AI in public, so you can see exactly what's possible — and steal the playbook.