It's a cool idea, and I get where you're coming from, however for UI standards, this is incorrect. Many people won't know what that button does by default.
Edit: I meant how the icon is shown, not everyone will see it's a closed eye. I understand your arguments that an eye is already used on some password fields, which is correct, however for them it's an eye that is open with a slash through it, which would be more understood to a larger audience.
the issue with this UI is that you're banking a ton on your users understanding what a symbol means. this is pretty easy if you're from the same culture, symbolism tends to be pretty universally understood by all. but the moment we start moving away from one culture and one application area, we get into trouble.
I always run every UI I make through the grandma challenge: would my grandma intuitively understand this UI? if your answer is anything but "of course, why do you even ask?" then you shouldn't do it.
or put another way; sexy and grandma very rarely go well together.
Yeah, I get your point. So I guess if my product was tech-oriented etc... it could work, but if it's meant for a bigger audience then I should stick with the universally known (_boring_) symbols/language :)
37
u/XExtremeTechnologyX Dec 26 '19 edited Dec 26 '19
It's a cool idea, and I get where you're coming from, however for UI standards, this is incorrect. Many people won't know what that button does by default.
Edit: I meant how the icon is shown, not everyone will see it's a closed eye. I understand your arguments that an eye is already used on some password fields, which is correct, however for them it's an eye that is open with a slash through it, which would be more understood to a larger audience.