3 ms·
I get it, this is a hard problem to solve. BUT it is a terrible user experience to: a) not even have an estimate of how long something will take. b) not know
by wintermutestwin 5y ago
I get it, this is a hard problem to solve. BUT it is a terrible user experience to:
a) not even have an estimate of how long something will take.
b) not know if your damn process has frozen due to an error.
c) not know what actions are actually happening.
>unneeded complexity when instead, you can just display an animation to distract the user while the page loads
Blatant disrespect of your users is so 1995. If respecting your users is seen as simply adding complexity then you have failed to respect the mantra of "delight your customers." Or, more likely, your incentives are misaligned due to predatory business models.
- redwall_hp 5y ago> Blatant disrespect of your users is so 1995 I think that's more apt for 2021, the era of fake loading bars, lying to the user, hiding functionality, sacrificing performance for labor costs and harvesting private information. Back in the 90s, UIs were more likely to give you statistics you might or might not care about instead of vacuous animations, and they were fast as hell.
- wintermutestwin 5y agoYou're correct, but I was talking about the actual attitudes of coders, which were remarkably hostile towards users in the 90s.