The concept was simple on the surface. Players raise digital monsters, train them, and battle others. But under the hood, the technical ambitions were anything but simple. I wanted a real mobile app backed by a real API — not just a toy prototype.

Choosing the Tech Stack

After evaluating my options, I landed on:

• Kotlin — for the Android app, giving native performance and a modern language
• Laravel — as the backend API and asset management system, providing a clean MVC structure and strong ORM support through Eloquent

The goal was to keep concerns separated: the app handles the user experience, and Laravel handles the data — monsters, users, items, and all game assets.

First Steps

 Early development focused on laying out the Kotlin app's structure and getting the core screens scaffolded. Simultaneously, I started defining the Laravel data models that the app would eventually consume.

Art assets were generated early to give the project a visual identity, but I quickly realized that without a solid backend, pretty sprites don't mean much. I pivoted to focus on Laravel first a decision that paid off enormously down the road.

This post kicks off a series documenting the full journey from idea to production. Follow along as I build, break, and rebuild a fully interactive virtual pet game.