4
2 Comments

What to do about non-definitive feedback

I've been building the No Code List very organically on purpose. In the past, I've always jumped right into building, but for this, I want to test and vet everything before spending any time creating it.

I've been showing mockups and posting potential plans on here. A good reaction means it's time to build and a bad reaction means I can save myself the hassle. But what happens when I put out a new feature, and the feedback isn't definitive either way? Do I take lack of feedback to mean lack of interest?

For whatever reason, I can't just kill this recent "expert comments" idea (it's got a lot of potential legs for the future). Instead, I decided to make a small tweak and try to get better feedback. Now each comment answers the two specific questions: "What is great about this software?" and "Who is it great for?" I also updated the /about page to reflect my goals with the list and who I think it's useful for.

What do you think? Is this more interesting by being more focused? Is the comments feature itself worth it? Is it just not interesting??

https://nocodelist.co/comments/?id=recBADDNLEvUjGXos

on October 5, 2019
  1. 2

    First time seeing this site and read the about page for context. That said, I think you want some kind of review feature.

    I think it needs to be:

    What it’s great for?

    What it’s not great for?

    Straddling the question with (or not great) makes it needlessly confusing.

    As a reader it’d be good if the comments had some form of rating (stars or whatever). For this, I’d probably just copy Apple’s AppStore review UI to start with.
    The challenge here is: what aspect does the rating actually rate?

    1. 1

      Thank you! That's a great point about being needlessly confusing.

      Instead of stars, I was using a "thumbs up," "thumbs down," or "nothing" model... I'm not a big fan of star ratings personally (everything below 4 might as well be 0). I realize now that it's not obvious that the thumbs up on each comment is a rating and not part of the comment.

      Re: the challenge here: exactly... and I think the key for me is to focus the review by asking more specific questions. If you'd ask me, the rating should be to how well the software does the job it claims to do. But I don't know if that's what everyone wants or expects.

      Thanks again.