Subscribe
Sign in
Building in public : Is it worth it?
The greatest advantage of building in public is the opportunity to grow an audience.
Are there any other benefits that I might have overlooked?
11
Replies
Best
@kate_kovbii Thanks so much, Kate! Just curious, is the product you're launching going to be developed in a public ??
@charlie_lee1 I like your question a lot 😁❤️ Sadly or happily, I joined the product team after all core features were developed (but we did need to reconsider them a bit), so I didn't have a chance to build in public. But I will definitely try out this strategy with all the future products 😌
And what about you? Are you planning to build something in public?
@kate_kovbii I plan to build in public. I'll let you know when we're ready.
Also, I've subscribed to your product which is launching soon. I'll be sure to offer my support!!
I've been thinking about website where you could connect your public/private git repository and would be able to comment any commits/pull requests you want. So users can't see your private repo but can see the comments about what's changed in your project at the moment.
Is there such one? Should I start to develop something like this if there's none?
@charlie_lee1 It could be something like Polywork for projects, not people. https://www.polywork.com/rrhoover
Like a wall of changes/updates, directly connected to github/gitlab repo, with audience comments and jobs/contributions posts.
That's how I see it, need to search for something similar, or just try to build this :)
With building a public you will easily gain early adopters for your product, feedback and great networking as weel :) wishing you good luck on your journey!
@sandradjajic Awesome! Thank you so much for your answer!! I really appreciate it.
Are you building Klu in public?
Sign