Conversation

Notices

1. Embed this notice
   mekka okereke :verified: (mekkaokereke@hachyderm.io)'s status on Sunday, 08-Sep-2024 00:22:12 JST mekka okereke :verified:

   Me when running a service:
   Oh no. One of our back-end services is down. This is causing latency spikes on the front-end and in the mobile app. Users don't understand what's happening, so they keep hitting reload. This is adding even more load to the server and making things worse. Only technical users know to just wait a while, and then try again later.

   Me when using a service:
   What the hell?! This should've loaded already! Why so slow?! I'll click reload a few more times! *ReloadReloadReload*

   • Embed this notice
     Dawn Ahukanna (dahukanna@mastodon.social)'s status on Sunday, 08-Sep-2024 00:22:11 JST Dawn Ahukanna

     in reply to

     @mekkaokereke
     Designer: probably should add:
     1. Loading pointer icon indicator
     2.Lloading, please wait UI interaction affordance
     3. UI throttle-trap to intercept repeat selects on the same control before the previous micro service requests have completed and returned their results.

     Developer: Don’t need to do none of that! Any reasonable person would make the request and wait. I know (not I presume with evidenced probability of zero-0) that they won’t repeatedly select the button.

     Designer: 🫣

     Paul Cantrell repeated this.
   • Embed this notice
     Marcel_Gehlen (he/him) (marcel_gehlen@social.tchncs.de)'s status on Sunday, 08-Sep-2024 00:22:11 JST Marcel_Gehlen (he/him)

     in reply to

     • Dawn Ahukanna

     @dahukanna @mekkaokereke

     We once recovered a whole star in the App Store when we corrected an error message from „no internet“ to „sorry our service is down“ when one of our services did not respond.

     This is how influential better UI design is.