Developer reports zero installs after launching BOGO app, revises listing and distribution strategy

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

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. I Believed People Would Come If I Posted the Link 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. 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. Get the $31 Stack Prompt Pack — $19 The exact prompts, cost calculator, and n8n templates from this stack.

2 hours ago

I Shipped It. Nobody Came. Here's What Zero Taught Me.

I pushed the final build of the BOGO deals app on a Tuesday night, wrote a short launch post, and then watched the analytics dashboard sit completely still for four days. Zero installs. Zero clicks. Zero anything. My first reaction was embarrassment. My second reaction, eventually, was that zero is actually one of the more honest things a launch can return. The Dashboard I Didn't Want to Look At The first morning after launch I opened the analytics tab and closed it in about three seconds. I told myself the data needed time to "warm up," which is a very comfortable lie. By day two I was checking it less than my email. By day four I finally sat with it long enough to actually read what nothing was telling me. And nothing was telling me a lot. The app store listing had 47 impressions. Forty-seven people saw the icon and the name and scrolled past. That's not "nobody found it." That's "47 people found it and none of them were curious enough to tap." That distinction hit differently than I expected. Zero installs isn't silence — it's 47 people quietly telling you something is wrong above the fold. Reading the Shape of the Failure I went back through the whole funnel with fresh eyes. The listing had screenshots I'd made in a hurry, a description I'd written at midnight, and a title that made sense to me but probably meant nothing to someone scrolling fast. The icon was fine, I think. But "fine" doesn't make anyone stop. What I didn't expect was how much you can triangulate from a zero. If impressions were zero, the problem is discoverability — keywords, category, word of mouth. If impressions are decent but installs are zero, the problem is the listing itself — screenshots, title, first sentence of the description. I had the second problem. The app existed in the world. People were seeing it. They just weren't interested. That's actually more fixable than invisibility. There's a difference between "nobody saw it" and "people saw it and passed." The fix for each is completely different. The Failure Log, Unedited Here's what I wrote in my notes the week after launch. I'm posting it as-is because I think cleaned-up retrospectives are kind of useless. Screenshots showed the UI, not the value. I put effort into making the screens look polished and zero effort into showing why anyone would care. The description opened with what the app does, not what problem it solves. "Browse BOGO deals near you" is a feature. "Don't miss a deal before it expires" is a reason. I launched on a Tuesday night because I was done, not because it was a good time. I announced it to roughly no one. I built the whole thing without talking to a single person who might actually use it. That last one is the one that stings. I've written about this before — the trap of building in a comfortable vacuum — but I walked right back into it anyway. Episode after episode and I still did it. What I Actually Changed I rewrote the first screenshot caption. I rewrote the description opening. I asked two people who regularly hunt for grocery deals to look at the listing cold and tell me what they thought it was. One of them thought it was a coupon printer. That was useful information. Installs ticked up. Not a flood. But the line stopped being flat. A rewritten caption on screenshot one did more than the entire launch post I spent an hour on. The Part Nobody Posts Zero users after a launch feels like a verdict. Like the market looked at your thing and issued a formal ruling. It isn't. It's just the first round of data, and it's less about your app and more about how you presented it to a stranger who owes you nothing. I'm less embarrassed about the zero now than I was that first morning. I'm more embarrassed that I launched without showing the listing to a single real person first. That one I can't blame on the algorithm. TL;DR: Zero installs after launch isn't a dead end — it's a specific, readable signal about where the funnel broke, and fixing the listing is often faster than rebuilding the app. Next episode: I try paid installs for the first time with a very small budget, and learn what "low quality traffic" actually means in practice. Get the $31 Stack Prompt Pack — $19 The exact prompts, cost calculator, and n8n templates from this stack.

6 hours ago