RUN WORLD - Games


My Role

RUN is an AI-driven platform for game development and gaming. The goal is to provide tools for developers to create their games with AI and then publish them on the RUN platform for the world to play.

My role here encompassed several aspects:

  • Work as a "solo developer" and early adopter of the tools for the platform (SDKs, clients, etc.) while developing several casual games.
  • Quickly prototype and pivot based on user reception and marketing tests. Marketing numbers dictated which game lived and which didn't.
  • Develop 7–10 small games, iterating and polishing based on results.
  • Extensively use and test the newest features, finding and fixing bugs, providing feedback and experiencing the innovations firsthand.
  • Generate and provide marketing and design assets for each idea in order to pitch it both to the team and the audience (via Marketing tests)
  • Make extensive use of AI tools such as Cursor, Codex, Claude Code, Gemini and several proprietary tools to streamline the generation processes in all game-dev aspects.
  • Experiment with AI to generate: images, code, and video.
  • Broadly collaborate with the rest of the 2-person teams in the company to share lessons learned, provide constant feedback, and help debug and fix issues.


The Games

AI (HTML5)

TECHNOLOGY

2

TEAM SIZE

7-10

# OF GAMES

Web

PLATFORM



Main Achievements and Takeaways

State-of-the-Art Technology


Given the nature of the work I had to do, I got the chance to stay up to date with the most recent tools and technology. I was lucky enough to have access to the Premium versions of the most relevant AI tools, which allowed me to pick the best tool for each job.

I got to explore the most innovative ways of putting AI to work in games.

I also had the chance to learn a lot from my peers and managers, as they also discovered new uses and tools that streamlined the work in interesting ways.

Fail Fast, Fail Often


As an emerging platform, Run needed a decent library of projects made with the very same tools we were developing as a company.

I was tasked with both becoming an early adopter for said tools and developing games that would showcase their potential.

The criterion for continuing work on a project was its performance in marketing tests.

As a result, I worked on numerous small prototypes that would pivot or disappear in the timespan of a week sometimes.

Some of them were original or innovative ideas that could have become interesting games; others were fully data-driven concepts where I needed to explore and deepen a mechanic, aesthetic or genre that had proved to be successful.

Thanks to this, I learned new things about monetization, live ops, marketing, ads, different game genres, gacha systems and more.

Dealing with the bittersweet feeling and rapid pace that came with immediately changing focus from one idea to another is one of the main takeaways from these projects.


Lean, Nimble Teams


One of the premises of these developments was to deliver with the smallest team possible.

As a Technical Game Designer, I had the solo-dev experience taking care of the Design and Engineering side of things.

On the art side, I got to work with a talented Technical Artist who took care of all the generation and implementation of the assets.

I also had support from the Lead Game Designer to discuss ideas and find the right path.

This was a somewhat familiar experience for me. It demonstrated how a lean team could move very quickly, while also revealing some shortcomings.

Achieving the ideal balance between workload, feedback, diversity of views and fast deliveries is the key to making this model work.

Communicating with the other small teams and sharing lessons learned was a valuable experience that helped us all grow as teams and as professionals.


Marketing tests are both valuable and harsh


With fast prototyping, strict market validation and lean development, pivoting and discarding games was the norm.

Sometimes you had to let go of your favorite idea because the numbers said the audience didn't care for it.

This is an incredibly valuable lesson for anyone working on any product, but especially for games.

The main lessons here are:

  • Learning about Marketing concepts, tests, metrics and the tools and platforms to get them.
  • How to respond to those numbers and make relevant changes to the game to actually see an improvement
  • How to generate and organize marketing assets to get the best results