Layout Bugs

While vibe-coding solo, I only tested on my own screen, resolution, and browser. The problem surfaced as soon as real users joined with different setups: some people saw everything misaligned, some things got clipped, some cards overlapped each other.

I had to rewrite the layout to use adaptive sizing so the game looks correct regardless of screen resolution. It should work now — but if something still looks off on your end, let me know and I'll fix it.

Bots Started Talking

Another change, unrelated to bugs. The service started feeling more alive. Previously, bots just played: rolled dice, bought cards, said nothing. Now they react in the chat to what's happening in the game — if someone's building gets taken, if someone buys an expensive card or runs out of money.

It's a small thing, but the game feels noticeably more lively. An empty game with silent bots versus a session where someone's commenting on what's happening in chat — it's a meaningfully different experience, even though the game itself is the same.

Thank You to Early Players

A special thanks to everyone who tried the game after my first article.

And extra thanks to a user with the nickname SHAM, who pointed out that the game rules never said you can't buy multiple purple cards in a row — even though the game itself has that restriction. Fixed!

What's Next

The project is still going. I'm thinking about ads and other ways to bring in players. Without new users, it's hard to get feedback — and without feedback, it's hard to know what to fix or improve first.

The unit economics don't quite work out yet: paid acquisition costs more than I'm willing to invest at this stage. I'll keep figuring it out. If you have ideas on how to find players for a project like this, I'd genuinely love to hear them.

The game is still live at rastushiy-gorod.ru. No registration needed. Same as before — all feedback gets read and used. That's how the project keeps moving forward.

Three days later, I had a working browser-based board game: rooms, multiplayer, bots, chat, full game sessions. But the most interesting thing turned out to have nothing to do with AI writing code.

What's the Game?

The game is called "Growing City". It's an economic board game about developing your own city. Each turn, players roll a die, buildings activate, income flows in, and you earn money to buy new structures. You can play directly in the browser with no registration.

Day 1: AI Really Can Write Games

I'm not a professional developer. I first wrote out the mechanics in detail, then gradually converted the description into code using AI.

Day 2: Writing the Game Was Just the Beginning

The code was far from the hardest part — the biggest problem was balance. AI can suggest ideas and rewrite code, but whether the game is actually fun after changing one number is something only a human can judge.

Day 3: Infrastructure Hurt More Than the Code

SSH, Node.js, PM2, Nginx, SSL, domains — deploying to a server turned out to be much harder than writing the game itself.

The Unexpected Conclusion

Code has become much more accessible, and you can ship an MVP very fast with AI. But after that, a completely different kind of work begins: finding your first users, collecting feedback, and understanding why players return or don't. That seems to be the real bottleneck for most AI-built projects right now.

The game is live at rastushiy-gorod.ru — no registration needed, solo against bots or with friends. Would love any feedback, especially: was it clear what to do without reading the rules, and did you find a strategy that breaks the balance?