4 ms·

I think the author's point about reset buttons and cancel buttons is valid, but not about the Google Meet interface. Reset and cancel buttons present an either/

by ysavir 6y ago

I think the author's point about reset buttons and cancel buttons is valid, but not about the Google Meet interface. Reset and cancel buttons present an either/or with the submit button. You either submit or cancel, and only rarely reset a form, so they present interface functionality that is rarely used, but significantly impactful of the experience. But a "leave meeting" button is used at least once per meeting by each participant, which may be more frequent than the mute or hide video buttons. It's appropriate to put it front and center where participants can easily find it. I feel like what the author really wants here is a confirmation before leaving in case of accidental clicks.

sesqu 6y ago
That's not so much a problem for the people who want to leave a meeting, but it is very much a problem for people who frequently toggle their mic on and off.
alejoar 6y ago
The "leave meeting" button is not used "at least" once by each participant. It is used exactly once. Same as the submit button. The reset button can be used multiple times, same as the "enable/disable mic/cam", although arguably the latter WILL be used multiple times. I believe it is more a matter of "multiple vs single" use that needs to be considered, or more like "on going vs finishing" actions when separating/grouping buttons.
- ysavir 6y ago
  The usage of the other buttons varies wildly by participant. I know some that mute and hide the camera at all times unless otherwise necessary, while I also know others that generally never mute or hide. > I believe it is more a matter of "multiple vs single" use that needs to be considered, or more like "on going vs finishing" actions when separating/grouping buttons We could probably separate them along those lines, yes. But I don't think this relates much to the original article. It compared the "leave meeting" button, which we agree is an "exactly once per call" button, to the cancel/reset buttons, which are in the "hardly ever maybe never" category, and that's not a fair comparison. My point is that while we can find ways to distinguish the "leave meeting" button from mute and hide, it's not appropriate to give it the same treatment as a cancel/reset button should get.
perryizgr8 6y ago
I never use the hang up button in Google meet because it just irritates me to figure out where to click. So I just close the tab.
- Aachen 6y ago
  That's actually a good point, I could add a user style that hides the button completely because I also always close the tab. Would make life a lot easier!
- ysavir 6y ago
  Exactly. Finding the "leave meeting" button is not one that should be hard to find as it's expected to be used at some point by each participant on the call. The UI should be calling attention to it (albeit in a click-safe way).

by ysavir 6y ago

sesqu 6y ago

That's not so much a problem for the people who want to leave a meeting, but it is very much a problem for people who frequently toggle their mic on and off.

alejoar 6y ago

The "leave meeting" button is not used "at least" once by each participant. It is used exactly once. Same as the submit button. The reset button can be used multiple times, same as the "enable/disable mic/cam", although arguably the latter WILL be used multiple times. I believe it is more a matter of "multiple vs single" use that needs to be considered, or more like "on going vs finishing" actions when separating/grouping buttons.

ysavir 6y ago
The usage of the other buttons varies wildly by participant. I know some that mute and hide the camera at all times unless otherwise necessary, while I also know others that generally never mute or hide. > I believe it is more a matter of "multiple vs single" use that needs to be considered, or more like "on going vs finishing" actions when separating/grouping buttons We could probably separate them along those lines, yes. But I don't think this relates much to the original article. It compared the "leave meeting" button, which we agree is an "exactly once per call" button, to the cancel/reset buttons, which are in the "hardly ever maybe never" category, and that's not a fair comparison. My point is that while we can find ways to distinguish the "leave meeting" button from mute and hide, it's not appropriate to give it the same treatment as a cancel/reset button should get.

perryizgr8 6y ago

I never use the hang up button in Google meet because it just irritates me to figure out where to click. So I just close the tab.

Aachen 6y ago
That's actually a good point, I could add a user style that hides the button completely because I also always close the tab. Would make life a lot easier!
ysavir 6y ago
Exactly. Finding the "leave meeting" button is not one that should be hard to find as it's expected to be used at some point by each participant on the call. The UI should be calling attention to it (albeit in a click-safe way).