Sometimes, a UI doesn't feel right because it's too fast. The solution: Just slow it down a bit. #uxdesign #ui #screenshotsaturday #buildinpublic
Discussion
Loading...
@keila I don't think I understand the context because the extra delay doesn't feel like an improvement.
What does "current value" mean and does the delay make it more stable?
If it waits for DNS to propagate, the proper delay that doesn't cause confusion could be measured in minutes.
@dcz This is a UI that shows you whether you have added the correct CNAME entries to your domain. So users will only use this button once or twice when setting up their domain - or if they don't trigger it manually with the button, a background job will check it automatically every few minutes.
@dcz To be even more specific: When you want to set up your newsletter with Keila Cloud, you need to add a few DNS entries. This UI helps you see if you've added the correct entries/if they've propagated already.
@keila Ah, I see now. So it is checking the propagation through external systems.
I think this UI is going to be frustrating to the people who don't know what's going on because it's still occationally "flaky" by returning unstable results. On the other hand, it's going to be frustrating to those who know what's going on because it's a little paternalistic with "nope, I'm not letting you see the result immediately".
I'd look for a solution in setting expectations rather than hiding complexity.
@keila Please don't actually do this. Add a little bit of text saying "n requests made (502ms)" or something: there are ways to increase my confidence that the computer is actually doing something, without adding artificial delays.
All this means is that (a) my workflow gets slowed down for no reason, and (b) it's harder to debug when something actually goes wrong, because I think the delay means it's "doing something" – even though it's completely fake.
@wizzwizz4 I would generally agree with this, but I think in this case it makes sense because this specific feature should be debounced/rate-limited anyways and users don't need to use it frequently.
@keila @wizzwizz4 Please... no...
@chebra @wizzwizz4 Why not, though? 🤔
@keila @wizzwizz4 Artificial delay in UI is never a good idea. No matter if everyone else is doing it. Everyone else is enshittifying, you don't have to follow them.
@chebra @wizzwizz4 In this case, I think it does two important things:
1) It helps communicate to the user that the check actually took place. Especially when there's no change, that might be hard to believe.
2) It introduces a rate-limit/debounce that prevents users from clicking the button over and over again
1) It helps communicate to the user that the check actually took place. Especially when there's no change, that might be hard to believe.
2) It introduces a rate-limit/debounce that prevents users from clicking the button over and over again
1+ more replies (not shown)
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled