The fantasy goes like this: you build a small app, it climbs the charts, and revenue screenshots replace your alarm clock. The reality, based on the postmortems and public numbers indie developers have shared over the past decade, is both harder and more interesting. Here’s what shipping alone actually involves, and what the people who’ve done it well keep saying.
You are the entire org chart
A solo developer is a engineer, designer, support desk, marketer, accountant, and compliance department. The engineering is maybe a third of the job. Marco Arment, who has run Overcast essentially alone since 2014, has described the rhythm honestly: writing code is the fun part squeezed between support email, server upkeep, and the yearly ritual of rewriting things Apple moved.
The support part surprises people most. Every feature you ship generates questions, and every question arrives in your personal inbox. Experienced indies develop machinery for this — canned replies, FAQ pages, in-app help — not because they’re impersonal, but because the alternative is drowning.
Maintenance is the product
Every June, Apple announces a new OS at WWDC, and every September, millions of users install it overnight. For a solo developer that means weeks of unpaid work: testing betas all summer, fixing what broke, and shipping a compatibility update before the reviews turn mean. Multiply by new screen sizes, new privacy rules, and deprecated APIs, and you understand why a $4.99 app that keeps working for five years is quietly heroic.
This is also why good indie apps seem to evolve slowly. The developer isn’t lazy — they’re spending most of their capacity keeping the floor from rotting.
The risk of one pair of hands cuts both ways
Solo concentration of risk became the whole industry’s cautionary tale in 2023, when Christian Selig shut down Apollo, the beloved Reddit client with millions of users. Reddit’s API pricing change made the business unviable overnight, and because Apollo was one person, there was no pivot budget, no pivot team — just a graceful, transparent shutdown that he wrote up in detail. Millions of users lost an app they loved because a single external decision landed on a single pair of shoulders.
The flip side: one pair of shoulders can also move fast. When users asked Charlie Chapman for a specific ambient sound in Dark Noise, it could ship in the next update rather than the next quarter. No committee, no roadmap negotiation. That intimacy — you email, the author answers, the thing changes — is the entire appeal of indie software.
What solo developers learn the hard way
Read enough indie postmortems and the same lessons repeat:
- Scope is survival. The apps that last do one thing. Dark Noise plays sounds, full stop. Every feature you add is one more thing that breaks in September.
- Charge from day one. Nearly every “I made it free and added paid later” story ends with regret. Free users give feedback, paying users give sustainability.
- Marketing is not optional. The build-it-and-they-will-come story is almost always false. The developers who make it are the ones writing, posting, and showing work in public long before launch.
- Ship imperfect. Version 1.0 of every successful indie app is embarrassing to its author. The 1.1 that people love only exists because 1.0 got out the door.
Why it’s still worth it
Ask solo developers why they keep going and the answers are consistent: no meetings, no permission, and the strange joy of a support email that says “your app changed how I work.” The money is real for some, modest for most. But the product — a small, sharp tool with a person behind it — is something a big company structurally cannot make.
If you’re curious how solo developers handle the emotional side of running a business alone, read my piece on building in public — sharing real numbers with strangers is its own kind of risk.
Pingback: App Store Review Survival Guide: 12 Mistakes That Get First Apps Rejected – App2Best