The Journey to 50 Million Downloads as an Independent App Developer — About the Creator of Rork Lab

In 2013, I made a decision that seemed reckless to most people: I left the stability of corporate employment at a major systems integrator to build mobile apps independently. I had no venture funding, no marketing team, no board of investors checking in on metrics. I had a clear vision and a willingness to work obsessively on something I believed in.

Thirteen years later, the apps I built had accumulated over 50 million downloads across iOS and Android, maintained millions of monthly active users, and generated sustainable revenue without requiring venture capital or external funding. This journey taught me lessons about product, market, user psychology, and the specific challenges of indie app development that I couldn't have learned any other way.

Rork Lab exists because I want to share these lessons seriously and explore what becomes possible when you approach app development not as a path to startup exit, but as a sustainable craft practiced with intention.

The Decision to Go Independent

Leaving a stable job to build apps wasn't driven by desire for fame or venture funding. It was driven by a simple observation: I had been building products for large organizations for years, but I had never built a product entirely my own. I had never experienced the full cycle of launching something, watching real users interact with it, iterating based on their behavior, and refining until something genuinely resonated.

I was also tired of building systems for internal consumption. I wanted to build for millions. Not to maximize growth for growth's sake, but because building for millions teaches you things about product development that building for thousands simply doesn't. You learn about edge cases you never considered. You discover patterns in user behavior at scale. You understand what "product-market fit" actually means.

The financial calculation was straightforward: I had saved enough to support myself for several years, and I believed that if I could ship a quality product that people genuinely wanted, monetization would follow naturally. I wasn't wrong, but the path was more nuanced than I expected.

The First Years: Building Without Pressure

The early years of my app business were characterized by what I can only describe as disciplined patience. I released apps, and they found audiences—slowly at first, then more rapidly as they accumulated ratings and moved up search results in the app stores. But I resisted the pressure to optimize purely for growth metrics.

My philosophy was simple: build something people love, not something people feel compelled to tolerate. This meant designing user experiences that were genuinely thoughtful, avoiding aggressive monetization that would annoy users, and prioritizing retention over user acquisition. In the long term, these choices compound. In the short term, they mean slower growth than competitors who are willing to be more aggressive.

But I had the luxury of patience. No investors demanding hockey-stick growth curves. No pressure to reach exit targets. This gave me the space to optimize for the right metrics: user retention, positive ratings, and sustainable revenue.

The apps I built were in the lifestyle category—primarily wallpaper and meditation apps. These seem simple on the surface, but they're actually quite challenging. Users have infinite choices. The barrier to switching to a competitor is virtually zero. In this environment, the only sustainable strategy is to build something so good that people keep using it, keep rating it positively, and keep recommending it to friends.

Understanding App Store Optimization

One of the most underrated skills in indie app development is what's become known as App Store Optimization, or ASO. This is the practice of understanding how app stores surface applications, what drives visibility, how keywords and ratings influence discovery, and how to optimize your presence within these constraints.

ASO is often described as a marketing skill. But I've always seen it as fundamentally a product skill. Understanding how the app store's algorithm works means understanding your users better. It means knowing what searches are driving your downloads, what words resonate with your target audience, and what expectations people have when they discover your app.

I spent countless hours studying App Store metrics. What searches was my app appearing in? What keywords were driving the highest-quality users—the ones who would actually use the app and keep it installed? How did ratings influence visibility? How did update frequency impact algorithmic ranking? These questions became obsessions.

The learning cycle was tight: ship an update, watch metrics for weeks, identify patterns, refine keywords and description, ship again. This iterative approach, repeated hundreds of times over more than a decade, compounded into serious competitive advantage.

The Psychology of Monetization

Perhaps the most delicate aspect of app business is monetization. You need revenue to sustain the business and justify the time investment. But if you optimize too aggressively for revenue, you destroy the product and lose users.

My approach evolved over time, but the principle remained constant: monetization should be aligned with user interests. If advertising is your model, serve ads in ways that don't completely disrupt the user experience. If you offer subscriptions, make sure they provide genuine value. If you sell premium features, ensure they're features that people actually want.

This sounds obvious, but I've seen countless apps where the monetization strategy contradicts the product strategy. The developers claim to care about user experience while implementing dark patterns designed to maximize revenue extraction. Users sense this hypocrisy immediately, and it shows in ratings and retention.

My apps used a mix of free with optional premium upgrades, plus advertising through AdMob. The advertising was unobtrusive. The premium features were genuinely useful, not just "no ads." This approach yielded healthy margins without becoming exploitative. The apps maintained high ratings (typically 4.5+ stars) even as they generated significant revenue.

The Infrastructure Story

One aspect of indie app development that rarely gets discussed is infrastructure. When you're operating independently, you need to think carefully about the backend systems supporting your apps. You need analytics. You need to be able to push updates. You need to handle user data responsibly.

