5 ms·

One job doesn't really fit the button thing because a button has to do many things, only one of which is being clickable. Having feedback when clicked, feedbac

One job doesn't really fit the button thing because a button has to do many things, only one of which is being clickable. Having feedback when clicked, feedback when hovered. A loading state, a disabled state, a mix of everything. That's also something I found very frustrating. Like if you take the example of a button that is tied to a service on the back end, clicking this button without any visual feedback doesn't tell you if that button was clicked or not. And if it doesn't have a loading state, you wouldn't know that. something is working behind the scene when you click this button so you would click at multiple times not knowing that it's still working behind the scenes.

m463 2mo ago
Just to go out on a wild tangent... buttons on simple hardware devices usually have many many functions. this button has a function. but if you are powering up and hold it, it does a different function. press and hold this button and while holding it press another button for something else. The most extreme example of this kind of thing I can recall is the anduril open-source flashlight firmware: an enormous number of functions on a one-button flashlight. example: https://budgetlightforum.com/uploads/default/optimized/3X/e/5/e5acf67cc0ac58293f0a2df74e46e80c25d2ae12_2_1035x685.png https://budgetlightforum.com/uploads/default/optimized/3X/e/... or in text: https://ivanthinking.net/manuals/anduril2-manual/ https://ivanthinking.net/manuals/anduril2-manual/
- othmanosx 2mo ago
  Yeah, I thought of this while writing my comment. I hate this actually, in all devices where you want to cut on the number of button there are, like a headphones for examples, having one button that does stop/play/next/prev/reset/whatever... is really annyoing, one button having too many functions is really bad UX IMO. I'd rather have another button to press once rather than holding the first one for 15 seconds to do some other thing
  - m463 2mo ago
    gah you have described something I do 100 times a day. I listen to audiobooks and skip back is click-click-click of main button. Why can't I get audiobook-friendly headphones? on the other hand, I do have a page-turner device for reading ebooks: https://www.amazon.com/dp/B0DS26MQZM https://www.amazon.com/dp/B0DS26MQZM imperfect but lazy-optimized-wonderful

m463 2mo ago

Just to go out on a wild tangent... buttons on simple hardware devices usually have many many functions. this button has a function. but if you are powering up and hold it, it does a different function. press and hold this button and while holding it press another button for something else. The most extreme example of this kind of thing I can recall is the anduril open-source flashlight firmware: an enormous number of functions on a one-button flashlight. example: https://budgetlightforum.com/uploads/default/optimized/3X/e/5/e5acf67cc0ac58293f0a2df74e46e80c25d2ae12_2_1035x685.png https://budgetlightforum.com/uploads/default/optimized/3X/e/... or in text: https://ivanthinking.net/manuals/anduril2-manual/ https://ivanthinking.net/manuals/anduril2-manual/

othmanosx 2mo ago
Yeah, I thought of this while writing my comment. I hate this actually, in all devices where you want to cut on the number of button there are, like a headphones for examples, having one button that does stop/play/next/prev/reset/whatever... is really annyoing, one button having too many functions is really bad UX IMO. I'd rather have another button to press once rather than holding the first one for 15 seconds to do some other thing
- m463 2mo ago
  gah you have described something I do 100 times a day. I listen to audiobooks and skip back is click-click-click of main button. Why can't I get audiobook-friendly headphones? on the other hand, I do have a page-turner device for reading ebooks: https://www.amazon.com/dp/B0DS26MQZM https://www.amazon.com/dp/B0DS26MQZM imperfect but lazy-optimized-wonderful