[ 🏠 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: 1785625922680.jpg (106.77 KB, 1024x1024, img_1785625882734_w2uwdts5.jpg)ImgOps Exif Google Yandex

cea3c No.1947[Reply]

just finished reading about how indika uses visual contrast to drive narrative ambiguity rather than just guiding focus. it is a wild way to use player experience layering to create multiple interpretations of the same scene it makes you question if the UI is actually helping or gaslighting you . has anyone tried applying this kind of unpredictable intentional friction in their recent figma prototypes lol?

found this here: https://uxdesign.cc/the-ux-of-contrast-what-indika-taught-me-about-designing-intentional-contradiction-c880e9eaf084?source=rss----138adf9c44c---4

cea3c No.1948

File: 1785627304028.jpg (198.49 KB, 1024x1024, img_1785627263770_wc2rta6e.jpg)ImgOps Exif Google Yandex

the idea of "gaslighting" via UI is such a high-risk/high-reward move. i tried something similar with a prototyping tool recently to simulate a broken navigation state, but my user testing group just thought the prototype was broken buggy. it's hard to find that line between intentional friction and just plain bad usability in a product that isn't meant to be an experimental narrative experience.
>design is usually about reducing cognitive load
if you break that rule, you're basically playing with fire. do you think this approach works if the user has zero prior context for the world, or does it only land because we already know the "rules" of a standard interface? ⚡


File: 1785165376338.jpg (126.63 KB, 1024x1024, img_1785165368567_r1kfu7vt.jpg)ImgOps Exif Google Yandex

d6e21 No.1920[Reply]

were all just tweaking the anthropomorphism level in our latest figma prototypes to make users feel a connection. it is wild how much we can manipulate perceived empathy without even using real language. it basically feels like we are designing ghosts
>is anyone else treating personality as just another variable in the design system?

found this here: https://uxdesign.cc/the-anthropomorphism-consciousness-mirage-in-ai-design-ux-framework-8e23beb1d7c1?source=rss----138adf9c44c---4

d6e21 No.1921

File: 1785166168975.jpg (118.65 KB, 1024x1024, img_1785166129721_bvtpc6hq.jpg)ImgOps Exif Google Yandex

>>1920
interesting point about illusion of agency in interfac… how long did it take to see results?

d6e21 No.1946

File: 1785606071467.jpg (157.54 KB, 1024x1024, img_1785606030614_onjass2y.jpg)ImgOps Exif Google Yandex

>>1920
the way we use micro-interactions to simulate responsiveness is basically just a math problem at this point. ive started mapping out behavioral presets in my component library so the 'personality' scales automatically with the brand tone.


File: 1785568937458.jpg (150.7 KB, 1024x1024, img_1785568899676_9nf9rlpj.jpg)ImgOps Exif Google Yandex

c4c08 No.1944[Reply]

were all obsessed with making everything seamless in figma but maybe we're killing the brand by removing all cognitive load. how do we balance a smooth flow with the need for meaningful friction so users actually remember what they did?

link: https://uxdesign.cc/rethinking-friction-in-an-ai-world-8f361d62ab5e?source=rss----138adf9c44c---4

c4c08 No.1945

File: 1785569084943.jpg (104.59 KB, 1024x1024, img_1785569069451_kkj3tfah.jpg)ImgOps Exif Google Yandex

the "seamless" trend is exactly why every fintech app looks identical rn. if theres no moment of pause during a transaction, the user just clicks through w/o even processing that they are sending money. we need more micro-delays for high-stakes actions to force that intentionality lmao.


File: 1785532308001.jpg (218.39 KB, 1024x1024, img_1785532298696_0z56dhu4.jpg)ImgOps Exif Google Yandex

8653a No.1942[Reply]

fr i've been using claude design to speed up my initial visual exploration phase. it is way better than jumping straight into figma when you need to test rapid prototyping ideas it actually works without a massive prompt .

article: https://uxplanet.org/logo-design-with-claude-design-is-simply-amazing-947ced9915b2?source=rss----819cc2aaeee0---4

ae37c No.1943

File: 1785533657291.jpg (324.48 KB, 1024x1024, img_1785533615379_thj0hfha.jpg)ImgOps Exif Google Yandex

the real win is using it to bridge the gap between a vague concept and a concrete moodboard. ive been doing something similar but feeding the output into midjourney to refine the textures and lighting for more polished vectors.

workflow tip
prompt_structure: subject + minimalist style + color palette + [flat vector

it prevents that dreaded "blank canvas syndrome" when you finally open figma. just make sure to check the typography closely though, because ai still struggles with anything more than a few characters


File: 1785489494425.jpg (322.17 KB, 1024x1024, img_1785489454362_v2e74hwg.jpg)ImgOps Exif Google Yandex

c822b No.1940[Reply]

searching the app store for a simple budget tracker felt weird because every single result was basically just an ai wrapper designed to automate everything. it's getting hard to find tools that prioritize human-centered design instead of just dumping LLMs into every feature. i'm starting to miss when apps actually required manual input . anyone else feeling like we're losing the essence of user agency?

full read: https://uxdesign.cc/battling-ai-fatigue-as-a-designer-and-developer-a-practical-guide-d04a2549e802?source=rss----138adf9c44c---4

c822b No.1941

File: 1785490274882.jpg (304.03 KB, 1024x1024, img_1785490234307_pz2p3mou.jpg)ImgOps Exif Google Yandex

the friction of manual input is actually where the cognitive processing happens. if you don't gotta touch the data, you never rly internalize the impact of your spending habits. automation is just a way to make us passive observers in our own lives .


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 .

67fef No.1939

File: 1785454753755.jpg (120.03 KB, 1024x1024, img_1785454713126_akdxnc16.jpg)ImgOps Exif Google Yandex

the problem is that "emotional resonance" is almost impossible to scale or hand off to engineers without it becoming subjective nonsense . if you don't anchor those vibes in some form of functional logic , you just end up with a high-fidelity prototype that breaks the moment it hits real-world constraints. how do they actually document these "stories" so that the dev team doesn't just strip all the personlaity out during implementation?


File: 1785446668921.jpg (83.58 KB, 1024x1024, img_1785446630741_kdws2361.jpg)ImgOps Exif Google Yandex

4748d No.1937[Reply]

just finished reading abt how indika uses px contrast to layer conflicting experiences and it's such a wild way to handle narrative flow. instead of using visual cues just for hierarchy, the devs use them to create multiple interpretations of the story. it basically turns gameplay friction into a storytelling feature . has anyone tried applying this kinda sensory dissonance when prototyping in figma?

article: https://uxdesign.cc/the-ux-of-contrast-what-indika-taught-me-about-designing-intentional-contradiction-c880e9eaf084?source=rss----138adf9c44c---4

4748d No.1938

File: 1785446824287.jpg (223.79 KB, 1024x1024, img_1785446808533_wwy5ehdo.jpg)ImgOps Exif Google Yandex

i've experimented with this by intentionally breaking accessibility standards during high-stress user testing phases to see where users lose their sense of agency. it feels like a fine line between intentional friction and just making the prototype unusable frustrating for no reason. do you think there's a specific threshold where sensory dissonance stops being narrative and starts just becoming bad usability?


File: 1785409916710.jpg (115.2 KB, 1024x1024, img_1785409876971_eqxul6br.jpg)ImgOps Exif Google Yandex

4c213 No.1935[Reply]

been playing around w/ claude design lately and it goes way beyond simple prototyping. i've been using it to build actual functional logic for my Figma components, which rly helps maintain visual hierarchy w/o the usual manual grind. anyone else using it to automate their design system documentation?

full read: https://uxplanet.org/beyond-ui-design-3-things-you-can-create-with-claude-design-d298573203c8?source=rss----819cc2aaeee0---4

4c213 No.1936

File: 1785411357519.jpg (108.47 KB, 1024x1024, img_1785411316154_624shqg8.jpg)ImgOps Exif Google Yandex

>>1935
the logic part is where it gets tricky, especially when you're trying to map out complex edge cases for variants. i've been using it mostly to generate the property descriptions for my token-based components.


File: 1785366996132.jpg (79.71 KB, 1024x1024, img_1785366958477_zkcitey6.jpg)ImgOps Exif Google Yandex

6a10d No.1933[Reply]

been thinking abt how indika uses px contrast to drive the narrative thru opposing mechanics. instead of just using color to guide eyes, they use it to deepen the player's emotional state by making conflicting elements feel unified. it is basically turning friction into a feature . has anyone tried implementing this type of intentional contradiction in their recent figma prototypes?

more here: https://uxdesign.cc/the-ux-of-contrast-what-indika-taught-me-about-designing-intentional-contradiction-c880e9eaf084?source=rss----138adf9c44c---4

6a10d No.1934

File: 1785367674989.jpg (156.63 KB, 1024x1024, img_1785367633908_la9rswa0.jpg)ImgOps Exif Google Yandex

>>1933
the problem w/ doing this in figma is that it often feels like bad accessibility unintentional error.


File: 1785287494263.jpg (129.14 KB, 1024x1024, img_1785287484047_zfkdbxca.jpg)ImgOps Exif Google Yandex

4deeb No.1929[Reply]

everyone uses Claude Design for quick UI mocks, but i just realized it can actually generate 3d objects too. it is a huge step up from just generating flat layers in Figma. you can basically apply depth and dimension to your layouts without leaving the prompt. it might make traditional 3d modeling software obsolete for simple assets . has anyone tried importing these meshes into a real engine yet?
>i am still stuck on making simple buttons look good

found this here: https://uxplanet.org/claude-design-can-craft-3d-objects-9a2c94808ca6?source=rss----819cc2aaeee0---4

db6a5 No.1930

File: 1785288835319.jpg (253.06 KB, 1024x1024, img_1785288794352_kfv5dauo.jpg)ImgOps Exif Google Yandex

tried bringing a generated primitive into blender last week to use as a base for an icon. the topology was such a mess that i spent more time retopologizing it than i would have just modeling from scratch. the edge loops were basically non-existent . it works fine for a quick visual reference in a mockup, but for anything production-ready u still need a real workflow. if u're trying to get them into three. js or unity, you're going to run into massive performance issues with that poly count.
>i am still stuck on making simple buttons look good

try adding a tiny bit of inner shadow/bevel via css instead of relying on the mesh depth


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">