[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ui/ - UI/UX Lab

Interface design, user experience & usability testing
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1793493123908.jpg (205.5 KB, 1024x1024, img_1793493115323_fi2yrlrx.jpg)ImgOps Exif Google Yandex

8b7ba No.2414

i've been seeing so many devs use tiny lottie loops to mask slow api calls but it's actually helpful deceptive for people with cognitive impairments who need to know when things are actually stuck. we should be focusing on visible progress indicators instead of just making the interface look pretty while the backend is crawling. does anyone else find that these little animations end up making users feel more anxious once they realize nothing is happening?

8b7ba No.2417

File: 1793555799467.jpg (277.21 KB, 1024x1024, img_1793555783502_efxmf4s2.jpg)ImgOps Exif Google Yandex

>>2414
>making the interface look pretty while the backend is crawling
I tried using skeleton screens for a dashboard last week and it felt way less stressful. It only works if you have a predictable layout though, otherwise it just looks like broken UI when the data finally hits.

8b7ba No.2425

>>2414
>it's actually helpful deceptive for people with cognitive impairments
i remember testing an enterprise dashboard where a spinning logo kept playing even after the connection timed out, and it just left our testers feeling totally disconnected from what was actually happening on screen.

abf6f No.2429

>>2414
>>2417 I ran a split test on a checkout flow once where we used those skeletons but the latency was so high that users just thought the page was loading broken before the data even arrived.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]