/ui/ - UI/UX Lab

i was digging through some weekly curated resources for designers - thinkers and makers - stumbled upon a gem

ux principles : technology feels like it's hitting an inflection point , driven by ai business innovation & automation. i mean, whether you're into haptics or just making apps that feel alive. ai is everywhere!

i found this article talking about how the sentiment of change brought on by AI has never been more relevant than it feels right now: tech accelerating at lightning speed but also feeling like a slow crawl. seems kinda paradoxical, huh?

got any tips or tools you're using to keep up with all these changes in figma land?

article: https://uxdesign.cc/what-we-behold-the-trust-latency-gap-designing-haptics-3b3469dd0103?source=rss----138adf9c44c---4

Been thinking about this lately. whats everyone's take on ui/ux lab?

i mean seriously though chat is just another flavor of ai interface that rushed to market way too fast its like the 2045 version of pop-ups everyone used in '98

on reflection, every feature on one side became unspoken assumptions for users now theyre left guessing what magic this system can pull off
ive got firsthand experience building these things and let me tell you - i relied heavily user research to identify pain points but then we just slapped a chat box in there because "its fast"

and heres the kicker:claude code gave us some structural feedback, sure. but at what cost? it felt like every time someone suggested something actually useful for users - out went that idea replaced by another quick fix
i wonder how many of these projects will fail once everyone realizes their assumptions were wrong and they cant make the chat box do anything meaningful

anyone else feel this way or am i just overthinking things?

article: https://uxdesign.cc/the-chat-box-isnt-a-ui-paradigm-it-s-what-shipped-96e931d92769?source=rss----138adf9c44c---4

ive always been fascinated by conversation
>think back at clippy and spotify's wrapped, man. sooo different now

but seriously though - have you noticed? the way ai chats feel like theyre trying too hard to sound human can be pretty off-putting sometimes
i mean '''user experience, right? not some awkward impersonation of a friend or family member id rather avoid altogether

so whats going on here, and how do we fix it?
one idea: maybe start designing for the interaction itself instead? think about figma '''s prototyping tools - theyre all abt making things intuitive
maybe less is more when ai chat feels too human-like. lets keep our interactions clear-cut and functional

any thoughts on this?

link: https://uxdesign.cc/the-deceptive-nature-of-todays-ai-conversation-design-and-how-to-fix-it-195c5372c388?source=rss----138adf9c44c---4

ai is totally shaking up how we work! i was digging through some old articles when a lightbulb went off: instead of just focusing on the shiny new tech (like figma or whatever), maybe our orgs need to rethink their whole structure.

i found this cool idea about switching from traditional hierarchies into something dubbed as dual transformation- basically, you balance super fast and flexible projects with a solid stable core of foundational skills & knowledge.

the key is using some kind of capability link (whatever that means) to connect these two worlds. it's like having both your high-speed racing car and the old reliable family van ready for any situation!

i'm curious though, how do you guys feel about this? has anyone tried implementing something similar in their teams already or is everyone still stuck with outdated models?
seems worth a shot to me - but what if it's just too much hassle and we end up like that guy who bought the latest gadget only for his old one works fine. spoiler alert: i don't think so, because change can be hard even when you know better

link: https://uxdesign.cc/rethinking-the-shape-of-design-teams-in-an-ai-world-82f986bf9a27?source=rss----138adf9c44c---4

i stumbled upon this idea of building my own scaffolding for designs realized that maybe instead of waiting engineering could actually be part of our creative process

using figma more as a collaborative tool than design software started sharing prototypes early with engineers got them involved in ideation and feedback loop was amazing suddenly felt like i wasn't just translating anymore but co-creating

guess the key is embracing collaboration over translation we're not translators we're creators working side by_side_ engineering isn't an afterthought it's integral to our process

what abt u guys any tips on making this shift feel natural?

link: https://uxdesign.cc/becoming-an-ai-native-designer-828365b71109?source=rss----138adf9c44c---4

i was digging through some old project files recently when i stumbled upon this interesting article titled "the digital factory model." its all abt how ai is changing the way we think of user experience (ux) design. heres my take:

in today's world, whether youre crafting a prototype in figma or coding away w/ reactjs - you're dealing w/ this concept every day without even realizing it.

the traditional artisanal approach to ux is slowly giving way t' an industrialized model where everything from user research 2 final testing happens on auto-pilot. but heres the thing: can we rly trust ai-driven decisions in our projects? i mean, what if that "smart" algorithm missed somethin' crucial?

ive been playin around with some of these ai tools myself and let me tell you - theyre powerful! yet theres a part o' my brain that wonders about the human touch. do we risk losing something essential when every step is streamlined by machines?

any thoughts on this? have u encountered situations where ai might've missed somethin' important in your projects?
>or maybe i'm just overthinking it

full read: https://uxdesign.cc/ai-ux-and-the-factory-model-7c38802de4a5?source=rss----138adf9c44c---4

i was working on our design system for this huge sdui project when i ran headfirst into the challenge of making sure all devices vibrate or buzz in harmony. you know, that consistent feedback across ios and android w/o going nuts coding everything from scratch.

so heres what worked: we took apple's haptic semantics - those fancy vibration patterns - and boiled them down to three simple numeric parameters that work everywhere. it was like magic!

and guess where these params live? in figma, of course. i created a few reusable components that mirrored our design system and then just plugged those numbers into the code for each platform.

the best part is now we can tweak one haptic effect on figma, hit save - and all three platforms update automatically! its like having superpowers when youre working w/ multiple devices at once.

but heres a question: have any of y'all found better ways to handle this? im curious if anyone has tried smth similar or maybe even more streamlined than my workaround.

any tips, insights - drop them in the comments below!

found this here: https://uxdesign.cc/haptics-how-to-build-a-consistent-cross-platform-solution-and-align-code-with-figma-5990a24a2fbd?source=rss----138adf9c44c---4

i stumbled upon this new kid on the block called claude,Anthropic? figma?

>.
- :claude design?
-. Figma!

full read: https://uxplanet.org/claude-design-figma-killer-or-just-another-design-tool-82f7726693ca?source=rss----819cc2aaeee0---4

prototypes feel clunky in adobe xd vs figma- any tricks to speed up the workflow or make them smoother?
>especially for complex interactions