A classic motion design mistake, featuring Google Calendar

Interesting. Never seen that before. There is probably a lot you have to take into account for UX

The write process for the saved time should not be affected by the animation displaying it

I hate animated UIs for this reason

I just tried this and no matter how fast I clicked OK, it set the time to xx:00. Maybe they fixed it?

If anyone needs a faster reacting UI on Android: Just bring up the developer options on your phone and set all * animation factors options to "disable animations". Now you get no more bs flying around UI elements and a faster UI.

Never had this problem. You do have a point

oh God why didn't they make the animation separate from the function... why does the animation actually control the time

The google calendar UI is just all around horrible to begin with.
I don't use it a lot but I feel like I have to decode ancient hieroglyphs every time I try to schedule something.

Silly. I have thought about this type of concept, and am confident I would've caught this mistake before writing the first line of code. But I don't like working with UI, so I understand taking shortcuts.

Similarly I hate when websites load a thing I would like to click on, then when I go to click on it, suddenly there's something else on top of it or, worse, shoving it out of the way just as I click!

I don't think that there are people that set their alarm that fast 😂

Not getting that, guess they watched your video 😅

They fixed it btw

Luckily, with Android, you can accelerate or disable animations. It's also a handy trick if your handset is painfully slow.

Power users almost always disklike animations in user actions. Try closing a dozen chrome tabs on android. If the animations werent there you could easily so it 5 times faster.

Now I know why this happens! Thanks for pointing it out.
Anyways, to me it looks like an implementation mistake that shouldn't have gone past E2E Tests.
Animations shouldn't be part of the logic of the form. I assume there was previously a bug where pressing the save button after not selecting the minutes ruined the form so they just said "ok when they immediately press save, we just take the minutes from the position of the selector" without thinking about how timmy implemented the selector as both visualizer and controller.

The whole Android date picker is the worst design one could come up with.

They fixed lol

They have added manual date input now.

Man even I can animation cancel many abilities in WuWa.

Ah yes I just use reduced motion/turn off animations

Looks like they fixed it

I never noticed this because I have my animations off lmao

I always hated that clock selection screen even without knowing about this issue, why can't I just type the fking number directly

MVC anyone?

Bad design regardless. So unnecessary.

I am pretty sure there is a similar issue in the web version of the google calendar. when I click too fast a specific action always fails - I am guesing I click during an animation, which it does not like

Oh wow that is horrendous. I don't even want to see the code behind that.

This has never happened to me ever. Android since 2014

Who
...
...
...
Cares

I've had all animations turned off on my phone for like 8 years. Had no idea the google calendar even did this. 😅

While it is a silly mistake I've never encountered it, doubt anyone clicks that fast. Still, like the picker

It's not 'tap quick', it's 'tap quickly'.

although the problem isn’t exactly in motion design itself, this is a bug and that’s all it is. in other implementation there can be other bugs.
either way this issue isn’t like inherit to motion design, just this one implementation

Everything on android os is just half finished. 😂

Its the sime one the select wheel on ios

And seems that Google don't care to fix that at all

Ou você que é muito rapido

Way to cherry pick imaginary problems in

ya!
the google calendar and alarm clock r annoyingly slow

Dark Souls-inspired app design.

Everything is proper here. I don't I know what is he talking about.

first world problems.... Get happy

Goggle is horrible in general at design with Android. This is the ugliest clock app I’ve ever seen.

How is it that much of a big deal, people are going to double check their time after setting it

I knew this from 13 when kitkat version was launched 😅

This sucks on Stock Android

It's not nostalgia. Older software was objectively better

This issue is fixed now. I used to use an old android phone that had this problem but I saw the problem has been fixed when I switched to a new Samsung mobile phone.