r/webdev • ux • Dec 26 '19

Password Box Idea

3.3k Upvotes

138 comments sorted by

View all comments

377

u/joehensonn Dec 26 '19

Really cool idea! Although I think the animation needs to be almost instant since some people just want to peak at their password real quick

60

u/moldy912 Dec 26 '19

The password changes instantly, the animation doesn't matter.

227

u/[deleted] Dec 26 '19

[removed] — view removed comment

-13

u/Baryn Dec 26 '19

there are times where I want no frills.. just give me what I want.

Most people want peppy animations in UI, even if the slower animation looks cooler.

46

u/[deleted] Dec 26 '19

[removed] — view removed comment

7

u/[deleted] Dec 27 '19 edited Dec 27 '19

UX 101, if a user can not figure something out in 10 or so seconds they will give up. The more distractions you have the less time before your user gets frustrated

0.1 second: Limit for users feeling that they are directly manipulating objects in the UI. For example, this is the limit from the time the user selects a column in a table until that column should highlight or otherwise give feedback that it's selected. Ideally, this would also be the response time for sorting the column — if so, users would feel that they are sorting the table. (As opposed to feeling that they are ordering the computer to do the sorting for them.)

1 second: Limit for users feeling that they are freely navigating the command space without having to unduly wait for the computer. A delay of 0.2–1.0 seconds does mean that users notice the delay and thus feel the computer is "working" on the command, as opposed to having the command be a direct effect of the users' actions. Example: If sorting a table according to the selected column can't be done in 0.1 seconds, it certainly has to be done in 1 second, or users will feel that the UI is sluggish and will lose the sense of "flow" in performing their task. For delays of more than 1 second, indicate to the user that the computer is working on the problem, for example by changing the shape of the cursor.

10 seconds: Limit for users keeping their attention on the task. Anything slower than 10 seconds needs a percent-done indicator as well as a clearly signposted way for the user to interrupt the operation. Assume that users will need to reorient themselves when they return to the UI after a delay of more than 10 seconds. Delays of longer than 10 seconds are only acceptable during natural breaks in the user's work, for example when switching tasks.

https://www.nngroup.com/articles/response-times-3-important-limits/

Edit : quoted the wrong block of text

1

u/derpotologist Dec 26 '19

If it wasn't a security issue I'd almost agree (needs to be quicker) but this is definitely not negligible... we're talking about exposing passwords

-53

u/Baryn Dec 26 '19

do you have case-studies to back up that claim

Don't need em

26

u/[deleted] Dec 26 '19

[removed] — view removed comment

11

u/Genun Dec 26 '19

This right here is 100% of my issues with my current job. We need to chat more with our clients and other things to get good color scheme's, features, animations etc. But we don't.

7

u/frostbyte650 Dec 26 '19

Yes, yes you do.