| I used to "build in public" with my first app 2 years ago, KTool[0] But back then most indie hackers only share numbers in their monthly reports, me included[1]. And it's not just MRR screenshots with no content. Many shared their lessons, experiments, personal struggles... I can't stress enough how helpful this was. To me and to many founders I've talked with. It helps us with the loneliness and we learned from each other's mistakes... I made a lot of online friends during this period. We were (still are?) inexperienced founders who trying to bootstrap a profitable business and share the experience. I stopped BIP now, mostly because it takes more time and effort than I could afford. And posting MRR screenshots only is bragging in public, not building in public. BUT I still believe in the value of BIP, especially when for a newcomer. You may find people who genuinely support your journey, and if you're lucky, you might build a decent following on Twitter. Your customers root for you because of your personal and authentic "brand". Seasoned founders might reach out and point out what you're doing wrong, avoiding making the same mistakes (I did get a lot of valuable advice from successful founders—to me, this has been the biggest value I get out of BIP) BUT if you treat it as a marketing channel, it probably won't work. Like others mentioned, it's saturated and you're only attracting the wrong kind of audience. If I was to start again, I would treat BIP as the sandbox to launch my product: ask for feedback, search for a few early adopters who might benefit from my product but not necessarily my ICP. [0]: https://ktool.io [1]: https://www.indiehackers.com/product/ktool |