3 ms·
I experienced this first hand with the manual sync button on one of my apps. I got feedback stating it didn't work when, in reality, there was no work to be don
by thealchemistdev 3y ago
I experienced this first hand with the manual sync button on one of my apps. I got feedback stating it didn't work when, in reality, there was no work to be done and the interface didn't have time to display 'syncing' before it finished.
The solution was to add a 50-300ms delay before the network request. Why? Because feelings and perception matter more than facts.
- _thisdot 3y agoPerceived loading time was a matter of debate during the NextJS vs RemixJS thing. RemixJS argued for fast loading time, while NextJS argued for perceived loading time. Remix would show a white screen and two seconds later have everything ready. Next would show the header and a loader first then gradually over the course of 3-5 seconds have everything ready.
- samsolomon 3y agoI see a lot of comments here about added animations because the request is too fast. In this case I would guess the issue is not with speed but feedback. The user did something, nothing changed, so they thought it was broken. Instead of the delay you could add a toast or some text with near the button indicating that the action actually happened.
- IIsi50MHz 3y agoModerate preference for the added text, rather than an an ephemeral 'toast' message.