Ask HN: Where can I get constructive criticism for my app/website?
6 comments
How about a monthly HN "Criticize Me" post where people can show their current projects?
Every top-level comment is a project and then the community can give feedback. That way you don't have the pressure of "Show HN" but can nonetheless benefit from the HN community.
Rather than getting constructive feedback from the "internet", like you are asking, it would be much better to get constructive feedback from your actual potential users.
So rather than posting to Show HN, Reddit, or random internet friends, make a list of 10 people who you could consider potential users and email them asking for feedback. Then for any/all that respond, given them a small reward from iTunes, Amazon, etc.
So rather than posting to Show HN, Reddit, or random internet friends, make a list of 10 people who you could consider potential users and email them asking for feedback. Then for any/all that respond, given them a small reward from iTunes, Amazon, etc.
Looking at the "Show HN" associated with your HN user name, one thing that pops out is that the post doesn't create much context for providing feedback. That is, there is nothing explaining what you are trying to achieve. Since I am clearly not in the target demographic, there's nothing for me really to evaluate the site against...I don't visit other street-fashion-rating websites or know why the woman on the beach is worth -422 for whatever it is that I'm picking.
It does something, but I don't know what let alone how well unless you tell me what it is supposed to do and why it is supposed to do it. I mean, I know there's a design vector under which I am simply not supposed to "get it," but I have no basis for evaluating it against a user story of someone who is supposed to "get it."
As others have said, the best feedback would be from people who are supposed to "get it". Absent that though, feedback requires an explanation...a blog or a comment or a link at the bottom of the page.
Good luck.
It does something, but I don't know what let alone how well unless you tell me what it is supposed to do and why it is supposed to do it. I mean, I know there's a design vector under which I am simply not supposed to "get it," but I have no basis for evaluating it against a user story of someone who is supposed to "get it."
As others have said, the best feedback would be from people who are supposed to "get it". Absent that though, feedback requires an explanation...a blog or a comment or a link at the bottom of the page.
Good luck.
Thanks for digging deep. However, this question was not in relation to my previous Show HN post (damn internet :)).
Since you did bring it up, I like to think that I'm aware of the reason for it not getting any attention. Long version: I got fixated on engineering, while forgetting about the core UX.
Case in point:
1. the score you mention begins with a node service scraping a random page from lookbook, which contains a list of photos and their 'hypes' (likes);
2. then all the scores get normalized, where 1000 would be given to the highest hype score, all other being (hype*1000)/max_hype;
3. finally the sign of the score is based on whether you correctly guessed that the looks hype is more ('Fashn') or less ('No Fashn') than the average, non-normalized hype for a given page, and the nominal value of it is the difference between the normalized average and a given photo's score.
I guess I didn't bother explaining this to the user, since the initial idea was to compare your taste to that of the lookbook community (read 'objectively fashionable'). However in approach above, the score for a photo is determined relative to the other photos on the page, but not other pages. Since relativity is unavoidable with the set logic, the user must be presented with a design that allows relative comparison. This, in turn, brakes the current minimalist design, which was one of the main features.
This Buridan's ass state is where I stopped development, and decided to show it as is. HN wasn't the first place, and all the feedback resolved around a broken (not well explained?) core mechanic. Meanwhile, the restless mind queued up a number of ingenious ideas, and, not being socially pressed for time nor resources, I decided to move on.
Since you did bring it up, I like to think that I'm aware of the reason for it not getting any attention. Long version: I got fixated on engineering, while forgetting about the core UX.
Case in point:
1. the score you mention begins with a node service scraping a random page from lookbook, which contains a list of photos and their 'hypes' (likes);
2. then all the scores get normalized, where 1000 would be given to the highest hype score, all other being (hype*1000)/max_hype;
3. finally the sign of the score is based on whether you correctly guessed that the looks hype is more ('Fashn') or less ('No Fashn') than the average, non-normalized hype for a given page, and the nominal value of it is the difference between the normalized average and a given photo's score.
I guess I didn't bother explaining this to the user, since the initial idea was to compare your taste to that of the lookbook community (read 'objectively fashionable'). However in approach above, the score for a photo is determined relative to the other photos on the page, but not other pages. Since relativity is unavoidable with the set logic, the user must be presented with a design that allows relative comparison. This, in turn, brakes the current minimalist design, which was one of the main features.
This Buridan's ass state is where I stopped development, and decided to show it as is. HN wasn't the first place, and all the feedback resolved around a broken (not well explained?) core mechanic. Meanwhile, the restless mind queued up a number of ingenious ideas, and, not being socially pressed for time nor resources, I decided to move on.
Everything on the damn internet is forever...fortunately it helps with discoverability.
Anyway, where I was going is that everything that is in your comment here provides context and most importantly is interesting to the people who are likely to read it:
So what I'm saying is that the hard part is figuring out what someone cares about. I mean even a website about designing websites around set logic and relativism has at least one person who cares...so does british-motorcycles-and-amphibians because I went to Junior High School with her.
The challenge is that it is a lot easier to find people, like me, to comment on a british-motorcycles-and-amphibians website than it is to build one that my friend will care about.
Anyway, where I was going is that everything that is in your comment here provides context and most importantly is interesting to the people who are likely to read it:
1. It's technical
2. It's on HN
So what I'm saying is that the hard part is figuring out what someone cares about. I mean even a website about designing websites around set logic and relativism has at least one person who cares...so does british-motorcycles-and-amphibians because I went to Junior High School with her.
The challenge is that it is a lot easier to find people, like me, to comment on a british-motorcycles-and-amphibians website than it is to build one that my friend will care about.
Few starting suggestions below. Note that you should have a working example, but it doesn't need to be 'final' or 'perfect'. Don't be afraid to release to a select group of people early for feedback. That feedback will help further the development of the product or site.
https://www.reddit.com/r/web_design
https://www.reddit.com/r/webdev
https://www.reddit.com/r/startups
https://www.reddit.com/r/entrepreneur
https://www.reddit.com/r/web_design
https://www.reddit.com/r/webdev
https://www.reddit.com/r/startups
https://www.reddit.com/r/entrepreneur
Also, if you're using something specific (Node, Bootstrap, Rails, Meteor etc.) you could probably get some help from those communities' subreddits.
You're right, getting unbiased, honest feedback is very difficult, but critical.
If you're looking for feedback from a marketing perspective, as in, how are my customers likely to respond to this, how likely are they to buy something, then we run a free weekly marketing clinic over at http://paulmontreal.com
You can apply here http://paulmontreal.com/apply
If you're looking for feedback from a marketing perspective, as in, how are my customers likely to respond to this, how likely are they to buy something, then we run a free weekly marketing clinic over at http://paulmontreal.com
You can apply here http://paulmontreal.com/apply
Shoot me an email, would love to help :)
Is there a solution on the web where you can provide your not-so production level solution, preferably anonymously, and get constructive feedback?