3 ms·
You return whatever results you can before the user perceives a delay. If you think a web search or slower search is useful (it isn't) then add a button to exp
by mulmen 5y ago
You return whatever results you can before the user perceives a delay. If you think a web search or slower search is useful (it isn't) then add a button to expand the search such as "Search the web for ${search term}" or "Continue this search in Explorer".
mulmen's laws of UX design:
1. It is never ok for the user to perceive input delay.
2. There must be no compromise in service of law #1.
3. Your UX improvement is a regression until proven otherwise.
4. To change the UX you must first destroy something you love.
5. The CPU belongs to the user, not to you.
- jojo14 5y ago"before the user perceives a delay": I agree with you. For any UX/UI designer out there a delay is perceived when it is greater than 200ms. Those are milliseconds.
- dragonwriter 5y ago> For any UX/UI designer out there a delay is perceived when it is greater than 200ms. Those are milliseconds. Delay is perceptible at around 10ms, and considered tolerable for generic apps (not realtime games, obviously) to about 100ms, and that's been established for quite a long time. 200ms is...too much.