Today, I want to share a pivotal chapter in my journey, one that taught me a lesson that still resonates with me years later. So, buckle up as I take you through the rise and fall of "Narucrow" – my first game development venture that left an indelible mark on my path.
Some History
Back in 2014, fueled by my passion for both coding and gaming, I embarked on a thrilling journey to bring my vision to life. The result? "Narucrow," an infinite scrolling tap game that paid homage to the beloved anime "Naruto."
The game was my brainchild, and its development was both exhilarating and challenging. As a novice software developer in my first year of my BSc at the University of the West Indies, my anxiety about being able to pull this off successfully was eclipsed by my passion for the anime Naruto and my curiosity for learning. Little did I know that game development posed a unique set of hurdles.
A taste of success!
To my delight, "Narucrow" didn't just see the light of day; it soared. The game hit the Android platform on the 3rd of March 2014 and quickly gained traction. I launched it on the Google Play Store initially and then the Amazon App Store. Gamers from all over were tapping away, immersing themselves in the world I had crafted. The download counter climbed, and the ratings on the Google Play Store soared past the 4-star mark. It was a high point in my journey, and I basked in the success of my creation.
After seeing the "huge" success (back then, close to 30k downloads was a lot in my opinion...). I saw game development as an actual way to retire if I could have monetized it. After a bit more research I decided to integrate Google Admob and showed a full-page interstitial ad after each game, and banner ads on the home page.
With each passing day, the amount I earned grew exponentially. I was excited. I distinctly remember thinking "Maybe I could retire once I finish my BSc"
The app was making money, which motivated me more and more to continue working on it.
The Fated End
As the saying goes, what goes up must come down. The crescendo of success met an abrupt halt, not due to a lack of players or dwindling enthusiasm, but to an unforeseen technical mishap. It's a lesson that remains etched in my mind and serves as a cautionary tale for all developers – novice or experienced.
You see, the catastrophic event that led to the downfall of "Narucrow" was a hard drive failure. It's a nightmare scenario that every developer fears, and I was caught unprepared. Little did I know, this unfortunate event would unearth a glaring gap in my contingency planning. The keystore file, an essential component for updating the game, had vanished along with my ailing hard drive. It felt like a cruel twist of fate – the very success I had achieved was now the harbinger of my game's demise.
It all seemed like a nightmare. I tried all the recovery tools I had access to and while I was able to retrieve old family photos and documents, my "recovered" keystore was corrupted and rendered unusable. The days of NaruCrow were numbered and no stroke of luck, magic wand, or pleading with Google themselves could have changed its fate.
RIP Narucrow: 3 Mar 2014 - 1 Aug 2014
A Lesson Learnt
The inability to update "Narucrow" had far-reaching consequences. As much as I wanted to bring new features, characters, and improvements to the game, I was stranded with no lifeline. The game eventually faded from the platform it once flourished on, leaving behind a community of players who were left wondering what happened.
This experience was a stark reminder of the fragility of digital creations and the importance of safeguarding your work. While the success of "Narucrow" was gratifying, the lack of a backup plan for critical files proved to be its undoing. It taught me a lesson that transcends game development – the significance of redundancy and contingency planning.
Years have passed since "Narucrow," and my journey as a game developer has ended. While I have tried to revive that application in the past, since I had no way to port over close to 30 thousand users across to the new app version, I eventually gave up hope... Thus, ending my very short dabble in Game Development.
The lesson that I painfully learned from that experience has become the cornerstone of my approach to development. Regular backups, version control, and disaster recovery plans are no longer mere buzzwords; they're integral parts of my process.
So, to my fellow developers, whether you're just starting out or already have a few projects under your belt, remember the tale of "Narucrow." Embrace the successes, but don't underestimate the importance of preparedness. As I continue on my journey, I carry this lesson with me – a lesson that has transformed the way I approach my craft and my creations.