从用户体验的角度来看，可以为微调器设置最短显示时间吗？
我的任务是根据可以在 UI 上选择的多个记录（源）中的数据生成文件。用户可以选择 1 到 100 条记录。生成（请求处理）时间取决于所选记录的数量。它可以是从几毫秒到大约 5 秒。
我计划显示此请求的微调器组件。但正如我上面提到的，它可能处理得太快并且旋转器会闪烁。那么，从用户体验的角度来看，为旋转器设置一些最短显示时间以防止令人讨厌的闪烁是否可以？如果是，那么最好的超时时间是多少？ 1秒？
PS 我读过一篇很棒的进度指示器让缓慢的系统变得更难以忍受文章尼尔森诺曼集团网站。但它并没有完全回答我的问题。
I have a task to generate a file based on the data from several records (sources) that could be selected on UI. A user can select from 1 to 100 records. The generation (request processing) time depends on the number of selected records. It can be from several milliseconds to approximately 5 seconds.
I am planning to display the spinner component for this request. But as I mentioned above it might be processed too fast and the spinner will blink. So, is it ok from the UX standpoint to set some minimum displaying time for the spinner to prevent irritating blinks? If yes, then what is the best timeout? 1 second?
P.S. I have read a great Progress Indicators Make a Slow System Less Insufferable article on the Nielsen Norman Group website. But it does not fully answer my question.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
尼尔森的研究表明您对 1 秒的猜测是在正确的区域- 或者更具体地说，所需的时间介于 0.1 秒和 1 秒之间。我可能会尝试 0.5 秒，看看用户感觉如何。
请注意，由于您可以提前大概知道时间，因此您可以立即知道天气或不打开旋转器。因此，如果用户按下按钮时选择的选项少于 10 个（根据上面给出的数字，假设线性关系，10 个大约为 0.5 秒），则不要显示微调器，否则，立即显示微调器。这是基于这样的原则：如果程序提前知道一些与 UX 相关的内容，则应立即向用户显示这些内容（同样的原则是，您不应该允许不可能选择的选项 - 即禁用它们 - 而不是让用户选择它们，然后说“抱歉，不能这样做”）。
Neilson's research would suggest that your guess of 1 second is in the right area - or more specifically, that the time needed is somewhere between 0.1 second and 1 second. I'd probably try 0.5 seconds and see how that feels for the users.
Note that as you can approximately tell in advance what the time will be, you know immediately weather or not to turn on your spinner. So, if the user has less than 10 selected when they press the button (based on the numbers given above, assuming a linear relationship, 10 would be about 0.5 seconds) DON'T display the spinner, but otherwise, IMMEDIATELY display the spinner. This is based on the principle that if the program knows something UX related in advance, that should be immediately shown to the user (the same principle that says you should simply not allow options that are impossible to be selected - i.e. disable them - rather than letting the user choose them and then saying "sorry, can't do that").