Managing two hyper-niche apps at completely different stages: 6 weeks of marketing one, prepping to launch the other
Hey everyone,
My family and I run a tiny indie studio, and right now we're juggling two very niche products at opposite ends of their lifecycle.
Product 1: TankSync (aquarium care app, causal trend analysis for water parameters, no subscription, local-first). Live since June 4th. We've been grinding organic marketing for about 6 weeks now — cold outreach to YouTube aquarium creators, community building on places like Reef2Reef, weekly build-in-public logs on X. It's slow and manual, but the needle is moving (downloads, App Store impressions up significantly, still zero paying users though).
Product 2: Explant Flow (tracker for plant tissue culture / explant propagation — an even smaller niche than aquarium keeping). Just wrapped final testing, prepping for App Store submission.
The context-switch between "grow a live product" and "get a new one ready to launch" has been a wild ride. Distribution is turning out to be way harder than building.
For those running multiple micro-products: how do you split your energy between growing what's live and launching what's next? Would love to hear how others handle it.
For those running multiple micro-products: how do you split your energy between growing what's live and launching what's next?
And honestly — I'd love to hear from anyone who's done this kind of marketing without a tech background and with limited English. Any tips, tools, or mindset shifts that helped you? I'm figuring this out as I go, and any experience you're willing to share would mean a lot.
The limited-English + non-technical-marketing part is the bit I can speak to directly. I run a couple of niche apps in unrelated domains (a motorcycle route planner and a TV-tracking app) and launched bilingually, so "my marketing writing isn't in my first language" was a real constraint for me, not a hypothetical. Two things helped more than I expected. First, in a tight niche, domain credibility beats polished English every time — aquarium keepers will forgive awkward phrasing the instant it's clear you understand water chemistry better than they do, so lead with the expertise and let the copy be plain. Second, write the post in your strongest language first and treat the English as a translation pass; composing directly in a second language tends to come out flat and generic.
On the split: I agree Explant Flow should launch quietly. The reason to still ship it now isn't traction — it's that a second live product doubles the surface area for the organic discovery you're already doing by hand. Just don't let it pull real marketing energy until TankSync's funnel actually tells you where people drop off. The analytics thread above (install → first open → the one action that proves value → day-2 return) is genuinely the right next step before you decide anything about the split.
This is genuinely useful, thank you. The "write in your strongest language first, translate second" tip is one I hadn't thought to try — I've been forcing myself to compose directly in English, which probably explains why some of my posts feel a bit flat.
And the framing on the split — "ship it for surface area, not traction yet" — actually resolves something I'd been going back and forth on. Appreciate you laying out both the reasoning and the caveat.
Running two products at different stages solo is rough. I'd be wary of splitting attention 50/50 right now, since TankSync already has 6 weeks of data to learn from and Explant Flow doesn't yet.
Where in the TankSync funnel are people dropping off? Are they never even trying it, or trying and not converting to paid? Those are two very different fixes. Happy to compare notes if it's helpful.
Honestly, that's the gap in my data right now — I have download numbers and store impressions, but no visibility into what happens after someone installs. I don't know if people try it and bounce, or never open it at all.
Would love to compare notes on how you'd set up that kind of tracking for a tiny indie app without over-engineering it.
For a tiny app, you really only need 3-4 events, not a full analytics platform: install -> first open -> the one action that proves someone actually got value -> day-2 return.
Firebase Analytics (free) or Amplitude's free tier both handle it with zero infrastructure work. What matters isn't the tooling though, it's picking the right "proves value" event, otherwise the data just tells you the wrong story more precisely. If you focus on the ones mentioned above that should give you a clearer idea into what's happening.
This is incredibly specific and useful, thank you. I'm not technical myself, so I'll pass this along to my brother and sister-in-law (they built the app) — the "one action that proves value" framing is exactly the kind of clarity we were missing. Really appreciate you laying out the actual event funnel instead of just naming a tool.
Reading this, I wonder if the harder decision isn't how to split your time—it's which product deserves to compound.
Launching a second product creates another opportunity, but it also resets the trust and distribution you've already started building. At some point, growing the first product and launching the second stop competing for time and start competing for momentum.
"Competing for momentum, not just time" — that phrasing just articulated the exact gut feeling I've been struggling to put into words. You hit the nail right on the head.
It really does feel like a reset button on trust. Since our two apps serve completely different niche audiences (aquarium keepers vs. plant tissue culture hobbyists), we can't easily cross-promote or leverage the distribution we've already built.
The honest reason we're doing both is that our tiny family team has distinct domain expertise in both fields. But your point about compounding is well taken — so practically, I think it means: let Explant Flow launch quietly, and keep doubling down on TankSync's momentum since that's the one with real traction already. Only shift real energy over once TankSync's momentum can hold on its own.
Curious if that matches how you'd approach it, or if you'd go further and just pause one entirely?
That's the part I'd be hesitant to answer in a few lines.
I don't think the key decision is whether to pause one product or keep both alive. There's an assumption underneath that choice which changes what the right answer actually is.
I'd rather explain the reasoning properly than give you an oversimplified opinion.
If you're open to it, what's the best email to reach you on?
Appreciate you taking this seriously! I'd actually love to hear the reasoning here in the thread if you don't mind — I think it'd be useful for others reading this too, and I'm genuinely curious what assumption you think I'm missing.
Happy to share the short version.
The assumption I'd question isn't whether one product deserves more time.
It's whether momentum is actually the resource you're allocating.
If that assumption changes, the answer to "focus on one or build both" can change with it.
That's the part I found interesting.
That's a sharp distinction. I think I was assuming momentum works like a shared pool — like both apps are drawing from the same tank of attention. But if it's not that... then what would you say momentum actually is? Something more like trust with a specific audience, that doesn't transfer between niches?