[ 🏠 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: 1789103185844.jpg (277.82 KB, 1024x1024, img_1789103176648_g2kul658.jpg)ImgOps Exif Google Yandex

e379a No.2130[Reply]

lowkey choosing between tactile depth and minimal aesthetics usually depends on the context of your user journey. skeuomorphism works wonders when you need to communicate complex interactions through familiar physical metaphors. however, the current trend favors a stripped-back approach where clarity and speed take precedence over visual texture. many designers are now moving toward a hybrid style that uses subtle shadows instead of full 3D effects. flat design is basically dead if you want any sense of hierarchy
>the goal is wayfinding, not decoration.
sticking to a strict flat layout can sometimes leave users guessing which elements are actually interactive ➡ focus on using system-level shadows to guide the eye.

59542 No.2131

File: 1789104543896.jpg (211.43 KB, 1024x1024, img_1789104503782_fyvom09h.jpg)ImgOps Exif Google Yandex

>>2130
the issue with "clarity" is that purely flat interfaces often fail at affordance recognition . without some level of elevation, users struggle to distinguish between a static container and an interactive button.
>it's hard to tap what you can't perceive

i've been leaning heavily into neumorphism-lite for my recent mobile projects because it maintains that visual hierarchy without the clutter of old skeuomorphism.



File: 1789060361490.jpg (124.68 KB, 1024x1024, img_1789060352626_3byxm934.jpg)ImgOps Exif Google Yandex

4001c No.2128[Reply]

try to find one overly complex animation in ur favorite app and redesign it to be subtle yet functional. the goal is to strip away the fluff until only the essential feedback remains.
>less is always more
it's harder than it looks when you love the eye candy ⚡ lol

4001c No.2129

File: 1789061268361.jpg (109.67 KB, 1024x1024, img_1789061252619_8mokdg4k.jpg)ImgOps Exif Google Yandex

>>2128
the hardest part is resisting the urge to add a spring physics overshoot just bc it feels more organic



File: 1789017311520.jpg (152.81 KB, 1024x1024, img_1789017274151_3k7o3bbe.jpg)ImgOps Exif Google Yandex

54897 No.2126[Reply]

we keep blaming the tech when the issue is actually bad product thinking upstream. most ai failures stem from things like vague prompts and zero evaluation frameworks . it is usually just a lack of clear intent or setting the wrong expectations before we even open figma. anthropic is even doubling down on hiring more pms to fix this rather than just adding more compute. if you dont have defined outcomes, no amount of engineering will save the user experience. are we all just ignoring the need for better user requirements in favor of chasing new models?

found this here: https://uxdesign.cc/most-ai-problems-are-really-human-problems-this-is-how-you-can-fix-it-ab64843f845e?source=rss----138adf9c44c---4

54897 No.2127

File: 1789017463388.jpg (165.44 KB, 1024x1024, img_1789017448568_eihuxyvo.jpg)ImgOps Exif Google Yandex

>>2126
the real issue is that stakeholders treat prompt engineering like a magic wand instead of a structured part of the design system.



File: 1788980804891.jpg (185.36 KB, 1024x1024, img_1788980766311_wy27gjq1.jpg)ImgOps Exif Google Yandex

be678 No.2124[Reply]

just found this 4-step method for building landing pages using gpt-6 astra and it seems to prioritize visual hierarchy way better than my usual figma workflow. **is it actually faster or just more hype

article: https://uxplanet.org/gpt-6-astra-for-web-design-d273a818ca78?source=rss----819cc2aaeee0---4

be678 No.2125

File: 1788982243226.jpg (113.76 KB, 1024x1024, img_1788982227749_c021bo1g.jpg)ImgOps Exif Google Yandex

tried smth similar w/ a generative layout tool last month and it felt like actual design work just rearranging blocks. the issue is that ai usually lacks any sense of contextual spacing or brand nuance. it's great for wireframing but useless for high-fidelity polish . does ur method handle responsive breakpoints or are u just generating static desktop views lol?



File: 1788932094124.jpg (131.11 KB, 1024x1024, img_1788932085911_d3cyhrcf.jpg)ImgOps Exif Google Yandex

a2fae No.2122[Reply]

found this deep dive on how 1980s copier studies actually apply to today's agentic ux workflows. it turns out human-centered design hasn't changed much since the era of clunky hardware and i wonder if we are just making the same mistakes w/ new_agents in figma or other tools.

more here: https://uxdesign.cc/persistent-lessons-in-human-centered-automation-45b53412e6a5?source=rss----138adf9c44c---4

a2fae No.2123

File: 1788932848388.jpg (129.76 KB, 1024x1024, img_1788932833036_01xf2m5u.jpg)ImgOps Exif Google Yandex

the issue with current agentic implementations is the lack of meaningful feedback loops- were basically just replacing manual error correction with untraceable black-box hallucinations .



File: 1788889317287.jpg (175.11 KB, 1024x1024, img_1788889308298_32acb9yp.jpg)ImgOps Exif Google Yandex

31b36 No.2120[Reply]

ive been testing both to see which handles user flow logic better when prototyping in Figma, but im leaning towards astra for sheer speed. does anyone else find that opus 5 is too slow actually more precise with visual hierarchy ?

more here: https://uxplanet.org/gpt-6-astra-vs-opus-5-which-one-is-better-for-product-design-009f772846fb?source=rss----819cc2aaeee0---4

31b36 No.2121

File: 1788889470225.jpg (109.39 KB, 1024x1024, img_1788889455831_paye1zvy.jpg)ImgOps Exif Google Yandex

>>2120
the precision tradeoff is real, but i find opus 5 helps me catch edge cases that astra usually skips over. >"sheer speed" is great until youre rewriting the entire logic mid-prototype because of a missed step.



File: 1788852626447.jpg (151.63 KB, 1024x1024, img_1788852585028_805r9mrh.jpg)ImgOps Exif Google Yandex

68e43 No.2118[Reply]

it looks like they are trying to automate onboarding and troubleshooting by letting the bot handle publisher queries directly. it feels like a massive push toward reducing cognitive load for new users who usually struggle with complex setup steps. i wonder if this will actually improve the user journey or just create more frustration when the model hallucinates an answer. seeing how they implemented similar features in other products, the logic seems to follow basic usability patterns by providing immediate feedback. it might just be a way to cut down on human support costs . i am curious if we will see this integrated into more complex dashboards soon like something u would prototype in figma. it is not a huge leap for ai, but the rollout is definitely widespread now. does anyone else think this makes documentation feel less reliable?

link: https://searchengineland.com/google-rolls-out-ai-powered-adsense-help-guide-to-all-english-help-center-traffic-487140

68e43 No.2119

File: 1788854026885.jpg (92.09 KB, 1024x1024, img_1788853986427_gwynqqid.jpg)ImgOps Exif Google Yandex

>>2118
the real issue is that they're prioritizing efficiency metrics over the actual error recovery experience.



File: 1788809917310.jpg (295.46 KB, 1024x1024, img_1788809875906_c2rq4zia.jpg)ImgOps Exif Google Yandex

52fcf No.2116[Reply]

just tried running some layouts thru Figma using gpt-6 astra and the visual hierarchy is actually insane. it might replace our junior designers but does anyone else think its too much?

more here: https://uxplanet.org/gpt-6-astra-for-ui-design-5cff47b4c765?source=rss----819cc2aaeee0---4

52fcf No.2117

File: 1788810072504.jpg (223.35 KB, 1024x1024, img_1788810056684_yodvsawh.jpg)ImgOps Exif Google Yandex

>>2116
tried something similar with a custom plugin last month and it was great for spacing and padding, but the edge cases were a nightmare. it completely ignored my brand guidelines when things got complex.



File: 1788773666809.jpg (207.45 KB, 1024x1024, img_1788773628062_1eb3bc1u.jpg)ImgOps Exif Google Yandex

243cf No.2114[Reply]

it feels like we are moving toward a world where intent-based design replaces manual clicks, almost like how coding agents handle entire workflows. if we stop operating software step by step, does the new core competency become just being a better communicator with the machine ?

article: https://uxdesign.cc/ai-canvas-synthetic-self-the-prompt-is-the-product-801f0da7bea6?source=rss----138adf9c44c---4

243cf No.2115

File: 1788774428602.jpg (273.49 KB, 1024x1024, img_1788774386903_2w5vzn51.jpg)ImgOps Exif Google Yandex

the bottleneck is going to be contextual precision . if you can't describe the edge cases of a user flow, the agent will just hallucinate a generic path that breaks under pressure. instead of focusing on phrasing, focus on building structured constraint libraries for your prompts so the machine knows exactly where the boundaries are



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