You've posted this, what, 3 times now?
You may be asking the wrong crowd. Try e-mailing some of the app review sites etc. to see what they use currently and how it can be improved.
You may be asking the wrong crowd. Try e-mailing some of the app review sites etc. to see what they use currently and how it can be improved.
I do doubt that he is asking the wrong crowd -- at least, at first. "Would anyone be interested in me building this?" vs "Hey, I built this. Anyone have a use for it?" are two very different questions. Since there are already people with working solutions in place, and they're easy enough to find, your first initiative should be to either a) build it for yourself or b) find out what problems they already have and how to eloquently solve them.
In short, he needs to find people that already have a need for it. As to whether or not they read HN, who knows. A direct email is a much better method of contact, though.
I'm sorry if I seem spammy, I'm just desperate to get this post right for proper feedback. Most features I just build, keep if it's used and abandon if it's not.
With an API I know people would be depending on me for their site. I'm trying to make sure it's the right direction so I don't end up having to abandon the project along with 1 or 2 users who adopt it.
Sounds like no feedback IS the feedback. If it were a good idea the wording wouldn't matter so much.
I believe it's less about how you get the post right and more about who you're asking. As I mentioned above, you need to talk to the people that are already using something similar to what you're... going to build?
Since you're not getting much feedback here, let me be the bird of encouragement that is sitting on your shoulder right now. Find people who you think would have a need for this, and talk to them. Those people apparently are not on HN. Ask the app review sites how they keep up and where they get their feeds from. It's a start!