3 ms·

It might be a function of my age but I find the lottery app in Europes ability to scan the barcode so fast from the camera on my phone that I don't trust it. I

It might be a function of my age but I find the lottery app in Europes ability to scan the barcode so fast from the camera on my phone that I don't trust it. It's almost as if I don't trust things that happen too fast with my 20+ years experience with IT

ketzo 4y ago
just this week, I put a minimum 200ms wait time on a loading spinner, because otherwise we thought it felt "buggy" because it was completing too quickly!
- janc_ 4y ago
  The alternative is to show no spinner at all when something is that fast, of course...
  - ketzo 4y ago
    haha you're not wrong but it's an async process that could take longer, so then you get into "well if it's <200ms we won't show a spinner, but if it takes longer we will..." it's a settings page where you're clicking toggles, and each toggle saves automatically when you hit it. so when you click one, you get a short spinner, then a check mark when it succeeds. feels right to me when I'm using it
- b112 4y ago
  Monsters!
  - ketzo 4y ago
    y'know, I felt like a monster doing it, but it weirdly is way more satisfying to use it goes from "wtf just flickered on my screen" to "wow, that loaded really fast!
- frosted-flakes 4y ago
  There should be a short delay (200ms to 500ms) before showing a loading spinner, and if the operation completes in that time you can avoid showing it at all. But if it takes longer than that, the spinner should be shown for a minimum of 500ms or so, to avoid a sudden flash of the spinner. I wrote a React hook called usePending[1] for this once. It's surprisingly difficult to get right. [1] https://gist.github.com/cmmartti/4f7833292b9d277685fc08135326e8a3 https://gist.github.com/cmmartti/4f7833292b9d277685fc0813532...
  - ketzo 4y ago
    wow, wait, this is awesome. I think I might drop this in instead. thank you!
mjrbrennan 4y ago
I feel the same way about the one here in Australia -- I always double check it's scanned the correct numbers. Haven't been cheated out of millions yet, unfortunately.
dylan604 4y ago
Surely, you're not saying that the system is rigged to say "You're Not A Winner"?

ketzo 4y ago

just this week, I put a minimum 200ms wait time on a loading spinner, because otherwise we thought it felt "buggy" because it was completing too quickly!

janc_ 4y ago
The alternative is to show no spinner at all when something is that fast, of course...
- ketzo 4y ago
  haha you're not wrong but it's an async process that could take longer, so then you get into "well if it's <200ms we won't show a spinner, but if it takes longer we will..." it's a settings page where you're clicking toggles, and each toggle saves automatically when you hit it. so when you click one, you get a short spinner, then a check mark when it succeeds. feels right to me when I'm using it
b112 4y ago
Monsters!
- ketzo 4y ago
  y'know, I felt like a monster doing it, but it weirdly is way more satisfying to use it goes from "wtf just flickered on my screen" to "wow, that loaded really fast!
frosted-flakes 4y ago
There should be a short delay (200ms to 500ms) before showing a loading spinner, and if the operation completes in that time you can avoid showing it at all. But if it takes longer than that, the spinner should be shown for a minimum of 500ms or so, to avoid a sudden flash of the spinner. I wrote a React hook called usePending[1] for this once. It's surprisingly difficult to get right. [1] https://gist.github.com/cmmartti/4f7833292b9d277685fc08135326e8a3 https://gist.github.com/cmmartti/4f7833292b9d277685fc0813532...
- ketzo 4y ago
  wow, wait, this is awesome. I think I might drop this in instead. thank you!

mjrbrennan 4y ago

I feel the same way about the one here in Australia -- I always double check it's scanned the correct numbers. Haven't been cheated out of millions yet, unfortunately.

dylan604 4y ago

Surely, you're not saying that the system is rigged to say "You're Not A Winner"?