Connect your Github repository. Ship new code with a pull request or commit. Get a tweet generated automatically to announce the new feature.
Generate launch tweets automatically when you ship new code
Connect your Github repository. Ship new code with a pull request or commit. Get a tweet generated automatically to announce the new feature.
When I first learned about Buildshare - 🤯 was my reaction! But also the more I think about it - the more it makes sense to me. It smells like future. Build-in-public, on automation. Let's go, @mattiapomelli! Congrats on the launch!
Whatsup PH! I’m Mattia, and I’ve been working on Buildshare for the past few weeks. I’ve been building in public and sharing my work on socials for about a year. Since I started, I was able to get much more reach for my projects and stay more motivated. I realized that on socials, consistency is key. But, it’s also the hardest part. The way you structure your posts and talk about your product can either boost you or kill you. That’s why I decided to build a tool to help developers be more consis
Very neat linkage. Not really my area of expertise, but I'm also sort of curious if there could be some type of 'translation' to convert github/developer talk to content for a twitter audience? E.g. "updated API" to "updated connection between BuildStreak.com and Buildshare.io" or something
I was just thinking about building something like this - glad you built it instead! Can't wait to try it out
This is SUCH a great idea!! We've been looking for a way to help take the load off the product/marketing team when it comes to announcing new feature releases, improvements, bug fixes etc, and this looks like it'll help solve our pain. If we could also get it to write a weekly changelog summary of some of the bigger ticket items, that would be the icing on the cake!
A measure of community engagement at launch. Higher means more people noticed and interacted with the product. It's a traction signal, not a quality rating.
Discussion threads divided by interest score. Above 0.30 is strong. Below 0.15 suggests the product got clicks but not conversation.
Categories come from the product's launch tags. Most products appear in 2-3 categories. The primary category is listed first.
The scores reflect launch-period engagement. Historical data is preserved and doesn't change retroactively. The build date at the bottom shows when the index was last refreshed.