Gregory's Server59. Please don't use confirmation dialogues, but if for some reason you absolutely must, don't sleepwalk through writing the the messages and the button labels. Don't just label them "okay" and "cancel" Without thinking about whether that wording harmonises with the message text. If possible, label the buttons as what they actually do, specifically.
|
28 comments
 Calling @Chartodon ...
0
0
17 Apr 2021 at 1:47 | Open on libranet.de
 @zensaiyuki This is exactly why I advise against using JavaScript's alert(), confirm(), or prompt() functions: They don't allow you to label your buttons anything other than "Okay" & "Cancel". I generally prefer native UIs, but in this case: PLEASE implement your own! Preferably something non-blocking like GTK's InfoBars.  @zensaiyuki I really like how NMS both does this and - crucially - says "your game was last saved X minutes ago". So I can go "saved 1 minute ago? yeah okay we're all caught up." or "oh, 6 minutes? we were just sitting in our ship the whole time, 's'fine." 60. Plan for failure software breaks. hardware fails. services go down. users make mistakes. Anticipate as many failure modes as you can, and design recovery plans and craft reasonable, well written communications for the user. Technical writing is its own topic, but for error messages the important things to accomplish are 62. Stop making your updates so intrusive. I open an app to use it. if you force me to stop and update it first i forget what I opened it to do. this is user hostile behavior. Ideally, users should not be bothered about updates at all- but unfortunately they a necessary. a less intrusive pattern is asking for permission to download and install an update on app EXIT. just don’t ask using a blocking modal dialog, for the love of durga. the least intrusive pattern of all is web apps that are just automatically always the latest version, and at worst, occasionally ask you to reload your browser so the front end matches the back end. this is a tradeoff of course because those updates happen without consent.  @zensaiyuki @zens yep. As any D&D player will attest: 1% is a lot higher chance than you think 68. don’t assume your users’ devices resemble yours or your close circle of friends when deciding minimum requirements- especially if you intend to reach a wider audience with a range of socioeconomic conditions and internet connection speeds. brought to you by the Australian government locking welfare payments behind a mininum iOS version. Le dernier message avant le mien, "the Australian government locking welfare payments behind a mininum iOS version." 70. your ui should not passively animate for anything less important than a carbon monoxide leak. it's effective at getting attention, often way too effective. via @binarycat  @zensaiyuki@mastodon.social It's a fairly straightforward argument to make that this is illegal per GDPR too, data minimisation is a binding legal requirement and demanding people register when there's no actual necessity seems to contradict that @zensaiyuki Wow, they're like shop security asking you to buy something or leave. Except they also want you to open a loyalty account. |