4
5 Comments

Considering "Building in Public"

I've been wondering if I should commit to "building in public" with blogging & tweets. I've been on a slow dev cycle for a few years (complicated reasons) & about to ramp up pace of releases & marketing considerably.

I need to get feedback from people on business model & the app but don't have user details captured to be able to reach out to them.

I'm concerned about this only being appropriate for very early stage products - in some ways Touchgram is "early stage" but it's been on the market since late 2019 (with a couple of pivots).

on September 3, 2023
  1. 3

    Same here, I am also thinking about doing 'building in public' for my NoCode Builder Flezr.com

  2. 2

    Hey Andy,

    The only feedback that really counts is that of paying customers.

    Building in public is only going to attract other likeminded "indiehackers". It's a way to build a support network but it's not really useful for getting paying customers (unless you are targeting indiehackers).

    Focus on getting paying customers first and foremost - their feedback is what you want.

  3. 2

    well if your project is open source just make a github repository and share the link with the world. :)

    Pedro

    1. 1

      Whilst I have released a lot of open source over the years, including many samples of small bits of tech that I use in Touchgram, the main product is definitely not open source. It's an app, iMessage extension and backend.

  4. 1

    I would advice you one thing. Focus on 80% of the customers. Don't try to make 100% customers happy else you will burn out.

    Don't deviate from the initial vision you had just because someone on social media advices not too.