Quantum Crypto Terminal
Crypto technical analysis: RSI, MACD, Fibonacci & more
Visit Website
June 23, 2026
I built a crypto technical analysis app as a solo developer
Hey IH! Solo Android developer here. Built Quantum Crypto Terminal — RSI, MACD, Fibonacci, multi-timeframe analysis, plus crypto news and an economic calendar.
Launched on Play Store a week ago. Almost zero organic downloads so far. Just tried Product Hunt too.
Figuring out:
- How to get traction with no marketing budget
- Was paid-upfront the right call vs freemium?
- Which crypto communities are worth my time
Open to feedback on the app or the approach!
5 Comments
Reading this, I found myself less interested in which acquisition channel you choose next.
What I'd be cautious about is how much weight you're giving the "almost zero downloads" result when thinking about pricing.
The same outcome can sometimes end up being used as evidence for very different conclusions.
That's the part I'd be most curious about before changing anything.
Fair point — you're right that I can't separate "wrong pricing" from "no visibility" yet. I think I'll wait until I've actually driven some real traffic (Product Hunt, communities) before changing pricing, so I'm not reacting to noise. Appreciate the nudge to slow down on that decision.
I think that's exactly the part I'd be most interested in.
Not whether pricing should change yet, but how much evidence would actually be required before treating pricing as the explanation rather than visibility.
I've got a few thoughts on that, but it's probably more than I'd try to unpack properly in a thread.
What's the best email to reach you on?
Happy to chat — feel free to send me a message here on IH, or I can share an email once we get into specifics. What's the general direction of your thoughts?
Broadly, I don't think the interesting question is whether pricing is wrong yet.
It's how you'd distinguish between "pricing is limiting demand" and "the current level of visibility simply isn't capable of producing evidence about pricing in the first place."
Those can lead to very different next decisions, even when the observable result looks identical.
I've got a few thoughts on that, but it's probably more than I'd try to unpack properly in a thread.
Happy to continue by email if you'd like.