Starting out my build in public journey -- how to effectively schedule, format, and share continously?

Overview

Hey all ✌️! I have taken the plunge and am now doing a #buildinpublic journey on Twitter, where I share the technical decisions and product decisions I make, while building my new Chat Assistant app, on iPhone! See my initial tweet here: https://twitter.com/bradleybernard/status/1668327054847401984

Plan of action

I plan on tweeting daily with various challenges that I run into, sharing mostly code and product screenshots, as well as transparency into decision making. I've been building products for years at various companies, but this is the first time I'm allowed to do my own thing (as my own boss) and share it!

Questions

This is my first time, so I would love to stir conversation here and get answers from others who are more experienced on content, marketing, Twitter and build in public!

Should content be mostly threaded? Should content be in one single Twitter thread (ie: long long thread with 100s of replies from day 1? Does that affect Twitter analytics good or bad?)
Is it worth spreading out content over days (scheduling)? I find myself doing quite a few things in one day, but am scared the volume of content might be a bit too much: hard to follow and feeling spammy
How to enable more conversations: how to tailor your content to get more engaged viewers/commenters. Is there any angle to push on, to get more engaging tweets with that in mind? Shouting into the void on a consistent schedule is good, but I don't mind adjusting my methods to get aim towards building an audience in a more efficient way. (hype?!)

Connecting with others

I want to connect with others who are building in public to understand your story, hear your success and failures, and see what your building! I've been browsing the #buildinpublic hashtag on Twitter and man there are so many cool IndieHackers out there :) love to see it and happy to be apart of it!

Let's connect on Twitter!
https://twitter.com/BradleyBernard

Bradley Bernard

posted to

Building in Public

on June 13, 2023

Say something nice to BradleyBernard…

Post Comment

4
i am building in public as well, here is my first tweet
I also post on indiehackers "building in public" group.
1. I don't know i am experimenting as well however i have taken the approach of multiple threads as i think single thread becomes confusing.
2. You just share your main learnings if there is any technical breakthrough or decision that needs more nuanced writing it can be a sepearate blog post. You will know with the engagement if its worth writing more about it. If people are not engaged in the headline itself than elaborating will do little in terms of increasing engagement.
3. Consistency is the only thing that i can think of. You can obviously make it more appealing by posing it as question or phrasing it as "how i solved x" but it appears too much of work on top of the work that i am already doing so i am not doing it. However you can put some thought in varying your content and see how it goes. It would be good learning.
pdyc

·
3 years ago
·
Reply
3

Hey man! I’m just starting my build in public journey as well. Good luck, looking forward to following your journey and reading about the lessons you learn! I’ll follow you on twitter.

crispintea

·
3 years ago
·
Reply
2

yeap

aakaweb

·
3 years ago
·
Reply