4 ms·
This kind of thing is related to Alarm Fatigue [0] and also has implications for designing software notifications and dialogs. More is not always better when i
by Terr_ 3y ago
This kind of thing is related to Alarm Fatigue [0] and also has implications for designing software notifications and dialogs.
More is not always better when it comes to warnings, and is often worse.
[0] https://en.wikipedia.org/wiki/Alarm_fatigue https://en.wikipedia.org/wiki/Alarm_fatigue
- nicbou 3y agoKorean emergency alerts are a good example. I got 5-10 a day during my first week in Seoul. At first it's scary, then it's annoying, then you turn them off.
- ehnto 3y agoI managed a product that was producing nearly a million exceptions every week. The developer considered almost every circumstance to be an exception. Username and password wrong? Exception. Form field not validated? Exception! Request timeout, ah! Whatever will we do! Exception! There were even some exceptions for things that went well. But you can imagine, if everything is exceptional, real issues don't stand out anymore and go unnoticed.
- euroderf 3y agoIt's a rule of software development management: If everything is a priority... then nothing is a priority.
- Dalewyn 3y ago>also has implications for designing software notifications and dialogs. I block notifs[1] from 99% of the programs on my phone because THEY. ARE. NOT. IMPORTANT. The small handful of programs that do have notifications enabled are because they actually are worth my attention. [1]: No, I refuse to properly call them notifications because notifs are not notifications. Notifications shouldn't be making me question if they are important, hence notif.