4 ms·
You don't need a spinner if feedback from clicking the button is sufficiently quick. According to Google that would be around 100ms. > Guidelines: > Process
by rane 7y ago
You don't need a spinner if feedback from clicking the button is sufficiently quick.
According to Google that would be around 100ms.
> Guidelines:
> Process user input events within 50ms to ensure a visible response within 100ms, otherwise the connection between action and reaction is broken. This applies to most inputs, such as clicking buttons, toggling form controls, or starting animations. This does not apply to touch drags or scrolls.
https://developers.google.com/web/fundamentals/performance/rail https://developers.google.com/web/fundamentals/performance/r...
- ricardobeat 7y agoThat only applies to actions which have an immediate, perceivable effect, which might not be the case for submitting a form, as described in the OP. For example, opening a dropdown, selecting a checkbox or radio button, etc.
- toastal 7y agoIn the case of network it's also presupposing that the user's has a low-latency, fast connection--which should basically never be assumed.