Why is it not common UX practice to start ignoring user input prior to rearranging the UI, and only responding to user input once the layout has settled and perhaps after a short delay?

It’s very frustrating to reach for an option in a list, only to have the list repopulate just as I tap, inevitably on an undesired option

I’m not even talking solely about web design: even the Google Cast destination picker does this and it’s native Android code

Has Apple solved this over in iOS land?

  • Tiuku
    4·
    2 years ago

    I agree, just a day ago I accidentally clicked Send this way, and sent a silly empty message on one site.

    I wonder if this is mainly an issue/feature of web engines? Maybe the idea is to make the initial load faster?

    • Helix 🧬@feddit.de
      3·
      2 years ago

      feature of web engines? Maybe the idea is to make the initial load faster?

      Lazy loading, you mean?

    • jokeyrhyme@lemmy.mlOP
      3·
      2 years ago

      Yeah, I think there are some cases where it’s a performance thing, sure: e.g. a list that displays a few hard-coded common options, and is repopulated with personalised options once they’ve been fetched from a back-end

  • Helix 🧬@feddit.de
    4·
    2 years ago

    Microsoft Teams is “great” in that regard. Try scrolling up and hitting the reply button on any message, it’s a sysiphean exercise in anger management. Gets me nearly every day at work when I need something from the day before.

  • sergih123@eslemmy.es
    3·
    1 year ago

    This is so true, I specially hate it when it’s due to he cookies pop-up, I’m about to click omethign and then the pop-up shifts the whole website up/down, and end up clicking in some random thing.

    When it happens twice in a row I feel stupid too.

  • seafoam_green@sh.itjust.works
    3·
    1 year ago

    Tbh I think a lot of developers either don’t know that they need to fix this or don’t know how to fix this. They get a mock-up from the designer and implement what they see, and their implementation work is reviewed be other engineers and product people, but less often (IME) by UX. Sometimes there’s no one to push for fixing these kind of things, especially when the developers don’t use the software they make in their own day-to-day lives.