3 ms·

This is certainly one of the most frustrating things in modern UIs, although I’m not sure what it’s called I feel like it’s common enough for someone to have co

by klysm 6y ago

This is certainly one of the most frustrating things in modern UIs, although I’m not sure what it’s called I feel like it’s common enough for someone to have coined a name by this point. There are a few ways I can think of to deal with it: 1. Have very close to 0 latency. Clearly not always doable. 2. When in the process of searching, indicate to the user that the results aren’t fresh and new ones are coming - grey out the current options for instance. 3. Analyze how long the new results have been shown for and treat very short durations differently. If the new results have been up for 2ms, it’s not possible for that to be your desired intention.

klysm 6y ago
Another possibility would be to freeze the results if the user is moving their mouse/arrow keys over the options.
- igorbark 6y ago
  doesn't work for mobile unfortunately
  - willcipriano 6y ago
    A possible solution: Human reaction time is on the order of something like 215ms, if the change happened less than 100ms ago or so, the user probably wanted the previous result as opposed to the current one. Add a additional dialog to confirm?
    - igorbark 6y ago
      nifty! i was thinking that new results (even if more relevant) get appended to the bottom
    - fareesh 6y ago
      This was one of the approaches I thought of but I wanted to know if this is a "solved" problem or whether there are some prevailing best practices by people who have spent time researching the various approaches Apparently it seems like one of those "can't believe it's 2020 and we can't solve X" types of problems
- jraph 6y ago
  That would not be sufficient even with a mouse: sometimes, I start moving my mouse and then click on the result that has already moved before I even started moving the mouse, but the whole interaction takes less than one second so I don't have the time to react to the update. Graying out the results while the new one are coming can also be annoying: if the result that I am looking for is here and the new results are slow to come, I would be frustrated to be unable to click on it. The whole situation is annoying but I don't know of a good solution and therefore I can't blame people who don't get this right.

by klysm 6y ago

klysm 6y ago

Another possibility would be to freeze the results if the user is moving their mouse/arrow keys over the options.

igorbark 6y ago
doesn't work for mobile unfortunately
- willcipriano 6y ago
  A possible solution: Human reaction time is on the order of something like 215ms, if the change happened less than 100ms ago or so, the user probably wanted the previous result as opposed to the current one. Add a additional dialog to confirm?
  - igorbark 6y ago
    nifty! i was thinking that new results (even if more relevant) get appended to the bottom
  - fareesh 6y ago
    This was one of the approaches I thought of but I wanted to know if this is a "solved" problem or whether there are some prevailing best practices by people who have spent time researching the various approaches Apparently it seems like one of those "can't believe it's 2020 and we can't solve X" types of problems
jraph 6y ago
That would not be sufficient even with a mouse: sometimes, I start moving my mouse and then click on the result that has already moved before I even started moving the mouse, but the whole interaction takes less than one second so I don't have the time to react to the update. Graying out the results while the new one are coming can also be annoying: if the result that I am looking for is here and the new results are slow to come, I would be frustrated to be unable to click on it. The whole situation is annoying but I don't know of a good solution and therefore I can't blame people who don't get this right.