Key Takeaway
Going full-time indie is not a binary switch you flip one day. It is a gradual transition with clear milestones: validate an idea while employed, build revenue to cover basic expenses, save 12-18 months of runway, then make the leap. The developers who succeed treat it like a business from day one, not just a coding project.
The Uncomfortable Question Nobody Wants to Answer First
Should you actually go indie? Before we talk about the roadmap, let me be direct about something. Going full-time indie is not inherently better than a salaried developer job. A senior iOS developer at a mid-size company earns $140K-$180K in the US with benefits, PTO, and zero revenue risk. The median indie app after 12 months earns less than $50/month according to RevenueCat's 2026 data.
I am not saying this to discourage you. I am saying it so you go in with open eyes. The developers who make it as indies are the ones who understand the math, plan the transition carefully, and build the business skills alongside the coding skills. This roadmap is designed to help you do exactly that.
For a deeper look at the income spectrum, check out our guide on how much indie iOS developers actually make. The numbers range from $0 to $500K+/month, and understanding where you are likely to land is important before you quit anything.
Phase 1: The Side Project Stage (Months 1-6)
You are employed. You have a steady income. This is your greatest asset, and you should use it wisely. The goal in this phase is not to build a billion-dollar app. It is to learn the non-coding skills that will determine whether your indie career succeeds or fails.
Choose the Right First Project
Your first indie app should be small. Not "small but actually takes 6 months." Actually small. Think: 4-6 week build time for the MVP, a single core feature, and a monetization model you can validate quickly. Here are the qualities of a good first indie project:
- Solves a problem you personally have. You are your own first user, so you already understand the pain point deeply.
- Has recurring value. The user comes back daily or weekly. This justifies a subscription and builds habit.
- Can launch with a single feature. A habit tracker, a niche calculator, a focused productivity tool. Not an all-in-one project management suite.
- Has existing demand. Search the App Store for competitors. If nobody is doing what you want to build, that is usually a warning sign (no demand), not an opportunity (blue ocean).
For app idea inspiration backed by revenue data, see our list of iOS app ideas that actually make money in 2026.
Build the MVP in 4-6 Weeks
The biggest mistake first-time indie developers make is spending too long on the first version. You need to get something into the App Store and start collecting real data: Are people downloading it? Do they complete onboarding? Do they hit the paywall? Do they subscribe?
Every week you spend polishing an unreleased app is a week you are not learning from real users. Ship the core feature, a basic onboarding flow, and a paywall. That is it. Everything else can come in updates.
Using a boilerplate like The Swift Kit dramatically compresses this timeline. Auth, onboarding, paywalls, analytics, and backend integration are pre-built. You are writing the feature code from day one instead of spending three weeks on login screens and subscription infrastructure.
Learn to Read Your Metrics
Once your app is live, you need to understand these numbers:
- Day 1 retention: What percentage of people who download your app open it the next day? Aim for 25%+.
- Paywall impression rate: What percentage of users see your paywall? If it is below 50%, your onboarding is losing people before they reach the offer.
- Trial start rate: Of users who see the paywall, what percentage start a free trial? Below 20% means your value proposition is not clear.
- Trial-to-paid conversion: RevenueCat's 2026 data shows the median is 10.7% for hard paywalls and 2.1% for freemium. If you are below median, focus here first.
- Monthly churn: What percentage of subscribers cancel each month? Under 8% monthly is good. Under 5% is excellent.
These metrics, not downloads, tell you whether you have a viable business. A hundred downloads with 10% trial conversion and 50% trial-to-paid is a much stronger signal than 10,000 downloads with 0.1% conversion.
Phase 2: Building Revenue While Employed (Months 6-18)
Your app is live. You have initial data. Now the real work begins: turning a side project into a revenue stream.
Income Milestones to Target
These milestones give you concrete goals and help you gauge when the transition to full-time is realistic:
| Milestone | Monthly Revenue | What It Signals |
|---|---|---|
| First Dollar | $1-$50 | Someone, somewhere values what you built enough to pay for it. This is more meaningful than it sounds. |
| Ramen Profitable | $500-$1,000 | Your app covers a real expense. Not enough to live on, but proof of product-market fit. |
| Side Income | $1,000-$3,000 | Meaningful supplemental income. At this point, going full-time starts to feel possible. |
| Transition Zone | $3,000-$5,000 | Covers basic living expenses in many areas. This is where most indie developers make the leap. |
| Comfortable Indie | $5,000-$10,000 | Equivalent to a decent salary after Apple's cut and taxes. Sustainable long-term. |
| Thriving | $10,000+ | You are earning more than most salaried iOS developers. Congratulations, you have built a real business. |
For a detailed breakdown of the math behind each milestone and what strategies drive growth at each stage, read our guide on growing from $0 to $10K MRR.
The Skills You Need Beyond Coding
Here is the part that blindsides most developers. As a solo indie, you are not just the engineer. You are the product manager, marketer, designer, customer support agent, accountant, and CEO. The coding is maybe 40% of the work. Here are the other skills you need to develop:
App Store Optimization (ASO)
For most indie apps, the App Store is the primary discovery channel. You need to learn keyword research, screenshot optimization, and description writing. The title and subtitle of your app listing are the most important pieces of marketing copy you will ever write. They determine whether your app appears in search results and whether people tap to learn more.
Focus on keywords that real people search for (use tools like AppFollow or AppTweak to research search volume). Put your most important keyword in the title. Write a subtitle that communicates the benefit, not the feature. And update your screenshots quarterly to keep them fresh.
Marketing and Distribution
You cannot outspend venture-backed competitors on ads. That is fine. Indie apps grow through organic channels: ASO, content marketing, social media presence, Product Hunt launches, press coverage, and word-of-mouth.
Pick one or two channels and go deep. A weekly blog post about your niche. A Twitter/X presence where you share build-in-public updates. A landing page optimized for Google search. Spreading yourself across every platform means doing none of them well. See our guide on creating an app landing page for the SEO and conversion fundamentals.
Customer Support
Every one-star review that goes unanswered is a permanent negative signal in the App Store. Every support email you respond to quickly is a potential five-star review. As a solo developer, you will feel the urge to ignore support so you can write code. Resist it. Good support at the indie scale is a genuine competitive advantage because most apps have terrible support or none at all.
Set up a simple support email (support@yourapp.com) and check it twice a day. Respond within 24 hours. Be human. Users are remarkably forgiving of bugs when the developer responds personally and quickly.
Financial Literacy
You need to understand Apple's commission structure (15% if you qualify for the Small Business Program, 30% otherwise), your tax obligations as self-employed income, and basic bookkeeping. Set aside 25-30% of your app revenue for taxes from day one. Open a separate bank account for your app business. Track expenses (Apple Developer Program fee, hosting costs, design tools).
This is not glamorous, but developers who ignore the financial side get a nasty surprise at tax time.
Product Thinking
The difference between a side project and a business is product thinking. A side project adds features because they are fun to build. A business adds features because they move a metric (retention, conversion, or revenue). Learn to prioritize ruthlessly. Use your analytics to identify where users drop off, then fix that before adding anything new.
Phase 3: Preparing to Go Full-Time (Months 12-24)
You have been building your app on the side. Revenue is growing. The thought of going full-time is starting to shift from "maybe someday" to "maybe soon." Here is how to prepare for the leap.
The Runway Question: How Much Do You Need?
This is the most-asked question in every indie developer community, and the answer varies based on your situation. Here is what the data and community wisdom suggest:
- Minimum viable runway: 6 months. This gives you enough time to go all-in on growing revenue, with a buffer to find a job if things do not work out.
- Recommended runway: 12-18 months. This is the range most successful indie developers cite. It removes the panic of a ticking clock and lets you make strategic decisions instead of desperate ones.
- Conservative runway: 18-24 months. If you have dependents, a mortgage, or simply want the comfort of a large safety net, this is the prudent choice.
Runway means savings that cover your living expenses (rent, food, insurance, minimum debt payments) with zero income from your app. Your app revenue is on top of this. Some developers wait until their app revenue covers 50-75% of their expenses and keep 12 months of the gap as runway. Others save the full amount and treat app revenue as a bonus during the transition period.
One thing every experienced indie agrees on: do not go below 6 months of savings. The stress of running out of money kills creativity, leads to bad product decisions, and makes the entire experience miserable.
The Transition Checklist
Before you hand in your notice, make sure these boxes are checked:
- Health insurance sorted. In the US, this is the single biggest expense. Research COBRA, marketplace plans, or spouse/partner coverage. Budget $400-$800/month for individual coverage.
- Revenue is stable or growing. Not spiking from a single event. You want 3+ months of consistent revenue to confirm the trend is real.
- Emergency fund separate from runway. Keep 2-3 months of expenses in a separate account for true emergencies (medical bills, equipment failure). Do not dip into runway for these.
- Your app is not a one-hit wonder. If all your revenue comes from a single feature that could be cloned by a competitor in two weeks, you are more fragile than you think. Ideally, you have multiple retention hooks and a growing user base.
- You have told zero people at work. Until your resignation is submitted, keep your indie plans private. You do not want to be managed out or lose equity/bonus while you are still preparing.
- You have a 90-day plan. What are the top three things you will do in your first 90 days of full-time indie work? If you do not know, you are not ready.
Phase 4: The First 90 Days Full-Time
You did it. You quit. The first Monday without a standup meeting is exhilarating. It is also terrifying. Here is how to make the most of this critical period.
Establish a Routine Immediately
The number one failure mode for new full-time indie developers is losing structure. Without meetings, sprints, and a manager, the days blur together. You sleep in, you context-switch between ten different ideas, and suddenly it is Friday and you shipped nothing.
Set a work schedule and stick to it. Many successful indie developers work 6-8 hours a day (not 12+) because focused solo work is more productive than office work with meetings. Block your calendar: 2-3 hours of deep coding in the morning, marketing and support in the early afternoon, and planning/learning in the late afternoon. Take weekends off. Burnout kills more indie careers than bad products.
Focus on Revenue, Not Features
Your instinct will be to build all the features you have been dreaming about. Fight that instinct. In your first 90 days, every hour should be judged by one question: does this activity increase revenue?
Improving your onboarding-to-paywall conversion from 3% to 6% doubles your revenue from existing traffic. Adding a dark mode does not. Optimizing your App Store listing to rank for a high-volume keyword brings in hundreds of new users per month. A custom animation on the settings screen does not.
The features that feel the least like "real engineering work" are often the ones that move revenue the most: paywall copy, screenshot design, onboarding flow, push notification timing. Embrace the business side. Check our monetization guide for specific strategies.
Build in Public
Share your journey publicly. Post weekly updates on Twitter/X. Write about your metrics (revenue, downloads, conversion rates). Share what you are building and why. This does three things:
- Marketing for free. Every post about your app is free exposure. The indie developer community is genuinely supportive, and build-in-public threads consistently drive downloads.
- Accountability. When you commit publicly to a shipping date, you ship. When nobody is watching, it is easy to let weeks slip by.
- Network building. Other indie developers become collaborators, beta testers, and friends. The loneliness of solo work is real, and this community connection matters more than most people realize.
Real Stories: Developers Who Made the Leap
Theory is useful. Real stories are better. Here are developers who went from employment to full-time indie, with honest details about how it went.
Antoine van der Lee: The Gradual Transition
Antoine is the creator of RocketSim (a developer tool for the iOS simulator) and the SwiftLee blog. In January 2023, he negotiated a four-day work week at WeTransfer, spending every Friday on his side projects. His indie revenue grew steadily, and the financial projections showed he could go full-time indie by 2026 if growth continued. This gradual approach, reducing employment one day at a time, is one of the safest transition strategies. It lets you validate revenue while still having a paycheck.
David Smith: 59 Apps Before the Breakout
David Smith shipped 58 apps over 12 years before Widgetsmith hit #1 in the US App Store in September 2020 with 100 million downloads. No marketing budget. Zero paid ads. Pure organic growth driven by iOS 14's home screen widgets. The lesson is not "build 59 apps." The lesson is that persistence, platform knowledge, and being in the right place at the right time compound over years. Smith was a full-time indie developer long before Widgetsmith because he had built a portfolio of apps that collectively generated enough income to sustain him.
Roman Koch: The Honest Struggle
In 2025, Roman Koch shipped 8 digital products, quit his stable developer job, and earned $1,464 in total revenue for the year. Not $1,464/month. Total. He publicly shared that most of his apps failed silently in the App Store, and that he underestimated how much marketing and distribution matter compared to code quality.
I include this story because survivorship bias is real in the indie community. For every Flighty ($500K/month with 3 employees), there are hundreds of talented developers whose apps never find an audience. The difference is usually marketing, distribution, and timing, not code quality.
The Portfolio Approach
One developer documented on Indie Hackers how they went from a single failed app to a 30-app portfolio generating $22,000/month in under a year. The approach was radically different from the single-product strategy: build fast, ship fast, keep what works, kill what does not. Each app was a small, focused utility that took 1-2 weeks to build. The winners funded the next experiments.
This strategy is not for everyone. It requires extreme discipline and the ability to let go of apps that are not working. But it reduces risk by diversifying your revenue across multiple products.
The Non-Obvious Mistakes That Kill Indie Careers
I have watched enough indie journeys (including my own stumbles) to identify the patterns that consistently lead to failure. These are the mistakes that are obvious in retrospect but invisible in the moment.
1. Building for a Year Without Shipping
The longer you build without shipping, the more attached you become to the idea, the harder it is to accept that the market does not want it, and the more time you have wasted. Ship in 4-6 weeks. If nobody wants version 1, nobody will want version 1 with custom animations and a dark mode.
2. Treating Marketing as Optional
"If I build a great product, people will find it." No. They will not. There are over 1.8 million apps in the App Store. Discovery does not happen by accident. You need to actively market your app from day one. ASO, content marketing, social presence, community engagement. Budget at least 30% of your working time for marketing and distribution. It feels wrong as a developer. Do it anyway.
3. Ignoring Retention in Favor of Acquisition
Getting new users is exciting. Keeping existing users is boring. But retention is what makes subscription businesses work. A 5% improvement in monthly retention compounds into a massive revenue difference over a year. Fix your onboarding, reduce friction in the core experience, and send thoughtful re-engagement notifications before you spend a dollar on acquisition.
4. Comparing Yourself to Outliers
Flighty makes $500K/month. Widgetsmith had 100 million downloads. These are incredible outcomes, and they are not your benchmark. Your benchmark is covering your expenses and building a sustainable business. $5K/month with low stress and full creative freedom is a life-changing outcome that puts you ahead of 95% of indie developers.
5. Going Full-Time Too Early
The excitement of quitting can override the math. If your app makes $200/month and you have 4 months of runway, you are not going full-time indie. You are going unemployed with a side project. Wait until your revenue covers at least 30-50% of your expenses and you have 12+ months of runway for the rest. Patience here prevents panic later.
Community and Resources
Going indie does not mean going alone. These communities and resources have been consistently valuable for indie iOS developers:
- Indie Hackers: The largest community of bootstrappers and indie developers. Great for accountability, feedback, and learning from others' metrics.
- Twitter/X iOS Dev Community: Follow indie developers who share revenue numbers and strategies. The #buildinpublic and #iosdev hashtags are active. Accounts like @jordibruin, @stroughtonsmith, and @_david_smith are worth following.
- Under the Radar podcast: David Smith and Marco Arment discuss the practical realities of indie iOS development weekly. Grounded, honest, no hype.
- RevenueCat's State of Subscription Apps report: Free annual report with the most comprehensive data on app subscription economics. Essential reading.
- Swift by Sundell, Hacking with Swift: Technical resources for leveling up your Swift and SwiftUI skills.
- Adapty's blog: Practical content about paywall optimization, subscription strategy, and going indie.
Your Roadmap Summary
Here is the full timeline distilled into actionable phases:
| Phase | Timeline | Goal | Key Activities |
|---|---|---|---|
| 1. Side Project | Months 1-6 | Ship MVP, get first paying users | Build in 4-6 weeks, launch, learn metrics, iterate |
| 2. Revenue Building | Months 6-18 | Reach $1K-$3K MRR | Optimize conversion, build marketing channels, develop business skills |
| 3. Transition Prep | Months 12-24 | Save 12-18 months runway | Stabilize revenue, sort insurance, build 90-day plan |
| 4. Full-Time Indie | Day 1+ | Grow to $5K-$10K MRR | Focus on revenue, establish routine, build in public, avoid burnout |
This timeline is not a guarantee. Some developers move faster. Roman Koch went full-time after months and is still finding his footing. David Smith spent 12 years before his breakout. Antoine van der Lee took the gradual route over several years. The timeline that works is the one that fits your financial situation, your risk tolerance, and your personal circumstances.
Ship Faster, Learn Faster
The single biggest accelerator on this roadmap is reducing the time between "I have an idea" and "it is live in the App Store." The Swift Kit gives you auth, onboarding, paywalls, analytics, Supabase backend, and an AI module out of the box. That is weeks of infrastructure work compressed into an afternoon. The faster you ship, the faster you learn, and the faster you grow revenue. Get it here for $99 one-time.
The Bottom Line
Going from side project to full-time indie iOS developer is one of the most rewarding paths in tech. You own your time, your creative direction, and your income ceiling. But it requires more than just being a good coder. It requires business skills, financial planning, marketing discipline, and the patience to let compound growth do its work.
Start while you are employed. Ship fast. Learn from your metrics. Build revenue gradually. Save aggressively. And when the math works, make the leap.
For more on the financial side, read how much indie iOS developers actually make and our breakdown of growing from $0 to $10K MRR. For the technical foundation, our 2026 tech stack guide covers every tool you need.