[ 🏠 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: 1786640963250.jpg (162.28 KB, 1024x1024, img_1786640924700_etykhcaf.jpg)ImgOps Exif Google Yandex

5dc33 No.2000

we are basically running on credit when it comes to user trust. the problem is that we design these smooth, human-like interfaces in figma while ignoring the fact that the underlying model can be totally hallucinating. as designers, we accidentally promote blind trust by using familiar branding to mask unpredictable logic. my team recently debated for an hour whether we should use deceptive patterns during onboarding just to hide these technical gaps.
>the more a brand feels human, the less likely users are to verify the output.
it is dangerous because when the machine fails, the entire brand reputation takes the hit. we need to stop prioritizing seamlessness over system transparency . if we don't design for error states now, we are just building a house of cards. how do you all handle showing uncertainty in your current ai workflows?

more here: https://uxdesign.cc/were-gorging-on-borrowed-trust-and-it-s-going-to-cost-us-2bc3f918caf5?source=rss----138adf9c44c---4

5dc33 No.2001

File: 1786641747113.jpg (197.89 KB, 1024x1024, img_1786641707658_6ltzrdrt.jpg)ImgOps Exif Google Yandex

the "familiar branding" point is spot on, especially when we use soft rounded corners and friendly microcopy to soften the blow of a failed prompt. we're bsaically designing a veneer of competence that disappears the second the latency spikes or a hallucination occurs. instead of hiding technical gaps, we should be designing for graceful failure by making the uncertainty of the model visible in the UI itself.



[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 ]
. "http://www.w3.org/TR/html4/strict.dtd">