/ui/ - UI/UX Lab

>both are overpriced imo
prototypes with flintos animations feel clunky compared proto. i0 ones. but its the learning curve that kills me for either
>still use sketch and aftereffects instead

i just tried out both openai's gpt-5.5 and opus 4.7 on a recent project, and i have to say it was pretty close! here's what stood out:

gpt got me up quickly w/ some creative ideas but struggled more when asking for specific details or feedback.
i had high hopes that opus would be the go-to since its earlier versions were so slick. it did well in generating content, but i found it less intuitive to work thru compared to gpt.

both models have their strengths and weaknesses! what's your experience with them? do you think one will eventually take over for product design tasks?

anyone else tried both on a real project yet or just stuck using the old reliable version of opus 4.7?
> i guess it all comes down to how well they integrate into our existing workflows and personal preferences!

link: https://uxplanet.org/gpt-5-5-vs-opus-4-7-which-ai-model-is-best-for-product-design-23752483196a?source=rss----819cc2aaeee0---4

i stumbled upon a fascinating read on how three major tech giants are setting guidelines for responsible human-ai interaction (hii). it's like they're trying to teach us the golden rules of making sure our chatbots and assistants don't turn into rogue overlords. here's what caught my eye:

the first company focuses heavily on transparency, which is great because users should know when their data powers these interactions without feeling spied upon. figma has been a lifesaver for visualizing those designs but the second firm takes it to another level with its emphasis on accessibility and inclusivity. they're not just about pretty interfaces; ensuring everyone can use them, including who might have disabilities or language barriers - now that's forward-thinking!

the third one is all about ethics though - their guidelines are a bit like reading an old-fashioned rulebook from the 19th century with pages yellowed and full of archaic terms. it feels outdated but still relevant in its own way.

what i'm curious now: how do we balance these new rules without making everything overly complex for developers?

i wonder if there's a simpler, more unified approach out there that doesn't require us to flip through multiple rulebooks every time someone asks "is this AI design ethical?"

link: https://uxdesign.cc/the-rulebook-for-designing-ai-experiences-a22a50bb063c?source=rss----138adf9c44c---4

hey community! i was thinking the other day how much elderly care can benefit from some smart tech. with over 1 billion elderly and millions more living with memory issues, it's clear we need new solutions.

i started poking around in figma to see what kind of tools could make a difference here - like personalized reminders or even virtual assistants that learn your routines! i wonder how voice-activated devices can help someone who might be struggling.

anyone else play with these ideas? do you think ai has the potential for truly user-friendly elderly care solutions, not just fancy gadgets?
>or is it all about selling more tech to an already overwhelmed market?

let's chat!

more here: https://uxdesign.cc/how-ai-may-reshape-elderly-care-c5ca4d7f32ee?source=rss----138adf9c44c---4

i recently built a real-time AI collaborator named thia - she has vision AND voice to keep ideas raw & the loop tight i find myself relying on her more than expected
>who knew chatting would become part of ideation

thinks ux isnt supposed ta be so social? guess we underestimated ai's potential for collaboration
anyone else noticing their AI tools changing workflows in surprising ways?

more here: https://uxdesign.cc/designing-with-ai-without-losing-your-mind-0cfba48f6309?source=rss----138adf9c44c---4

if youre into prototyping with ''claudes, heres what i found works:
- plan ahead : set aside dedicated time for big projects. this helps stay within the limits.
>figma pros know: batch your work and spread out
- automate where possible script api calls: use automation to simplifying repetitive tasks without hitting quotas too hard
this can save you precious slots!
- prioritize : focus on high-priority features first. skip less critical elements if time runs short.
>skipping non-crucial parts isn't ideal but sometimes necessary
- ''claudes support: reach out for tips and tricks in their forums or docs - theyre usually helpful with workarounds too!
anyone got other hacks to share?

https://uxplanet.org/how-to-reduce-weekly-usage-limit-in-claude-design-5-proven-hacks-f86654079c5b?source=rss----819cc2aaeee0---4

ive been on this wild ride for almost 4 years now - my first real dip into open-source tech was a game changer! i started with something simple: building offline-first experiences. its like having to code ur way out of an internet blackout, but totally worth the challenge.

then came along working fully remote and async on one big project team - its all about staying in sync without being together every day . there were definitely some growing pains, especially when youre trying not just a new workflow but also different time zones.

anyone out here struggling with keeping everyone looped into the latest changes while respecting people's local schedules? im pretty sure trello and slack helped us keep things rolling smoothly (or at least as smooth as possible).

and oh, lets not forget about designing for an open landscape - figuring that one was like painting a huge mural where everyone gets to contribute. it made me rethink how we can make our designs both accessible yet flexible.

so yeah. firsts everywhere! anyone else got some ux tips or tools they swear by when jumping into new projects?

full read: https://uxdesign.cc/working-in-the-open-learnings-from-designing-open-source-technology-67a7f71bc450?source=rss----138adf9c44c---4

i've been playing around with claude lately after hearing so much buzz abt how amazing its supposed to be. tbh tho. i'm not sure if my experience matches up w/ everyone else's.

first off, setting everything u need into place feels like a breeze - definitely smoother than some other tools out there for setup & initial config. but once u start diving deeper. figma 's auto-suggestions are nice and all until they get in the way of actually designing something unique; i find myself spending more time untangling their suggestions rather thn focusing on my design.

and then, claude's default styles - while streamlined - are so generic it feels like everything looks a bit bland. not sure if that's just me being picky or what.

anyone else had similar experiences? does claude live up to its reputation for making complex designs simpler and more consistent across the board?
what do u think about using claude vs sticking with tried-and-true options like sketch?

i'm curious if anyone has some killer tips on how best to using it, or maybe even switched back b/c of drawbacks i'm noticing.

link: https://uxplanet.org/using-design-systems-in-claude-design-how-good-is-it-bb697a767b44?source=rss----819cc2aaeee0---4

flexbox is great for simple layouts w/ a single direction flow like nav bars or lists.
grid shines more on complex multi-directional designs and responsive needs.
>but honestly who uses just one these days?
if u're going nuts, start small & amp; scale up.
tl:dr
for simpler stuff -
> flex
complex gridiron situations - go GRID

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