Hello!
The comments on this profile are unclaimed and thus are unverified.
Do they belong to you? Claim these comments.
Des
Is this you? Claim Profile »
4 months ago
in Progressive Discloure on uxRefresh
Whilst I like the principle of progressive disclosure, I find that it's often used as a crutch to avoid making a design decision.
Adding a Show/Hide behind an element is effectively saying "I'm not sure if this should always be here or not, so I'll let the user decide".
Certainly the examples you've highlighted are using it effectively, but I've seen far too many counter examples.
Also, if you're using progressive disclosure you should really check your stats and see if your visitors are as undecided as you are. If they all choose to "show" then maybe it should be shown all the time.
http://www.contrast.ie/blog/the-problem-with-st...
Adding a Show/Hide behind an element is effectively saying "I'm not sure if this should always be here or not, so I'll let the user decide".
Certainly the examples you've highlighted are using it effectively, but I've seen far too many counter examples.
Also, if you're using progressive disclosure you should really check your stats and see if your visitors are as undecided as you are. If they all choose to "show" then maybe it should be shown all the time.
http://www.contrast.ie/blog/the-problem-with-st...
1 reply
Grant
Des ~ You bring up an excellent point which is why looking at any quantitative and qualitative data to back up your decisions is a must. Based off of the data, I firmly believe that any idea is an idea worth testing. What's wrong with letting the user decide what they want to see? If done effectively, as in the examples I've provided, it adds nicely to the user's overall experience.
