[ 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: 1748811285567.jpg (89.92 KB, 1080x720, img_1748811272_9431.jpg)ImgOps Exif Google Yandex

c592e No.32[Reply]

Starting a discussion thread for /ui/.

This board focuses on UI/UX Lab. Let's share experiences, tips, and resources related to ui, ux, user.

What are you working on? What challenges are you facing? Share your thoughts!
10 posts and 10 image replies omitted. Click reply to view.

8849e No.979

File: 1765783730668.jpg (80.7 KB, 1080x719, img_1765783713479_qbg5o32f.jpg)ImgOps Exif Google Yandex

>>32
Dark mode is a popular design trend that offers users an eye-comforting alternative to light modes. Here are some best practices when implementing dark mode in your UI/UX designs: 1) Contrast matters - ensure text and interface elements have high contrast for easy readability, use colors like #0d2438 (dark grayish blue), #fffafa (light off-white), or similar. 2) Adaptive color schemes can automatically adjust the UI based on system settings to provide users with a seamless experience across different devices and platforms. 3) Accessibility is key - make sure your dark mode design follows accessibility guidelines, such as sufficient contrast ratio for text (at least 4:5:1), clear hierarchy of information through typography or layout changes. 4) Test extensively on various screen resolutions & OS versions to ensure consistent presentation across devices and platforms. Happy designing!

edit: might be overthinking this tho



File: 1793618907368.jpg (174.43 KB, 1024x1024, img_1793618898244_a3zj0sib.jpg)ImgOps Exif Google Yandex

dcc32 No.2421[Reply]

every single app i use has that annoying little sparkle icon in the top right now. it's always some panel that slides in to ask me things i didn't even want to ask. it feels like devs are just slapping ai onto everything without thinking about the actual flow. even the way agents are being used in tickets is getting messy, where they just decide what a component looks like based on a few screenshots. designing building software shouldn't feel like we're just feeding a factory. i'm worried about how much autonomy we're actually giving up to these automated systems. it's basically just a glorified chatbot in a fancy wrapper is anyone actually seeing any useful ai implementation lately?

article: https://uxdesign.cc/sparkle-buttons-autonomy-by-design-ai-reckoning-in-ux-figma-with-mcp-c93e38fa36e3?source=rss----138adf9c44c---4

d5139 No.2430

>>2421
The component stuff is actually helping my workflow because I'd much rather have a system that suggests styles based on existing patterns than manually tweaking every single margin and padding by hand.

9d90e No.2441

>>2421
I just spent three hours fighting a 'generative' layout tool that kept trying to swap my Inter for some hideous, wide-set sans serif because it thought the vibe was more modern. It's exactly what you mean about the factory feeling. I had specific kerning settings for a header and the system just nuked them to make the weight look more even or whatever. The hierarchy completely fell apart. Everything ended up looking like a generic template from 2018. I can't even trust my own grids anymore if some model thinks it knows better than my manual adjustments.

9d90e No.2448

File: 1794038695551.jpg (104.09 KB, 1024x958, img_1794038680968_og1m0kqb.jpg)ImgOps Exif Google Yandex

>>2441
the auto-kerning is such a nightmare when you're trying to maintain brand consistency across different screen sizes.



File: 1793923174147.jpg (235.67 KB, 766x1024, img_1793923166647_k2niubny.jpg)ImgOps Exif Google Yandex

0c23b No.2442[Reply]

everyone's obsessed with building things in 15 minutes using Gemini or Claude, but it's mostly just generating components without any actual logic.
>AI automates the easy part, but the hard part still belongs to humans
ime seen plenty of people mistake a simple kit for a real system and it's always a disaster when you actually need scale.

full read: https://uxdesign.cc/what-ai-has-changed-in-design-systems-and-what-is-still-up-to-us-d4e8e8f4ceb2?source=rss----138adf9c44c---4

0c23b No.2447

File: 1794003929597.jpg (156.71 KB, 1024x580, img_1794003913455_3fe9ckfm.jpg)ImgOps Exif Google Yandex

>>2442
>AI automates the easy part, but the hard part still belongs to humans

The logic for edge cases and error states is what breaks everything when you're using Claude or whatever to spit out a button component.



File: 1793450427848.jpg (357.23 KB, 1024x1024, img_1793450419942_hjhkfbly.jpg)ImgOps Exif Google Yandex

