You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A delay of 0.2–1.0 seconds does mean that users notice the delay and thus feel the computer is "working" on the command, as opposed to having the command be a direct effect of the users' actions.
Currently when clicking "Create" if the createSuggestion promise resolves quickly then the UI state for "loading" only displays very briefly. This can be jarring (as per @karmatosed's comment below).
To avoid this we should enforce a minimum delay on the "Creation" of between 500 - 1000ms to the ensure the user can perceive the editor is doing "work".
The 'creating page' flashed a little too short. I wonder if we either shouldn't see it or should and then carry on. Seeing a flash was a little weird for an experience.
The text was updated successfully, but these errors were encountered:
https://www.nngroup.com/articles/response-times-3-important-limits/
Currently when clicking "Create" if the
createSuggestion
promise resolves quickly then the UI state for "loading" only displays very briefly. This can be jarring (as per @karmatosed's comment below).To avoid this we should enforce a minimum delay on the "Creation" of between 500 - 1000ms to the ensure the user can perceive the editor is doing "work".
Originally posted by @karmatosed in #19775 (comment)
The text was updated successfully, but these errors were encountered: