Here's the thing nobody tells you when you set out to build an app on your own. The building is the easy part. Not easy easy — but it's the kind of hard I understand. A bug has a cause and a fix. A slow generator can be profiled and sped up. You chip, you test, it gets better. Honest work with a visible finish line.
Then you launch. You put it on the obvious sites, you post it to the obvious places, you press the button — and you get the one thing you weren't braced for. Not bad reviews. Not angry feedback. Silence. No views. No clicks. The crickets. You built a whole thing and dropped it into a void that didn't even echo.
WHY “NOBODY KNOWS YOU EXIST” HAS NO STACK TRACE
Discovery is harder than code because it doesn't behave like code. A crash gives you a stack trace. “Nobody can find you” gives you nothing to grep. There's no error to fix — there's just an absence, and absences don't come with line numbers.
The brutal mechanic underneath it: a brand-new website has no authority. Search engines don't trust a domain that's a few weeks old, so they won't rank it for anything competitive for months, no matter how good the page is. You can write the clearest, most honest guide on the internet, and if the domain's young and nobody else links to it, it sits in the dark exactly where you put it.
THE PART WHERE I GOT IT WRONG
My first instinct was the engineer's instinct: brute-force it. If one good page won't rank, write a hundred. So I did — piles of pages, chasing every keyword and variation I could think of. “X vs Y.” “How to solve X.” The lot.
It was the wrong move, and worse, it was actively counterproductive. A heap of thin, near-identical pages doesn't read as “thorough” to a search engine — it reads as low-quality noise, and it can drag the whole site down with it. So I spent a day doing the opposite of building: I deleted around forty-seven of them, folding each one into the single strong page it had been a watered-down copy of. Turns out the lesson everyone repeats is just true: it's quality, not volume. One real guide beats ten doorways.
WHAT ACTUALLY MOVES THE NEEDLE (NO HACK)
I went looking for the growth hack. There isn't one — or if there is, it isn't for a solo dev with a wordless puzzle app and no audience. What actually works is slow and unglamorous: be genuinely useful where your players already are (without spamming them), make a real thing worth linking to, lean on the app store's own search, and then wait, because good content compounds over months, not days. Reach is earned off-site and over time. You cannot clever your way to an audience overnight from inside your own codebase.
That was the humbling bit. Every other problem in this series, I could out-work. This one I mostly have to out-last.
WHERE I AM RIGHT NOW
Honestly? Still mostly crickets. This isn't the post where I tell you one trick fixed it, because that post would be a lie. What I've got instead is a thing I'm genuinely proud of, a habit of showing up and being straight about it, and the patience to let the slow stuff do its slow work. The ghost isn't in a hurry, and it turns out I'm learning not to be either.
So if you've read this far, you're one of the people who found it — which genuinely means a lot. The best thing you could do is just play today's puzzle, and if it's any good, tell one person. That's the whole growth strategy, really. One person at a time.
— the (still-yelling-into-the-void) dev behind GridJoy 👻