Taking the Leap: Becoming an Indie Dev and Thriving
I often share my journey into becoming an independent developer with folks, and today, I want to be transparent about how I got here. From leaving a stable full-time job to where I am now, this post will walk you through my path into indie dev, the bumps along the way, and what’s worked so far. If you’ve ever wondered what it takes to make the leap, read on—you might find some valuable insights for your own journey.
I am Earning £0
Right now, my app revenue is £0. That’s right—zero. I have an old tax calculator on the App Store that’s due for a rewrite or removal, but it’s not my focus. Currently, I’m fully committed to building something with real potential and market fit. Sure, there’s a risk it might not take off, but there’s also a thrill in going after something I believe in. I have a handful of other app ideas waiting in the wings, so it’s all forward movement. Even if I’m the only one using them, I’ll be happy.
While my apps aren’t earning yet, freelancing as an iOS Developer and UI Designer is helping me make ends meet. These two skillsets give me flexibility to find work, and though it’s not the same income as full-time, I’m still doing work I enjoy and pushing forward on my own projects. Which brings me to Step One of going indie…
Step 1: Take Stock
Becoming an indie dev takes more than a passion for code; it requires a clear look at your life right now. I’m married, a father of three, and my wife and I have many responsibilities. I shared my desire to go independent with her so we could both understand what changes might come and how to handle them. It was a huge relief to have her support, but we both knew we needed a solid plan.
We reviewed everything: our finances, income, and monthly needs. Luckily, we’re pretty frugal and already track our spending closely, so we knew what we needed. The biggest shift was realizing that going indie would mean both of us adjusting our roles. My wife took on a part-time job, giving us more flexibility if projects fall through or if I need a break between gigs. This buffer makes the leap into indie dev a lot less daunting.
When you’re clear on your needs and responsibilities, you can make smarter, less risky decisions about going indie. Having this foundation means fewer surprises and a lot more peace of mind.
Step 2: Set Up a Strong Foundation
Building a strong foundation is key. For me, this means three things:
- Find your tribe. Surrounding myself with other indie devs has been invaluable. I’ve been lucky to meet folks like Antoine van der Lee and Hidde van der Ploeg, both of whom have been incredibly generous with advice and encouragement. Antoine’s course, From Side Project to Going Indie, was a game-changer, and chatting with Hidde often sparks new ideas or gives me a nudge in the right direction. Watching them work and seeing their journeys turn what could be a lonely path into something really inspiring.
- Stick to routines and goals. Living with ADHD and OCD can make routines tricky, but setting goals each week keeps me on track. My wife’s work schedule means I have specific days with full focus time, and on those days, I aim to hit three main goals: ship a TestFlight build, learn something new, and write. It might sound simple, but this structure keeps me productive, even when other life demands get in the way.
- Eliminate distractions. Indie work is a balancing act, especially with kids. I make the most of my structured time and try to keep distractions low so that I can hit my weekly goals and still have time for family and hobbies. This discipline is new for me, but it’s making a big difference.
The support from others such as Mikaela Caron, Anna Beltrami, Paul Hudson, Chris Hefferman, and many more (whether directly or indirectly), setting up a realistic routine, and minimizing distractions are all helping me stay focused on the big picture. A strong foundation is like a safety net—it lets me be bolder without losing sight of what matters most.
Step 3: Have a Plan for What to Work On
Some folks jump into indie dev without a clear plan, but having a few ideas lined up helps me stay focused. Currently, I have four projects in progress. I originally planned on releasing one app per month, but my main project has grown as more beta testers and target users give feedback. There’s a promising market fit here, so I’m putting more time into it. I want to make sure it’s the best it can be before launch, which means taking time to test, polish, and iterate.
I chose these ideas based on a mix of personal interest, market need, and feasibility. When I started this journey, I didn’t want to over-commit to one project and risk burning out. Instead, I kept the scope of each idea manageable so I could work on them in parallel. This strategy keeps me moving forward even if one project slows down.
In my experience, having a clear plan—especially one with achievable goals—is crucial. My strategy is simple: work lean, ship fast, and learn along the way. Knowing what I want to work on means I don’t spend time jumping between ideas and can instead stay focused on building something meaningful.
In Closing…
These three steps—taking stock, building a foundation, and planning—are what I believe will help me succeed as an indie dev. They’ve kept me grounded and moving forward, even with three kids and zero app revenue (for now!). If you’re dreaming of your own indie journey, I hope my experience gives you a nudge to dive in.
Thinking of going indie? I’d love to hear from you on X at @stphndxn or drop me an email!