Google Firebase was transformative for me. Before Firebase matured, running backend infrastructure as an indie developer was painful. You had to manage servers, handle scaling, monitor uptime, manage databases. Firebase abstracted much of this away, allowing me to focus on product rather than infrastructure operations.

This is one reason why indie app developers should pay careful attention to platform evolution. A tool like Firebase—or equivalent infrastructure services—fundamentally changes the calculus of what's possible for small teams. It meant I could build products with millions of users without needing a dedicated DevOps team. It meant I could focus on product quality rather than infrastructure management.

At Scale: Learning From Millions

By the time my apps reached tens of millions of downloads, I had access to behavior patterns from millions of users. This became incredibly valuable data. I could see which features people actually used versus which ones I thought they'd use. I could identify drop-off points in onboarding. I could see which locales and devices had the highest retention.

This data transformed how I approached product development. I stopped relying on intuition and started relying on evidence. Not exclusively—intuition still matters, and sometimes the data tells you things that are misleading if you don't understand context—but evidence became my primary guide.

One unexpected insight was how much user behavior varies by geography and cultural context. The same app performed differently in different countries. Users in some regions had very different expectations about pricing, about how frequently to see ads, about the kinds of content that resonated. Building for a global audience meant understanding these differences and often shipping localized experiences.

The Unseen Challenges

What people don't often discuss about indie app development at scale is the grinding operational challenge of maintaining quality across millions of users. Every update requires careful testing. Every bug potentially affects hundreds of thousands or millions of users. You learn quickly that "move fast and break things" works fine when you're an early-stage startup competing for market share, but it's a terrible strategy once you have millions of users who are counting on your app to work reliably.

I also learned the challenge of platform dependency. My entire business depended on decisions made by Apple and Google. They control the distribution, they set the terms of service, they can change algorithms overnight, they can disable monetization models without warning. This wasn't a hypothetical risk—it happened multiple times during my years building apps. A monetization model would shift. Google would change how search worked. I had to constantly adapt.

This is both the advantage and vulnerability of building on top of existing platforms. The advantage is reach and infrastructure you couldn't build independently. The vulnerability is that you're building on someone else's land, and they can change the rules whenever they want.

Why I Stepped Back

After more than a decade, I stepped back from active app development not because the business was failing, but because I wanted to explore other territories. The apps were still generating revenue. The user bases were stable. But I had learned what I wanted to learn from that chapter.

What pulled me away was my artistic practice. In 2019, I experienced something that reoriented my entire perspective on creative work. I became fascinated with exploring consciousness, perception, and the psychological territories that can't quite be reached through practical product design.

This wasn't a rejection of app development. It was a recognition that I had one life and multiple interests, and I wanted to explore the artistic side with the same intensity I'd brought to building apps. If I was going to be an artist, I wanted to do it seriously. That meant stepping back from app development.

The Lessons

What strikes me looking back at the app business years is how much success came down to basics that sound almost boring:

Build something people genuinely want. Not something you think they should want. Not something that optimizes perfectly for metrics. Something that actually solves problems or brings pleasure to real people.

Optimize for retention, not acquisition. You can buy your way to downloads. You can't buy your way to retention. If people love your app, they'll tell their friends. If they tolerate your app, they'll delete it the moment they find something better.

Respect your users. Don't exploit dark patterns. Don't use aggressive monetization that contradicts your product strategy. Don't ignore negative feedback. Treat users as people whose time and attention matters, because it does.

Be willing to learn from data while maintaining vision. Numbers tell you what's happening. They don't tell you why or what to do about it. Use data to inform decisions, but maintain the confidence to make judgment calls when your intuition and data suggest different things.

Think long-term. It takes years to build anything worth building. Most competitors optimize for quick wins. If you're willing to play the long game, patient compounding of small advantages can yield outsized results.

Why Rork Lab Exists

After stepping back from app development, I continued to think about these lessons. I noticed that the app development community was increasingly dominated by startup culture thinking: rapid growth, venture funding, exit strategies, growth-hacking tactics. There's nothing wrong with that path, but it's not the only path.

Rork Lab exists to explore the indie developer path seriously. What's possible if you approach app development as a sustainable craft rather than a startup? How do you build long-term relationships with users rather than optimizing purely for growth metrics? What becomes possible when you think in terms of decades rather than quarters?

I'm not claiming this path is better than the startup path. They're different approaches optimized for different goals. But I'm convinced the indie developer path deserves more serious exploration and documentation. There are lessons there that apply far beyond app development.

Apps

Websites

Social Media

Masaki Hirokawa App Developer & Digital Creator

Building 50 million-download businesses independently taught me that sustainable success comes from genuine user value, patient iteration, and thinking in terms of decades rather than quarters.