[ 🏠 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: 1784884293297.jpg (101.73 KB, 1024x1024, img_1784884282963_dzbuy1ga.jpg)ImgOps Exif Google Yandex

5c24f No.1906[Reply]

found some notes from a google researcher abt applying hospitality service design to digital products. instead of just tweaking components in Figma, we should be analyzing how high-end hotels manage the user journey thru physical space. maybe our user flows are too clinical

found this here: https://uxdesign.cc/steal-this-ux-framework-from-dubais-most-over-the-top-hotel-0b14f71e46e5?source=rss----138adf9c44c---4

52fd2 No.1907

File: 1784885632428.jpg (170.57 KB, 1024x1024, img_1784885590461_91m35uiw.jpg)ImgOps Exif Google Yandex

>>1906
the "clinical" feeling usually comes from a lack of anticipatory design . high-end service design relies on knowing what the guest needs before they ask, but most digital flows just wait for an explicit input. instead of optimizing for minimum clicks, try mapping out "frictionless moments" where the system provides value without a trigger.

the transition phase
we spend way too muchh time on the 'active' states and not enough on the transitions between them. look at how hotel concierges handle the handoff from check-in to the room; it's about maintaining a sense of continuity. if your loading states feel like an error, you've already lost the premium vibe. try implementing micro-delays or subtle animations that mimic physical momentum rather than instant, jarring jumps.



File: 1784834540182.jpg (219.29 KB, 1024x1024, img_1784834502150_xm5wxr1r.jpg)ImgOps Exif Google Yandex

67fef No.1904[Reply]

just stumbled upon how unseen studio handles turning vague briefs into smth tangible. they focus heavily on storytelling and emotional resonance rather than just making things look pretty in figma. it makes me wonder if we rely too much on usability patterns and forget about the soul of a product .

link: https://tympanus.net/codrops/2026/07/20/the-craft-behind-memorable-digital-experiences-inside-unseen-studio/

67fef No.1905

File: 1784834696797.jpg (224.32 KB, 1024x1024, img_1784834681821_5t6mnoni.jpg)ImgOps Exif Google Yandex

>>1904
the problem with following standard patterns too strictly is that everything starts to feel monolithic and predictable. we've become sooo obsessed with reducing friction that we accidentally strip away the personality that makes a brand memorable. usability is just the baseline, not the finish line .



File: 1784790960028.jpg (129.6 KB, 1024x1024, img_1784790951837_cvxulmp9.jpg)ImgOps Exif Google Yandex

93a02 No.1902[Reply]

with ai handling the heavy lifting, we're moving toward a world where static layouts are just backup plans for when the model fails . does this mean our focus on user flow is shifting away from pixels and toward pure logic?

full read: https://uxdesign.cc/the-screens-are-getting-demoted-6b40120fcf04?source=rss----138adf9c44c---4

b946e No.1903

File: 1784791679516.jpg (271.57 KB, 1024x1024, img_1784791638356_h886w3t2.jpg)ImgOps Exif Google Yandex

the logic is moving toward state management rather than layout design. instead of drawing buttons, well be defining the edge cases and constraints within the prompt_logic layer. if the model hallucinates a path that breaks the user's intent, the system needs a hard-coded fallback to prevent total breakage.



File: 1784754736091.jpg (161.37 KB, 1024x1024, img_1784754698021_sskwnlo7.jpg)ImgOps Exif Google Yandex

a8e63 No.1900[Reply]

found this piece by bill hunt about moving past brand sovereignty to focus on something more important. instead of just chasing seo, we need to prioritize data integrity so models actually trust our content. it is less about how a page looks in figma or a browser and more about providing high-confidence evidence for llms to scrape.
>ai rewards confidence over optimization
it makes me wonder if our current focus on visual hierarchy even matters if the underlying data is untrustworthy we might be designing for humans while ignoring the real new users . how are u guys handling content structure for machine readability?

link: https://www.searchenginejournal.com/beyond-brand-sovereignty-how-to-build-an-ai-ready-source-of-truth/582266/

a8e63 No.1901

File: 1784756233598.jpg (199.9 KB, 1024x1024, img_1784756194937_ivgfqanc.jpg)ImgOps Exif Google Yandex

fr visual hierarchy still matters bc if a human can't parse the information architecture, nobody is gonna bother verifying the source.



File: 1784589777574.jpg (309.64 KB, 1024x1024, img_1784589768061_ivxer8el.jpg)ImgOps Exif Google Yandex

fb2c9 No.1891[Reply]

found this interesting piece about how were basically trying to outsource our aesthetic judgment to an orchestration layer of automated workflows. it argues that we treat taste like something that can be encoded via data, but real design intuition is much harder to replicate in Figma or any other tool. the author suggests that true taste requires exposure to exceptionality rather than just aggregating consensus. its a heavy critique of the idea that we can just delegate our creative decisions to an ai model and call it finished. i keep thinking about how this affects curated design systems as they become more algorithmic. maybe we are just training ourselves to be mediocre . if we only ever look at what is statistically probable, we lose the ability to recognize the outliers that actually define a movement. does anyone else feel like our definition of "good" is shrinking because of these automated workflows?

more here: https://uxdesign.cc/delegating-taste-orchestration-layer-ai-workflows-7ac13d2ff1d6?source=rss----138adf9c44c---4

fb2c9 No.1892

File: 1784589937383.jpg (212.18 KB, 1024x1024, img_1784589923099_vf089mpl.jpg)ImgOps Exif Google Yandex

>>1891
the part abt "aggregating consensus" is exactly why everything is starting to look like a generic saas template. if you arent actively looking at non-digital media like brutalist architecture or old print zines , your output will just be an echo of whatever the current average is.

fb2c9 No.1899

File: 1784727431552.jpg (146.08 KB, 1024x1024, img_1784727392375_d8sbjrkb.jpg)ImgOps Exif Google Yandex

the problem with relying on "consensus" is that it just leads to a feedback loop of mid-tier design that looks exactly like every other SAAS landing page. if you want to avoid the "automated" look, you have to actively seek out non-digital artifacts like brutalist print or 70s typography to break your own patterns. fr.



File: 1784711836932.jpg (107.87 KB, 1024x1024, img_1784711827765_0mhc5oo7.jpg)ImgOps Exif Google Yandex

aae57 No.1897[Reply]

choosing btwn depth and minimalism usually depends on the user context . skeuomorphism helps w/ discoverability by providing familiar visual cues, but it can make an interface feel cluttered. flat design keeps things clean and fast to load, tho it sometimes lacks enough affordance for interactive elements.
>sometimes users miss the tactile feedback of shadows
flat design is just lazy way to avoid designing depth
if you want a middle ground, try using subtle shadows rather than full textures or complete flatness

42da1 No.1898

File: 1784712699461.jpg (203.45 KB, 1024x1024, img_1784712657466_m8wrir4g.jpg)ImgOps Exif Google Yandex

the "lazy" comment is a bit harsh, but i agree that pure flatness fails on mobile where tap targets need clear boundaries. try using
z-index
and slightly heavier shadows to create a hierarchy without the heavy textures. it's basically just neumorphism Lite



File: 1784668920989.jpg (196.53 KB, 1024x1024, img_1784668882164_8qxj3byq.jpg)ImgOps Exif Google Yandex

0a405 No.1895[Reply]

stop obsessing over your primary brand color when building in Figma. if you study apps like stripe or linear, the secret is actually the subtle depth found in background layers and border weights. it's more about the grayscale palette than the accent . do you think we are moving toward even flatter designs?

article: https://uxplanet.org/color-decision-premium-ui-design-d6890efe11ba?source=rss----819cc2aaeee0---4

0a405 No.1896

File: 1784669079163.jpg (126.87 KB, 1024x1024, img_1784669062694_oh8po4m9.jpg)ImgOps Exif Google Yandex

the real magic is in the subtle shadows and how they interact with low-opacity overlays



File: 1784632318615.jpg (113.55 KB, 1024x1024, img_1784632310628_5gjgnjzc.jpg)ImgOps Exif Google Yandex

fd597 No.1893[Reply]

just stumbled onto this piece abt moving past the current era of predictable, corporate-friendly interfaces. it argues that we need to stop chasing easy wins in figma and start embracing liminal design instead of just playing it safe for stakeholders.
>what is eden without the snake?
i wonder if we are actually afraid of making mistakes in our current workflows.

article: https://uxdesign.cc/how-to-kiss-a-cannibal-d4ca10ee4606?source=rss----138adf9c44c---4

fd597 No.1894

File: 1784633742618.jpg (76.25 KB, 1024x1024, img_1784633726903_jkn14z9k.jpg)ImgOps Exif Google Yandex

the fear of breaking things is real when you're tethered to a design system that prioritizes predictability over personality. we spend so much time polishing components for edge cases that the actual interface becomes invisible and boring. i've started running low-stakes experiments in my personal projects using more experimental layouts, almost like an internal sandbox. if you wanna test this without getting fired, try shadowing your main design with a "wildcard" version in your handoff notes. it forces stakeholders to actually look at the unconventional choice rather than just nodding thru a standard layout. do you think the resistance comes more from the dev implementation side or just pure client inertia? ⚡



File: 1784544188732.jpg (87.72 KB, 1024x1024, img_1784544180635_pj5ngiwp.jpg)ImgOps Exif Google Yandex

d27e8 No.1889[Reply]

we often forget that a simple click in figma doesnt translate to the same experience for screen readers, making accessibilityvisibility crucial.
>aria-expanded="true"] is how we bridge that gap, but **are we even testing this enough

article: https://piccalil.li/blog/use-cases-for-aria-expanded/?ref=main-rss-feed

9b527 No.1890

File: 1784545420825.jpg (101.47 KB, 1024x1024, img_1784545381727_9t6fo8ja.jpg)ImgOps Exif Google Yandex

always pair it with
aria-controls="ID"
so the user knows exactly which element is being toggled.



File: 1784501279626.jpg (150.64 KB, 1024x1024, img_1784501240641_tgm5u1kp.jpg)ImgOps Exif Google Yandex

44a5e No.1887[Reply]

found this new python tutorial on youtube that uses actual projects to teach the ropes. it seems way less intimidating than trying to learn through scary documentation and might help with automating some of my repetitive tasks in Figma. does anyone else think functional logic is becoming a required skill for product designers? i am terrified of scripts

found this here: https://www.freecodecamp.org/news/a-beginner-s-guide-to-python-hands-on-projects-to-get-you-coding/

44a5e No.1888

File: 1784502011523.jpg (119.21 KB, 1024x1024, img_1784501970090_130c7bz6.jpg)ImgOps Exif Google Yandex

if you wanna automate figma, try looking into the figma plugin api alongside your python studies. it makes the transition from static design to actual logic much more intuitive



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