3 ms·
> If a password is entered, a simple ‘nod’ animation can be introduced upon completion. Whereas a horizontal shake can be used when denying a password. The NeX
by TYPE_FASTER 11y ago
> If a password is entered, a simple ‘nod’ animation can be
introduced upon completion. Whereas a horizontal shake can be used when denying a password.
The NeXT used to do that on the login screen. It got huge applause at the premiere I saw in 1988.
> Any way you can avoid showing a loading status will make your app appear much faster.
The animation is now the loading status. The animation isn't making the user think the app is faster, it's just taking the place of a different animation that would show the asset is loading.
I do appreciate showing that loading status so I don't have to try to figure out what my phone is doing by looking for the spinner at the status line at the top of the screen, but don't change the size of the button and distract me from the content.
- wyattpeak 11y ago> The animation isn't making the user think the app is faster... I disagree. The right hand animation, sure, but if I saw the middle animation, I don't think I'd register the latency at all. In fact I think I might misinterpret and get irritated that my time was being wasted with an unnecessary animation. Not necessarily better, but I would have been distracted from the load time.
- underwater 11y agoOS X has the same shake animation on failed login. It's horrendous because there is a non deterministic delay before it shows. If I glance away from the screen and miss the animation I have no idea that the login has failed. It also doesn't differentiate between different failure modes. I've had my company's active directory stop working, but I don't know this because the feedback is exactly the same as if I'd mistyped my complex password. As a rule: a failed login is the wrong time to try and delight me with a beautiful UI.