A building journey only builds trust if it shows momentum
A public building journey can help trust — but only if it shows momentum.
For most visitors, trust comes from two questions: does this solve my problem, and will it still exist in 6 months?
A building journey answers the second question well, but only if it shows real momentum — not just activity.
Polished landing pages can signal “we’ve arrived,” but a building journey can signal “we’re accountable.” That is especially valuable for early adopters who are often betting on the maker as much as the product.
Might be worth thinking about what you’re highlighting: are you showing that you’re building, or what the building is revealing about the problem you’re solving?
The second one is where it gets much more compelling.
Trending on Indie Hackers
Yep. The best build-in-public updates are less “shipped feature X” and more “I learned users behave like Y, so I changed Z.” For consumer health apps especially, showing what real usage taught you builds more trust than polished screenshots because people can see the product getting closer to their actual habits.
this makes a lot of sense. most build in public stuff is just a list of features added or minor bug fixes which gets boring fast. showing teh actual insights you get from users or how your understanding of teh problem changes is way more interesting. it shows you are actually solving something instead of just typing code to feel productive.