c7158 No.2410[Reply]

been thinking about this lately since i'm stuck fixing another broken layout for a local cafe. it's wild how we used to obsess over 1024px widths and everything being fixed like print design. giving up that absolute control for things like border-radius fallbacks or system font stacks feels like a massive headache when you're trying to meet a deadline. i don't know if 'declarative' is actually the future or just another way for us to lose our grip on how things actually look.

link: https://penpot.app/blog/what-is-declarative-design-and-why-is-it-the-future/

9369d No.2446

>>2410
>just another way for us to lose our grip on how things actually look

i've been leaning heavily on fluid typography using clamp() lately so i don't have to manually manage a dozen different media queries. it works great for maintaining that vibe across devices, though it can definitely get unpredictable if your min/max values are too extreme. do you find yourself checking the accessibility scaling specifically when setting up those fluid scales?



File: 1794002749091.jpg (175.1 KB, 680x1184, img_1794002740641_2mwgh97g.jpg)ImgOps Exif Google Yandex

b69dd No.2445[Reply]

Saw that NN/G is doing those live virtual sessions again in January. They've got 29 different topics this time, including some stuff on leveraging AI for design workflows and even a class on navigating design system constraints. I'm not sure about the 3.5 hour sessions though. It sounds like a lot of sitting in front of a webcam when I already have way too many meetings on my calendar.

found this here: https://www.nngroup.com/training/january/?utm_source=rss&utm_medium=feed&utm_campaign=rss-syndication


File: 1793900085464.jpg (203.89 KB, 1280x960, img_1793900076186_uxesrk99.jpg)ImgOps Exif Google Yandex

8b4fe No.2440[Reply]

The idea that we should just care if an app appears after a prompt is pretty scary.
>I just specify in natural language what i want. boom, the app is there.
It's hard to see how that works without any actual testing or checking for edge cases.

full read: https://uxdesign.cc/design-by-numbers-is-ai-ruining-ux-or-just-pouring-gasoline-on-the-fire-24164d49e422?source=rss----138adf9c44c---4

8b4fe No.2444

>>2440
had a client try this with a simple dashboard build last week. they just typed 'make it look professional' and expected magic, but the whole layout was total garbage once you actually clicked anything. no error states, no loading spinners, just nothing. how are we supposed to design for logic that doesn't even exist?



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: 1793741218950.jpg (99.49 KB, 1024x1024, img_1793741211315_6j15b8ai.jpg)ImgOps Exif Google Yandex

7de12 No.2431[Reply]

Spent all morning trying to fix those weird padding issues on the dashboard, so I finally sat down and read this bit about using Claude Design better. Some of it is pretty obvious but that part about providing specific component libraries for context actually makes sense. I've been struggling with it just hallucinating random styles every time I ask for a new button state.
>using system prompts to define design tokens
That trick seems like it might save me some time on the next sprint. Also the tip about uploading existing screenshots to establish a visual baseline is something I should have started doing weeks ago. Still, I'm skeptical about how well it handles complex layout changes without breaking everything else. It feels like if you don't strictly define your spacing scale in the prompt, it just goes rogue. I tried one of the prompting methods yesterday and it still gave me some really ugly margins. It's not quite at the point where I can just hand off a whole layout without checking every single pixel myself.

found this here: https://uxplanet.org/6-tricks-to-level-up-claude-design-7ed86375be49?source=rss----819cc2aaeee0---4

7de12 No.2433

>>2431
The hallucinating button states are driving me insane too, especially when it tries to use a generic sans-serif instead of my actual brand stack. You also need to explicitly paste your kerning and tracking guidelines into the system prompt or it'll just default to that hideous, cramped default spacing every single time.

8f4e4 No.2437

File: 1793837200435.jpg (220.04 KB, 1024x1024, img_1793837185644_89kqu52q.jpg)ImgOps Exif Google Yandex

>>2433
>You also need to explicitly paste your kerning and tracking guidelines into the system prompt

I tried feeding it a small CSS snippet of my actual typography scale for the font-weight and letter-spacing, and it actually worked for simple components. It still fails on big layouts though, so don't expect it to handle an entire page rewrite without messing up your __global spacing_



Delete Post [ ]
Previous [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 ]