TL;DR
Managing several apps well comes down to a simple system, not memory. Track what each app earns, where its project and assets live, and what needs updating, so nothing gets neglected or breaks quietly in the background.
Building one app is easy to keep in your head. Running three or five at once is where it falls apart. Projects pile up, you forget which app needs an update, one sits neglected for months, and a user reports a crash in an app you cannot even remember how to build. I'm David, and the builders who scale calmly are not more organized by nature - they have a simple system that does the remembering for them. If you rely on memory, more apps just means more chaos and more silent breakage.
Track what you own
You cannot manage a portfolio you cannot see. Keep one running list of every app you have live, even a basic one. For each app, note what it does, where its project lives, what it earns, and when you last updated it. This single list is the difference between a business you can grow and a scatter of apps you are slowly losing track of.
Know each app's numbers
As your portfolio grows, unclear performance costs you focus. You need to know which apps earn, which are flat, and which are quietly bleeding support time. Check each app's App Store Connect and Google Play Console analytics so you can see downloads, revenue, and retention per app. It sounds fussy until the day you are pouring effort into your weakest app while your best one goes stale.
- Keep one running list of every app you have live
- Record where each app's project, assets, and store accounts live
- Note downloads, revenue, and retention for each app
- Mark whether each app is thriving, flat, or needs attention
Flag what needs an update
A neglected app is dead money - it earns less over time and can break when the stores change their rules. Your list should make it obvious which apps have not been touched in a while or have a known bug waiting. Reviewing that gap regularly is one of the most profitable habits in a portfolio, because it turns a fading app into one that is stable, ranked, and earning again.
Watch for dead weight
Some apps just do not perform no matter what. Tracking how each one does over time shows you what is not working, so you can invest in a fix, sunset it, or leave it running quietly. An app that earns nothing but eats support hours is a drain. A quick monthly review of your weakest apps keeps your effort going to the ones that actually pay.
Know your capacity
There is a real limit to how many apps you can build, update, and support well. Pushing past it means apps go stale and users get ignored. If your update backlog keeps growing, you are shipping apps faster than you can maintain them - the fix is to slow new launches and stabilize what you have, not cram in more. Managing a portfolio well sometimes means not building the next app yet.
A growing set of apps is only an asset if you can see it, measure it, and maintain it. One running list with location, numbers, and status turns a chaotic set of projects into a real business you can scale without losing track of a single app.
Common questions
How many apps can I realistically manage?
It depends on how complex they are and how fast you can update them, so there is no fixed number. The real test is your update backlog: if it keeps growing, you are shipping apps faster than you can maintain them. The fix is to slow new launches and stabilize what you have.
Why should I record where each app's project lives?
Because without knowing where the code, assets, EAS config, and store accounts are, a simple update becomes an archaeology dig. Write it down the moment you ship each app - you will not remember months later, and a lost project can leave a user-facing bug unfixable.
How do I keep track of each app's performance?
Check each app's App Store Connect and Google Play Console analytics for downloads, revenue, and retention, and note them in your list. This matters most the day you catch yourself pouring effort into your weakest app while your best one goes stale. Per-app numbers keep your focus honest.
What is the most profitable portfolio habit?
Regularly reviewing which apps have gone stale or have a known bug waiting. A neglected app earns less over time and can break when the stores change rules. Turning a fading app back into a stable, ranked one is one of the fastest ways to unlock value already in your portfolio.
What should I do with apps that will not perform?
Track how each does over time so weak ones stand out, then invest in a fix, sunset it, or leave it running quietly. An app that earns nothing but eats support hours is a drain. A quick monthly review of your weakest apps keeps your effort on the ones that pay.
Do I need special software to manage a portfolio?
Not at first. A simple running list or spreadsheet with each app's location, numbers, and status covers most builders early on. Consistency matters more than tools. You can add dashboards as your portfolio grows, but a list you actually keep current is enough.
Keep going
Turn a scatter of apps into a business you can scale
Get the other 37 in the app user stack, plus the full App Store Launch Club community - $9/mo, cancel anytime.
Join the Club