A guy named Max, zero coding background six months ago, built a workout app using Claude, hit 1,000 active subscribers and 20,000 iOS downloads, and is now pulling in $13,000 a month. The lesson everyone is drawing from it: the tools lowered the floor, but what really separates winners is "topic selection, distribution, and consistent public documentation."
That last part -- build in public -- is being treated as the secret sauce. I want to argue it is not.
The framing in the post, and echoed across the comments, is that AI coding tools have commoditized the technical side of building apps. Fine, I mostly agree with that. But the conclusion people jump to is that the differentiator is now building in public: filming yourself, posting your process daily, narrating your journey. Max shot 5 to 10 videos a day, analyzed scroll-away rates, turned the best-performing organic content into paid ads. That is presented as the moat.
Here is the problem: that is not a moat. That is a distribution channel. And there is a meaningful difference.
A moat is something that is hard to copy. A TikTok or Instagram content strategy built around your founder story is, by definition, one of the most imitable things on the internet. The moment your first video performs, anyone watching that video can reverse-engineer your format, your hook, your editing rhythm, and your posting frequency. Many will. Some will do it better.
Max's actual advantage in the fitness space probably has nothing to do with his willingness to document his process. It has to do with when he started, which fitness niche he picked, and how quickly he could iterate the product based on retention signals. Those are the choices that are genuinely hard to reproduce after the fact. You cannot time-travel back to six months ago and pick the same underserved niche with the same low competition.
Building in public accelerated his distribution, yes. But calling it the thing that "separates winners" puts the emphasis in the wrong place for anyone trying to learn from his story.
Thousands of indie developers are building in public right now. Most of them are not making $13,000 a month. The ones who are not making that money are also filming themselves, also posting their metrics, also narrating their struggles. We do not hear about them because the algorithm surfaces the success stories.
When a community looks at Max's result and extracts "build in public" as the causal variable, it is doing bad statistics. It is like watching someone win a poker tournament and concluding that the winning move was checking on the river. Maybe. Or maybe they just had better cards for most of the game and the check was incidental.
The honest read of Max's story is that he got several things right at once: he chose a niche with real demand, he used AI tooling to keep his development costs near zero, he found a content format that resonated, and he scaled it with paid ads once he had proof. Build in public was one piece of a system. It was not the system.
I am not saying building in public is worthless. For accountability, for early feedback loops, for attracting your first few hundred users who want to root for an underdog, it is genuinely useful. If you are stuck between shipping in secret and shipping with narration, narration is probably better.
But the fitness app community and the indie hacker community have elevated this practice into something closer to a philosophy, and that elevation causes real harm to people who adopt it uncritically. Developers who should be spending time on product-market fit instead spend hours crafting update threads. Founders who need to talk to 20 potential customers instead post a screenshot of their revenue dashboard.
The advice sounds correct because it is partially correct. That is exactly what makes it easy to misapply.
If you want to learn something from Max's story, here is what I think it actually teaches:
AI coding tools genuinely removed the biggest cost barrier for solo founders, which was development time and money. That is real and it matters.
Content-as-distribution works in consumer apps where the founder is the target user and can demonstrate value authentically. Max is presumably a fitness person making a fitness app. He is not performing relatability; he probably has it.
Paid amplification of organic content is a smart, testable playbook. Find what works for free, then spend money to reach more of the same people. That part of the story is clean and replicable.
None of those lessons are "build in public." They are lessons about cost structure, authentic positioning, and growth experimentation. Build in public was the delivery mechanism for the last one. Mistaking the delivery mechanism for the insight is how you end up with a beautifully documented product nobody wants.
The tools did lower the floor. But the ceiling is still set by whether you picked the right problem, for the right people, at the right time. No amount of daily video content changes that.
So here is what I genuinely want to know: have you ever seen a build-in-public founder who had the wrong product-market fit and fixed it because of audience feedback from their public documentation -- or does the audience mostly just validate whatever you are already building?
