B Builderlog
Builderlog ·Shipping Mini-Apps ⑥ ·Jun 21, 2026 ·2 min read

How My Plan to Get 100 Users With No Ads Fell Apart in 3 Weeks

#user acquisition#growth#solo dev#post-launch#marketing

The app was out. It cleared store review, it had a link. And nobody came. Which is obvious — except I never managed to think it was obvious.

On launch day I did exactly one thing. I posted “made this” in two communities I’d been lurking in. The response was so-so. A few comments, a few likes. But the number of people who actually installed it was around fifteen. And half of those were people I already knew.

That’s when a weird confidence kicked in. The “I just need to promote it more” thought. That confidence cost me three weeks.

The launch-post funnel

Saw the post
two communities
Reacted (likes / comments)
Installed
~15 — half already friends
Came back
the number that actually decides it
The shape of the drop-off after one launch post — illustrative, not measured.

I Added Channels, the Numbers Didn’t Budge

Five communities, three open chat rooms, two social accounts. Every time I posted, there’d be a trickle of installs. But a pattern emerged. Two days of a little blip after posting, then dead silence. No matter how many channels I added, people came in only as fast as I could write posts by hand.

Shipping wasn’t a feature, it was labor. And that labor didn’t scale.

Three weeks in, I’d gathered 68 users. That’s 68% of the goal, but it felt like getting a test back with a 68 on it. Because I’d figured out the problem was the structure, not the number.

There Was an Assumption I Got Wrong

I’d been unconsciously believing that “a good app spreads.” It doesn’t. At least not a mini-app aimed at a needle-thin need like a convenience-store BOGO app — it only gets installed if it shows up at the exact moment someone needs that exact thing. A community post can’t create that timing. It’s visible the instant you post it, and then it sinks down the feed.

People search when they need it — not when I happen to post.

Once I understood that, I started turning toward search traffic. Instead of the app’s name or feature list, I rewrote the store description in the words people would actually type. Tiny, but there was a change.

I Did the Math on Three Weeks of My Time

I roughly tallied the hours I’d put into distribution. Writing posts, making images, checking responses, rewriting. It was probably north of 40 hours. In that time I could’ve built maybe two more app features. I still don’t know which would’ve been the better call.

I spent 40 hours on distribution and got 68 users. I’d rather not run the efficiency math on that.

Honestly, this post is part of the distribution too. And that’s kind of funny.

TL;DR

”Distribution is harder than building” — turns out you don’t really believe it until you’ve hit the wall yourself.

Next time: I looked at how those 68 people actually use the app, and it was nothing like what I expected.