New answers tagged profile
The principle you want to leverage, here, is called social proof. I noticed that the experts at user-experience consultancy NN/g discuss this in their article, Social proof in the user experience. This article gives a quick overview and, in the last few paragraphs, provides links to other authors and research for in-depth reading. You might like to read ...
For your specific scenario, there are many benefits and really can't see why NOT to use them. Basically, you want to have user's reviews, so while users are not the focal point, they're an important aspect of your site, if not THE MOST IMPORTANT. and this is NOT an exageration. I assume your app is oriented to sell. Now, with apps like yours, I can find 100 ...
First we should know what is the goal. You might want to encourage the user to fill in his profile but it's not the only posible case, either ways don't show empty fields to visitors. If it's beneficial only for the user but not you to fill it in, that case hide the empty fields in profile view and only show on edit page.
Well, if the fields are optional, then you're offering the user the option to NOT to fill some info. As a result, you have a zero data field. In this case, you face the issue of how to handle this. While Adit Gupta's links are really nice and informative (and I recommend you to check them out for ideas, as well as this one), your case is very different. ...
I think one of the best ways to handle it is to provide a delightful message to the user along with encouraging him to take the next step. This article on Tympanus can give some more clarity on how to handle empty states. Also, check out this interesting page showcasing how apps and websites handle empty states - Empty States
Top 50 recent answers are included