different species of crabvietnamese mud crabsoft-shell crab
3
11 Comments

I spent a month building my first consumer app. Now I'm realizing I was solving the wrong problem.

A month ago I challenged myself to build a consumer mobile app from scratch.

As a developer, I thought the difficult part would be building it.

It wasn't.

The coding was actually the easiest part.

Now that the MVP is finished, I've realized I've entered a completely different world.

Landing pages.

ASO.

SEO.

Content marketing.

Talking to potential users.

Distribution.

Community building.

Those skills feel much harder than writing code.

I used to think:

Build something useful and people will find it.

Now I think:

You can build something great, and nobody will ever know it exists.

That's been a humbling lesson.

The app is currently in Google Play Closed Testing, so I'm using this time to learn everything I can about launching a consumer product before it goes public.

For founders who've already launched:

What was the biggest thing you underestimated?

For me, it's definitely distribution.

on July 9, 2026
  1. 1

    This is very relatable. Building feels hard until the product is done — then you realize distribution is a completely different skill.
    I’m learning the same thing with my own SaaS. A working product doesn’t mean people will find it, trust it, or care enough to try it.
    The biggest thing I underestimated was how much time has to go into talking to users and finding the right channels, not just improving the product.

  2. 1

    Treating distribution as its own product built in parallel is a much better mental model than treating it as a phase that comes after the real building is done. Turning user objections straight into landing page copy is smart too, it means the two hardest parts of early growth are actually feeding each other instead of being separate tasks competing for the same time.

  3. 1

    The commenters calling out that gap in the title versus the body is a fair catch, distribution and "wrong problem" are genuinely different diagnoses even though they feel the same when you're stuck. Talking to closed-testers directly before touching acquisition channels seems like the right order, otherwise you're optimizing a funnel for a product you haven't actually validated the value of yet. When you do talk to them, are you asking why they opened the app, or why they came back a second time, those tend to surface different answers.

  4. 1

    You learned in one month what takes most engineers years: code is now the cheapest part of a company. Next build, invert the sequence; spend the first two weeks selling the problem (a landing page with a price on it, DMs, a waitlist) and only write code once strangers raise their hands. The fix isn't learning marketing skills, it's sequencing.

  5. 1

    This is a lesson a lot of technical founders eventually discover. Building the product feels like the main challenge because it’s where most of the skills and effort are visible. You can spend weeks solving bugs, improving features, and making everything work — but after launch, the challenge shifts completely.

    Distribution, positioning, and understanding users become just as important as the product itself. A great solution doesn’t create impact if the right people never discover it or don’t understand why they need it.

    I think the biggest mindset shift is realizing that building and marketing are not two separate stages. User conversations, feedback, content, and community should influence the product from the very beginning.

    It’s great that you’re learning this before the public launch. Many founders only realize the importance of distribution after spending months building something nobody knows about. Looking forward to seeing how the app evolves after launch.

  6. 1

    This resonated — I'm shipping a consumer app right now and hit the exact same wall. Coding gives you a green checkmark; distribution gives you weeks of silence before anything moves, and sitting in that silence without quitting turned out to be the actual skill.

    One reframe that helped: distribution isn't a phase that comes after building — it's a second product you build in parallel, with a much longer feedback loop.

    And one concrete thing, since you listed "talking to users" and "content marketing" separately — they're really the same job. The exact objection someone raises in a DM is the headline of your next landing page. Your user conversations are your content pipeline; you just write down the sentences they use, not the ones you'd use.

    Small heads-up from this week too: most "free" launch boards aren't — it's usually a badge swap or a months-long queue. The earned stuff (a couple of honest answers where people already search for the problem) is slower but actually free.

    You're further along than you think just by naming the shift.

  7. 1

    Distribution is the obvious one, and it's real. But the thing I underestimated even more, one layer down: it's not enough to reach people who HAVE the problem — you need people who feel it badly enough to pay to make it go away. I just watched my first paying client work perfectly and still probably churn, because the problem didn't cost him enough to care. Distribution gets you attention; acute pain is what turns attention into money. "Build it and they'll come" is wrong, but so is "distribute it and they'll buy." The real filter is: who's already bleeding? Talk to those people first — the ones actively complaining, not just the ones who fit the profile.

  8. 1

    Marc already called the real thing: "wrong problem" and "distribution" are opposite diagnoses, don't fix one by doing the other. I'll add what to do with the phase you're in right now. Closed testing isn't time to go study launching, it's the one moment you have a captive group who'll actually reply. Message every tester who stopped opening the app and ask what they opened instead and what they expected it to do. You're not fishing for feature requests, you're stealing the exact words they use for the problem. Those words become your store listing, your ASO, your landing copy later. If you can't get five testers to describe the problem in their own language, that's your answer on whether it's the right problem, before you spend a month on channels.

  9. 1

    worth noticing: your title says "wrong problem" but everything under it is distribution — those are opposite diagnoses. if the problem is actually wrong, more ASO/SEO/ads just gets you to "no" faster; distribution only amplifies whatever's underneath it. the closed-testing phase you're in right now is the cheapest chance you'll ever get to find out WHICH of the two you have. id aim those 10 conversations (like the other commenter said) squarely at "is this even the right problem for these people", not at "how do i get users" — before sinking another month into acquisition channels.

  10. 1

    One thing I'd question is whether distribution is always the problem.

    Sometimes it is. But sometimes it's that the product solves a problem people only recognize after they already have the solution. In those cases, marketing has to educate before it can sell, which makes every acquisition channel feel harder. Figuring out which of those you're dealing with changes almost every decision that follows.

  11. 1

    Distribution is the one I underestimated the most too. Built a solid product, assumed "if you build it they will come." Reality: spent weeks on SEO, landing pages, even ran ads — got a handful of users. The thing that actually moved the needle was manual outreach: finding 10 people who fit the exact profile and talking to them directly. It doesn't scale, but it teaches you more about your market than any landing page A/B test ever could.

Trending on Indie Hackers
The feature you're most sure about is the one you should question first User Avatar 117 comments The hardest part isn't building anymore User Avatar 114 comments 5 days post-launch: Top 50 on Product Hunt, zero signups, and why I think that's actually fine User Avatar 111 comments I let 3 LLMs argue on the famous AI "Car wash: Walk or Drive" problem to prove a point. User Avatar 50 comments Built a local-first privacy extension. Looking for feedback. User Avatar 36 comments I spent months chasing clients who already had a webmaster. So I built something that only finds the ones who don't. User Avatar 34 comments