Shipping Apps

Everyone romanticizes the one big idea, the startup you pour three years into and either win huge or lose everything. I do the opposite. I build small apps, ship them fast, and let the winners reveal themselves. That is not settling for less. It is the smarter game for a solo builder, and here is the full reasoning. Small apps actually ship A big idea has a hundred features standing between you and launch, and you will build most of them before you ever learn whether anyone wants the thing at all. A small app has one clear job. You can build it, ship it, and get real-world feedback in days or weeks instead of years. Shipped-and-learning beats unshipped-and-perfect every single time, because an app in the store is generating information and an app on your hard drive is generating nothing but anxiety. The faster you ship, the faster reality starts correcting your assumptions. ...

You can finish a great app and still be weeks away from your first user, because publishing has its own setup that nobody warns you about. The accounts, the identity checks, the review processes, and a few surprise requirements all take real, unavoidable time. Here is exactly what you need to get an app onto the App Store and Google Play, what it costs, and the traps that catch first-timers, so the publishing phase is a planned step instead of a panicked scramble the week you wanted to launch. ...

Pricing is the decision indie developers agonize over least and should agonize over most. It quietly determines who installs your app, how much you earn per user, how your reviews read, and whether you have a business or a hobby. There is no universally correct answer, but there is a right answer for your app, and you can reason your way to it. Here is how to think about the four main models. ...

The most expensive mistake in app development is not a bug. It is spending two months building something nobody wanted, which you could have learned in two days. Validation is the cheap work you do up front to avoid the expensive work of building the wrong thing. It is also the step solo builders skip most, because building is fun and validating feels like a chore. Here is how to do it without it becoming a chore, or a crutch. ...

As a solo founder you are the developer, the designer, the marketer, the support team, and the accountant, all at once, with no one to hand anything to. The constraint is never ideas and rarely skill. It is time and energy, and how you spend them decides whether you ship for years or flame out in months. After building and shipping a string of apps alone, here is what actually keeps the machine running. ...

The first time the App Store rejects your app, it feels like a personal verdict on your worth as a developer. It is not. Rejections are a routine, expected part of publishing, they happen to everyone, and almost all of them are fixable. Learning to handle them calmly, instead of spiraling, is a real skill that saves you time and stress on every app you ship. Here is how to think about rejections and how to get through them. ...

For most companies, privacy is a legal department problem: a policy to publish, a box to tick, a risk to manage. For an indie developer, privacy can be something far more useful, a genuine product strategy that differentiates your app, earns trust, and quietly simplifies your whole business. The companies built on collecting data cannot easily copy you, because their model depends on the very thing you are refusing to do. That asymmetry is an opportunity. Here is how to think about privacy as a feature instead of a chore. ...