TL;DR
Build your second app once your first is stable and earning, one at a time. Pick something adjacent so you reuse what you learned, ship it, and sunset apps that do not perform so you never spread yourself thin.
Sticking to one app is great for learning, but eventually you notice ideas passing you by, or your first app plateaus. Building more apps can smooth your income and open new growth - but done carelessly, it just scatters your attention across half-finished projects you cannot maintain. I'm David, and adding apps deliberately, one at a time, is what let me grow without losing the quality that made my first app work.
Stabilize your first app first
Do not build a second app until your first reliably works and earns. A solid first app - stable, well-reviewed, retaining users - is proof you can finish and maintain something. Jumping to a new app while the first is still buggy just leaves you with two rough apps and twice the support. Prove you can win with one before adding another.
Pick an adjacent app first
The easiest second app is one near the first, where your code, your skills, and even your users partly carry over. If your first app is a habit tracker, a focus timer or a streak app may share components and audience. An adjacent app lets you reuse what you built and learned instead of starting from zero, so it ships faster and stabilizes sooner than something totally unfamiliar.
Ship small before you scale it
Treat a new app as an experiment. Build a small version, ship it, and see how it actually does - downloads, retention, revenue - before pouring months in. A lean first release tells you whether the idea works without risking much. If it flops, you learned something cheaply rather than sinking huge effort into an app nobody wants.
- Stabilize and prove your first app before starting another
- Pick an adjacent app that shares code or audience
- Reuse your components, template, and EAS setup
- Ship a small version before investing heavily
Watch each app's numbers
As you add apps, track how each one performs separately - profit, retention, how much support it takes. Some apps look exciting but turn out flat or high-maintenance once they are live. Clear numbers per app show you which to lean into and which to quietly sunset. This is where good tracking directly turns into smarter expansion.
Do not spread yourself too thin
There is a real limit to how many apps you can build, update, and support well. Chasing every idea at once means you are mediocre at all of them and your backlog becomes chaos. It is usually better to run a few apps you maintain deeply than a dozen you neglect. Add an app, let it stabilize, then decide whether to add another.
Expansion is a lever for growth, not a way to escape a weak first app. Stabilize one app, add adjacent ones one at a time, ship small, and keep only the apps that earn their place. That is how you grow your portfolio without losing your quality.
Common questions
When should I build a second app?
Once your first app reliably works and earns, and you can maintain it. A stable, well-reviewed first app is proof you can finish and support something. Branching out before you can win with one just leaves you with two rough apps and twice the support burden.
Which app should I build second?
Usually one adjacent to your first, where your code, skills, and even users partly carry over. If your first app is a habit tracker, a focus timer may share components and audience. Adjacent apps let you reuse what you built, so they ship faster and stabilize sooner.
How do I avoid wasting effort on a new app?
Ship a small version first and watch how it does - downloads, retention, revenue - before pouring months in. Treating a new app as a lean experiment protects your time. Scaling up only after a small release performs is far safer than committing heavily on a hunch.
How many apps can I handle at once?
There is a real limit set by how many you can build, update, and support well. Chasing every idea leaves you mediocre at all of them and turns your backlog into chaos. A few apps you maintain deeply usually beats a dozen you neglect.
How do I know if an app is worth keeping?
Track each one's numbers separately - profit, retention, and how much support it takes. Some look exciting but turn out flat or high-maintenance once live. Clear per-app numbers show you which to lean into and which to quietly sunset before they drain your time.
Should I reuse code from my first app?
Yes, wherever you can. Carrying over components, your project template, your EAS setup, and your understanding of store review makes a second app far faster to build with Claude Code. Reuse your own proven pieces before writing anything new from scratch.
Keep going
Grow your portfolio without losing your quality
Get the other 21 in the app type stack, plus the full App Store Launch Club community - $9/mo, cancel anytime.
Join the Club