3 ms·

Zoom solves this problem by.... adding a confirm popup button. As far as I can tell they're the only meeting app that does that, I find it almost annoying most

by vxNsr 6y ago

Zoom solves this problem by.... adding a confirm popup button. As far as I can tell they're the only meeting app that does that, I find it almost annoying most of the time but very useful when I hit it by accident.

danielbarla 6y ago
I've often wondered why this kind of confirmation couldn't be conditional on the confidence that the click / touch was intentional? As an example, my favourite pet peeve was using Visual Studio with old-school, upfront locking source control (like TFS), and then accidentally drag and dropping a file or folder due to lag in remote desktop, or a failing mouse which sent two click events in 1 ms or something. VS duly pre-emptively locks the 10k files in the folder you just dragged, and begins a 5 minute operation you'll have to somehow undo later, even though it should be fairly obvious from the click events that it was non-intentional. Going back to the meeting example, surely solid, accurate taps in the center of the hang-up icon could be taken as intentional, but a kind of glancing, less accurate one needing confirmation?
- EarthLaunch 6y ago
  That type of approach is the way forward in UI. Maybe if we call it something silly like MLUX it will catch on sooner. Another instance of the same principle is that if an unexpected button/element appears and I click it in <30ms or whatever the fastest possible read+react time is, the click isn’t intentional and should be ignored or confirmed. This should scale over time based on user familiarity and speed. This culminates at: > as the technology became more sophisticated the controls were made touch-sensitive - you merely had to brush the panels with your fingers; now all you had to do was wave your hand in the general direction of the components and hope. [HHGTG]
  - tpxl 6y ago
    Changing the way buttons behave that is completely opaque to the end user is a good way backwards. > if an unexpected button/element appears and I click it in <30ms Easily solvable by locking the buttons for a few seconds (or less).
    - EarthLaunch 6y ago
      Disadvantage there is advanced users know where the button will land and have to wait.
chrismorgan 6y ago
That popup annoys me, because I never hit the button to leave a call by accident. It used to annoy me even more because there was a time last year when it was impossible to leave a call by keyboard only on Windows, because all methods of normally closing the window would trigger this popup, but you couldn’t submit that popup by keyboard. Now at least I can Alt+Q Enter or something like that. (I confess that the first time I encountered this I opened Task Manager and found and killed a Zoom.exe process all by keyboard, just on principle. That was when I discovered that Zoom has two processes so that the main one can restart the call if the call process crashes!) But you know one potential factor for my never hitting it by accident? They use text labels (“Leave Call” / “End Call”) rather than an icon. Much easier to get right.
- breeny592 6y ago
  It feels like one of those things where the context of the meeting/call should be taken in: was the scheduled time of this call for an hour and you've left 10 minutes in, maybe a confirmation dialog is more useful than when you've decided to leave within a few minutes of the finish time. Doesn't cover all the edge cases etc., but just observing that "the right UX" is super contextual and not a one size fits all thing.
  - kybernetikos 6y ago
    Whether taking that context into account is a good idea is very debateable. The more contextually 'intelligent' a system is, the harder it is for the user to model it, and ease of user modelling is often more important than reducing the number of interactions need to complete a task. In this particular case, it wouldn't be possible to know if your keyboard sequence that quits a call would feature an unnecessary enter at the end or not.
kenneth 6y ago
Doesn't fix the problem of accidentally turning your video on when you meant to shut the call off. I've taken plenty of calls in places where it'd be more professional to keep the video off (especially when outside home)

by vxNsr 6y ago

danielbarla 6y ago

I've often wondered why this kind of confirmation couldn't be conditional on the confidence that the click / touch was intentional? As an example, my favourite pet peeve was using Visual Studio with old-school, upfront locking source control (like TFS), and then accidentally drag and dropping a file or folder due to lag in remote desktop, or a failing mouse which sent two click events in 1 ms or something. VS duly pre-emptively locks the 10k files in the folder you just dragged, and begins a 5 minute operation you'll have to somehow undo later, even though it should be fairly obvious from the click events that it was non-intentional. Going back to the meeting example, surely solid, accurate taps in the center of the hang-up icon could be taken as intentional, but a kind of glancing, less accurate one needing confirmation?

EarthLaunch 6y ago
That type of approach is the way forward in UI. Maybe if we call it something silly like MLUX it will catch on sooner. Another instance of the same principle is that if an unexpected button/element appears and I click it in <30ms or whatever the fastest possible read+react time is, the click isn’t intentional and should be ignored or confirmed. This should scale over time based on user familiarity and speed. This culminates at: > as the technology became more sophisticated the controls were made touch-sensitive - you merely had to brush the panels with your fingers; now all you had to do was wave your hand in the general direction of the components and hope. [HHGTG]
- tpxl 6y ago
  Changing the way buttons behave that is completely opaque to the end user is a good way backwards. > if an unexpected button/element appears and I click it in <30ms Easily solvable by locking the buttons for a few seconds (or less).
  - EarthLaunch 6y ago
    Disadvantage there is advanced users know where the button will land and have to wait.

chrismorgan 6y ago

That popup annoys me, because I never hit the button to leave a call by accident. It used to annoy me even more because there was a time last year when it was impossible to leave a call by keyboard only on Windows, because all methods of normally closing the window would trigger this popup, but you couldn’t submit that popup by keyboard. Now at least I can Alt+Q Enter or something like that. (I confess that the first time I encountered this I opened Task Manager and found and killed a Zoom.exe process all by keyboard, just on principle. That was when I discovered that Zoom has two processes so that the main one can restart the call if the call process crashes!) But you know one potential factor for my never hitting it by accident? They use text labels (“Leave Call” / “End Call”) rather than an icon. Much easier to get right.

breeny592 6y ago
It feels like one of those things where the context of the meeting/call should be taken in: was the scheduled time of this call for an hour and you've left 10 minutes in, maybe a confirmation dialog is more useful than when you've decided to leave within a few minutes of the finish time. Doesn't cover all the edge cases etc., but just observing that "the right UX" is super contextual and not a one size fits all thing.
- kybernetikos 6y ago
  Whether taking that context into account is a good idea is very debateable. The more contextually 'intelligent' a system is, the harder it is for the user to model it, and ease of user modelling is often more important than reducing the number of interactions need to complete a task. In this particular case, it wouldn't be possible to know if your keyboard sequence that quits a call would feature an unnecessary enter at the end or not.

kenneth 6y ago

Doesn't fix the problem of accidentally turning your video on when you meant to shut the call off. I've taken plenty of calls in places where it'd be more professional to keep the video off (especially when outside home)