Building for Fun, Scaling for Profit: Lessons from a Decade of Indie App Development

An indie developer's scarcest resource is rarely compute. It is focused time. Every product competes for design, implementation, store operations, support, marketing and maintenance from the same limited calendar. A feature that appears free because it has no vendor bill may be the most expensive item in the portfolio.

Evaluate ideas through recurring attention as well as launch effort. Ask how often data changes, how many edge cases create support, which platform policies can force updates and whether the product becomes more useful without continuous manual input. The strongest small products turn existing work into repeatable value.

A free user creates distribution, feedback and the possibility of future conversion, but also consumes infrastructure and support. Calling that user an asset only makes sense when the product knows what value grows with adoption: better data, word of mouth, a larger market for a paid layer or evidence that improves future decisions.

Measure the whole funnel rather than celebrating installs. Activation, repeated use, retention, conversion and cost per active user show whether reach is compounding. If every additional user creates the same manual work and no durable advantage, growth can make the business more fragile.

Pricing is a statement about what the product will continue to deliver. Subscriptions fit recurring value and recurring cost; one-time purchases fit a bounded promise; advertising exchanges attention for access. None is automatically fair or profitable. The model should match how often value appears and what users expect after paying.

Experiments should protect trust. Explain the paid boundary, preserve already-purchased value and avoid dark patterns that create short-term conversion at the expense of ratings and retention. A smaller base of satisfied paying users can be healthier than a large audience trained to reject every sustainable option.

The lowest initial price can hide migration work, lock-in, missing observability and manual operations. The opposite mistake is building an enterprise platform before product demand exists. Good indie architecture preserves optionality at the boundaries that are costly to change while keeping the rest deliberately ordinary.

After a decade, profitability looks less like one clever launch and more like disciplined portfolio management: reuse proven capabilities, stop products whose economics no longer work, invest in distribution and keep enough margin to maintain trust. Sustainable software is a sequence of explicit trade-offs, not a lucky download graph.