[ 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.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1793965913819.jpg (261.94 KB, 1024x1024, img_1793965905253_uhludx1v.jpg)ImgOps Exif Google Yandex

e1180 No.2443[Reply]

the confetti problem is real. it's fine to have a nice animation for finishing a business setup, but seeing that same burst after updating the 47th record of the day feels totally patronizing. figma's agent can follow every rule in our system and still deliver an 'emotionally inappropriate' response because it doesn't know if the user is in a rush or celebrating. i'm worried we're just going to end up with a bunch of perfectly polished but deeply annoying interfaces. do you think we'll actually be able to prompt for 'vibe' or is that just more bloat?

found this here: https://uxdesign.cc/ai-can-generate-the-interface-what-makes-it-worth-caring-about-a5f3a3e81986?source=rss----138adf9c44c---4


File: 1793413730538.jpg (356.13 KB, 1024x1024, img_1793413722304_d4lrpw72.jpg)ImgOps Exif Google Yandex

d3e8f No.2408[Reply]

nn/g's move to experience specialist actually makes sense if you think about ai agents booking flights or filing complaints without us even being in the loop. i don't know how we're supposed to map a customer journey when there isn't even a human touching the interface anymore.

link: https://www.nngroup.com/articles/ux-vs-experience-design/?utm_source=rss&utm_medium=feed&utm_campaign=rss-syndication

55a24 No.2439

File: 1793871883623.jpg (264.21 KB, 1733x1300, img_1793871868310_yqdtdp7j.jpg)ImgOps Exif Google Yandex

>>2408
>there isn't even a human touching the interface anymore
spent all week optimizing a checkout flow for a client only to find out their users are just using brave extensions to scrape data and bypass everything. just building for headless bots now.



File: 1793863578181.jpg (26.4 KB, 1280x960, img_1793863570111_c7q0tgs8.jpg)ImgOps Exif Google Yandex

6c58b No.2438[Reply]

i'm tired of seeing heavy background color changes every time a cursor moves over a link. try designing a small component this week using only subtle border or underline shifts instead.


File: 1793820850063.jpg (195.12 KB, 1024x1024, img_1793820841827_ipsqubdw.jpg)ImgOps Exif Google Yandex

0d6d0 No.2436[Reply]

just read something that really called out how we act like our own moral convictions are some kind of universal truth for users. it's so true that deciding what to make visible or where to add friction is actually a huge responsibility, not just a way to signal how "good" we are as designers.
>our convictions carry weight because we make decisions for other people
ngl i feel like most of my client work is just trying to balance protecting users from harm vs. their autonomy without being a total hypocrite.

https://uxdesign.cc/virtue-ethics-in-everyday-interface-design-5f2aca841781?source=rss----138adf9c44c---4


File: 1793291197964.jpg (239.64 KB, 1024x1024, img_1793291189222_abexo815.jpg)ImgOps Exif Google Yandex

f2ec2 No.2399[Reply]

i'm tired of seeing 1.2 leading in sidebars where everything just bleeds together. Try setting your tightest navigation component to exactly 1.4 and see if it actually stops the eye-strain.

c83a0 No.2432

>>2399
>Try setting your tightest navigation component to exactly 1.4

I've been trying something similar in Figma but I can't tell if it's working or if I'm just making the whole sidebar too tall. Did you measure that 1.4 against a specific font size?

c83a0 No.2435

File: 1793806877185.jpg (83.2 KB, 1024x1024, img_1793806863986_t9jsnihd.jpg)ImgOps Exif Google Yandex

>>2399
I tried 1.4 on a dashboard project last week and it definitely helped with the readability. It felt much less cramped than what we had before. Are you using that value for the whole typography scale or just the specific navigation items?



File: 1793778064201.jpg (333.06 KB, 1024x1024, img_1793778054340_kb3sx9g1.jpg)ImgOps Exif Google Yandex

94369 No.2434[Reply]

the idea of using the macos notch to annotate everything on your screen sounds like a total nightmare for my focus. apparently they're moving away from just typing in chat boxes and now you can basically use video or screenshots to fix layout issues. it's supposed to bridge that gap when the design system fails at the last mile. i saw they're claiming agents are hitting about 90 percent accuracy now instead of the old 50 percent range. still seems like a lot of manual babysitting if you're just marking up figma comments or pointing at pixels. it's basically just another way to do visual QA but for an agent instead of a person. i can't imagine how much time we'd waste just drawing boxes on screenshots all day. feels like we're just trading one type of tedious work for another. do you think anyone actually wants to spend their afternoon annotating screen recordings?

https://www.lukew.com/ff/2170/design-feedback-for-ai-agents


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

8b7ba No.2414[Reply]

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.



File: 1793370841448.jpg (354.87 KB, 1024x1024, img_1793370833294_itlnhltq.jpg)ImgOps Exif Google Yandex

f3afe No.2405[Reply]

was reading about the differences between managing contractors versus using an EOR for people in places like brazil or japan. it's basically just comparing how they handle onboarding and payments without the whole legal entity headache.
>the company typically contracts directly with the freelancer
i don't know if i'd trust a platform to handle all that compliance stuff alone when things get actually complicated with local regs. anyone else using these for their freelance team yet?

more here: https://uxplanet.org/deel-vs-rippling-for-contractor-management-which-platform-gets-the-user-experience-right-275775f329d8?source=rss----819cc2aaeee0---4

d8580 No.2424

>>2405
>i don't know if i'd trust a platform to handle all that compliance stuff alone when things get actually complicated with local regs.

I had the same doubt when we brought on a dev from Argentina last summer. We ended up using an EOR because the paperwork for direct contracting was becoming a total nightmare for our finance lead.

d8580 No.2426

>>2405
The compliance headache is real, especially when you're trying to keep everything organized. I tried managing a small group of designers through direct contracts once and the margin errors in our invoicing system were driving me insane. The hierarchy of info was just unreadable a mess. We switched to an EOR because seeing that cleaner interface actually saved my sanity.

b9a51 No.2428

>>2426
The interface for Rippling isn't even the main perk. The real win is that it actually automates the tax forms so you aren't manually chasing people for paperwork every single month.



File: 1793698333275.jpg (305.47 KB, 1024x1024, img_1793698323825_v7ehjp4a.jpg)ImgOps Exif Google Yandex

4debe No.2427[Reply]

just saw someone recycling that building analogy again.
>the top-most plane is the Surface, which is the most visible or concrete aspect of ux design
it's such a cliché way to explain why we don't just paint pretty buttons on top of broken flows. do people still actually use this framework for anything besides portfolios?

found this here: https://ixdf.org/literature/article/the-relationship-between-visual-design-and-user-experience-design


File: 1793655736792.jpg (115.2 KB, 1024x1024, img_1793655728264_5yai3dc5.jpg)ImgOps Exif Google Yandex

cb781 No.2423[Reply]

saw some tests comparing 'frontend design' vs 'ui/ux pro max' results. it's wild how much the output changes just by tweaking the prompt for taste skill. honestly feels like a lot of hype when the actual layout logic is still pretty mediocre. idk if i trust it with anything more complex than a basic flexbox setup

link: https://uxplanet.org/i-tested-3-claude-code-skills-for-web-design-which-one-is-best-521137220dc1?source=rss----819cc2aaeee0---4


Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]