For all developers asked to design something or not given a design - CSS padding is your friend. Add spacing and then add more. It won't make it a masterpiece but it'll prevent misclicks and make the UI easier to read and understand. Also, use headings like "Amber Alerts", "Weather" and "War". And, use semantic titles like "[TEST] Tsunami" or "ALERT! - Tsunami"
It Was Bad UX, not a “Wrong Button” in Hawaii
51–60 of 132 posts
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#52Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#53Earlier quoted context omitted.
Because that's literally the law: > TERRORISTIC THREAT > > (a) A person commits an offense if he threatens to commit any offense involving violence to any person or property with intent to: > > 2. place any person in fear of imminent serious bodily injury;
That's a fucked up law. If some guys in a bar start arguing about a spilled drink and one says "I'm gonna punch you!", that shouldn't be considered terrorism! Terrorism used to mean violence or a real threat of violence committed for political reasons. Now it just means any crime committed by someone whose motives (or whose ethnic group) the speaker disapproves of.
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#54For all developers asked to design something or not given a design - CSS padding is your friend. Add spacing and then add more. It won't make it a masterpiece but it'll prevent misclicks and make the UI easier to read and understand. Also, use headings like "Amber Alerts", "Weather" and "War". And, use semantic titles like "[TEST] Tsunami" or "ALERT! - Tsunami"
And for certain actions (such as deleting a file or letting a population know an IBCM is coming at them), it could be a good idea to add a msgbox asking "are you sure you want to ? [yes] [cancel]" ^^
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#55The UX in most software made for the government is terrible. At the end of the day, I think anyone clicking any button in that list should have been well aware of what those buttons do especially since clicking that button was a routine part of the shift change process in that shop. Bad UX, sure. But that person dun goofed.
Interfaces are always designed by the programmers alone, and they are universally awful.
Heck, several years ago I remember having to learn Blender so I could create 3D models for some simulation software (no one else to do it, guess it's me again -> here have some rockets that look like something out of 1950s scifi). Apparently the folks writing the contract didn't think we'd need anyone with any 3D art skills to create 3D visualization software.
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#56A lot of conversations seem fixated on what's the worst that could happen if the wrong message was sent, but very few of these people are considering what's the worst that could happen if the right message wasn't sent. Also, it's very likely that the dropdown message text was not added by a developer, and this addition of the messages by non-technical users should also be part of that UX conversation.
Missile warning: Everyone flees to basements.
Right next to each other, no way that'll go wrong.
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#57There was a very similar incident in 1971 ("code word hatefulness"). Back then, three tapes were kept next to a EBS transmitter, two real alerts and one for testing. One day, an operator accidentally loaded the real alert rather than the correct test alert, and many stations prepared to tell the country the nuclear war was imminent. The fix was to: > …In the past three tapes, one for the test and two for actual emerg…
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#58If it takes two people turning two keys to launch a missile, shouldn't it take the same to send a missile warning?
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#59Earlier quoted context omitted.
Why do you see that as terrorism?
Because that's literally the law: > TERRORISTIC THREAT > > (a) A person commits an offense if he threatens to commit any offense involving violence to any person or property with intent to: > > 2. place any person in fear of imminent serious bodily injury;
Re: It Was Bad UX, not a “Wrong Button” in Hawaii
#60There was a very similar incident in 1971 ("code word hatefulness"). Back then, three tapes were kept next to a EBS transmitter, two real alerts and one for testing. One day, an operator accidentally loaded the real alert rather than the correct test alert, and many stations prepared to tell the country the nuclear war was imminent. The fix was to: > …In the past three tapes, one for the test and two for actual emerg…
That's a good example. Shockingly poor foresight. It's similar to the "A gun is always loaded" principle. Unless you can tell at a glance that a firearm is not in a ready-to-fire state, you treat it as if it is. People are clumsy and forgetful, and you only have to mess up once. Leaving the live rounds right next to the blanks, in that way, is pretty indefensible. (Ignoring of course that blanks can still kill, for t…
That's when you need to treat it like it is the most.