Ask HN: Should your UX contain 'greyed-out' features?
In any given startup you move fast, really fast and sometimes you want to develop good user habits early. For features that are coming soon, very soon is it a good idea to show a link to them that is 'grey-ed' out?
In one sense this lends it's ear back to the under construction signs of the web in the 80s, but a more modern approach would allow you to get early feedback on what users like and don't like about features you are working on now.
So I put it out to HN, how do you feel about using disabled buttons, or UX to get early feed back on features that are actually under construction?
Are there any clear examples of this being a Win or a Fail on the teams trying it?
Does it depend on your customer? What types of customers might this be a win for and which one's might find it frustrating?
In one sense this lends it's ear back to the under construction signs of the web in the 80s, but a more modern approach would allow you to get early feedback on what users like and don't like about features you are working on now.
So I put it out to HN, how do you feel about using disabled buttons, or UX to get early feed back on features that are actually under construction?
Are there any clear examples of this being a Win or a Fail on the teams trying it?
Does it depend on your customer? What types of customers might this be a win for and which one's might find it frustrating?