Building in public means sharing your journey as you go, the progress, the decisions, the numbers, the failures, instead of working in silence and unveiling a finished product. For an indie developer with no marketing budget, it is one of the most powerful and underused growth strategies there is. It turns the lonely work of solo building into something people can follow, root for, and eventually buy. Here is how to do it well, and how to start even when no one is watching yet.

Why it works

People do not connect with polished launches. They connect with stories and with people, and a build-in-public journey gives them both. When you share the real process, the small wins, the frustrating bugs, the lesson you learned the hard way, you become a person someone is following rather than a faceless app. That relationship is the foundation of everything that follows.

The mechanics are simple and compounding. People follow your journey, some become users, some become the people who tell others, and crucially, the audience you build is not tied to one app. It follows you to the next one. You are not just marketing a product, you are building a standing audience that makes every future launch easier. That is the opposite of paid ads, which stop the instant you stop paying.

What to actually share

The most common worry is “I have nothing interesting to share.” You have more than you think. The material is your actual work:

  • Progress. “Added offline mode today, here is what it looks like.” Simple, and it shows momentum.
  • Decisions and trade-offs. Why you chose one approach over another. People love seeing the reasoning, not just the result.
  • Problems and how you solved them. The bug that took a day, the thing that broke in production. Struggles are relatable and useful, and they make the wins land harder.
  • Numbers, if you are comfortable. Downloads, users, revenue. Real numbers are magnetic because so few people share them honestly, and they build enormous credibility.
  • Lessons. What you would do differently, what surprised you. This is genuinely useful to others walking the same path, which is the whole spirit of articles like these.

You do not have to share everything, and you should not share what makes you anxious. But the ordinary reality of building, told honestly, is far more interesting to people than you expect.

Be honest, especially about the failures

The instinct is to share only the wins and hide the struggles, but that is exactly backwards. The failures are what make you trustworthy and relatable. Everyone posts their launches. Almost no one posts the app that flopped, the feature nobody used, the month with no growth. When you share those honestly, you stand out, and you give people a reason to believe your wins are real too. Polished, relentlessly positive feeds read as marketing. Honest ones read as a person, and people follow people.

Where to do it

Pick the platform where your kind of people already gather and where you will actually keep posting. For many indie developers that is a public feed on a social platform, a community like the right subreddit or Discord, or a blog like this one where each post is also a durable, searchable asset. The blog has a particular advantage: unlike a social post that scrolls away in a day, an article keeps working for years and feeds your SEO at the same time. Many builders do both, short updates on social to build relationships, longer posts on a blog to build a lasting record.

Consistency beats virality

Do not wait for the perfect post or chase a viral moment. Building in public works through steady, repeated presence, not one big hit. Showing up regularly with small, honest updates builds an audience far more reliably than occasionally posting something you agonized over. Lower the bar for what is worth sharing, post consistently, and let it accumulate. The person who posts a modest update three times a week for a year will have built something real, while the one waiting to go viral will still be waiting.

Starting from zero

The hardest part is the beginning, when you are posting into apparent silence with no audience. Everyone starts there, and the only way through is to keep going while the audience is still tiny. Engage genuinely with others doing the same thing, support their journeys, and be a real member of the community rather than a broadcaster. Early on, your reach is small but your relationships are strong, and those early followers are often your most loyal users and loudest advocates later. Treat the silent early days as planting, not failing. The audience compounds, slowly and then quickly, the same way getting your first users does.

A few mistakes to avoid

Building in public has failure modes worth naming. The first is performing instead of sharing, turning every post into a humblebrag or a growth-hack thread that reads as fake, which repels the exact trust you are trying to build. The second is comparing numbers competitively and getting demoralized when someone else’s chart looks better, when their context is nothing like yours. The third is letting the audience steer your product, building what gets likes instead of what users need, because applause and usage are not the same thing. And the fourth is quitting during the silent early stretch, right before it starts to compound. Avoid those four, keep it honest and consistent, and the rest mostly takes care of itself.

The takeaway

Building in public turns solo building from a silent grind into a story people can follow and a relationship they can invest in. Share your real progress, decisions, problems, and lessons, be honest especially about the failures, pick a platform you will stick with, and post consistently rather than waiting for perfection. Start before you have an audience, because everyone does, and let it compound. Done sincerely over time, it becomes a standing audience that makes every app you ship easier to launch than the last, which is exactly the kind of compounding advantage a solo builder needs.