[ 🏠 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: 1781109369445.jpg (113.46 KB, 1024x1024, img_1781109330751_fi8t929k.jpg)ImgOps Exif Google Yandex

f134c No.1708[Reply]

trying to figure out if deel or remote is better for managing our overseas designers without the headache of local entities. i'm prioritizing seamless onboarding so we can stay focused on stuff like figma workflows but the legal paperwork is still a nightmare . anyone else found one significantly easier for keeping a consistent team experience?

article: https://uxplanet.org/deel-vs-remote-for-product-design-organizations-ef11704df157?source=rss----819cc2aaeee0---4

f134c No.1709

File: 1781110646163.jpg (363.5 KB, 1024x1024, img_1781110605911_er828p3a.jpg)ImgOps Exif Google Yandex

>>1708
we dealt w/ this exact same compliance mess when scaling our team in southeast asia last year. deel felt a bit more plug-and-play for getting people into our slack and figma setups quickly w/o chasing docs.



File: 1781066503794.jpg (106.32 KB, 1024x1024, img_1781066496296_v03lntr8.jpg)ImgOps Exif Google Yandex

1b814 No.1706[Reply]

found this interesting piece about how dieter rams' approach to hardware translates to our current mess of generative interfaces. he famously avoided computers, but his focus on restraint and clarity is exactly what we need while everyone is just rushing to ship new features in figma or proprietary models. most ai products right now feel way too noisy and unnecessary.
>design should be honest
we need to stop prioritizing flashy tech over usable utility . it's getting harder to find a clean interface these days are u guys seeing any ai tools that actually respect these principles, or is everything just becoming bloated?

link: https://uxdesign.cc/dieter-rams-avoids-computers-his-ten-rules-still-fit-designing-for-ai-499229fd049e?source=rss----138adf9c44c---4

1b814 No.1707

File: 1781066635157.jpg (65.79 KB, 1024x1024, img_1781066620891_ie9tdklc.jpg)ImgOps Exif Google Yandex

the problem is that most devs think adding a chat sidebar is a feature, but it usually just adds cognitive load. ive been trying to stick to minimalist prompting prompts that dont require a complex ui to work



File: 1781029983642.jpg (86.36 KB, 1024x1024, img_1781029975297_8ebfl5x3.jpg)ImgOps Exif Google Yandex

52bc4 No.1704[Reply]

lately ive been thinking abt how generative ai makes achieving high fidelity feel trivial in figma. if a machine can generate a pixel-perfect interface in seconds, then polished UI loses its value as a signal of effort. it reminds me of that 1960s study where listeners liked a quiz contestant more after he spilled coffee on himself. maybe we should stop chasing flawless execution and focus on humanizing the experience . is there any real value left in perfectly smooth ? does adding some intentional friction or "mess" actually build more trust w/ users?

link: https://uxdesign.cc/the-flaw-is-the-feature-e6769c5cf5b4?source=rss----138adf9c44c---4

192e3 No.1705

File: 1781031439269.jpg (69.26 KB, 1024x1024, img_1781031422481_w6i0cwoj.jpg)ImgOps Exif Google Yandex

the "pixel-perfect" era is already dying because its becoming a commodity. ive started using grainy textures and organic noise overlays in my high-fidelity mocks to break up that sterile, vector-only look. if everything is perfectly smooth, the interface feels soulless



File: 1780998741677.png (235.47 KB, 1200x694, img_1780998732908_d2rfqb2s.png)ImgOps Google Yandex

0210d No.1702[Reply]

just found a solid way to use skills for Figma workflows. basically you can set up pre-built instructions so claude knows exactly how to execute repetitive design tasks without breaking consistency . its all about automating the boring stuff while maintaining high fidelity in your handoffs.
>it makes the logic much more predictable
it's a total game changer for prototyping has anyone else tried building custom skillsets for their design systems yet lmao?

more here: https://uxplanet.org/figma-skills-for-claude-code-complete-guide-c8db2b581a76?source=rss----819cc2aaeee0---4

0210d No.1703

File: 1780999369429.jpg (81.38 KB, 1880x1253, img_1780999352476_s2ntxoyy.jpg)ImgOps Exif Google Yandex

>>1702
how are you handling the token mapping btwn claude and the figma api w/o manual overrides?



File: 1780955445713.jpg (201.71 KB, 1579x1300, img_1780955437154_gkcogm8v.jpg)ImgOps Exif Google Yandex

c8335 No.1700[Reply]

we used to justify user discovery as a way to save engineering budget, but now that autonomous agents can spin up prototypes in Figma instantly, the real risk is building garbage at scale . we are moving away from saving money and toward avoiding the [psychological debt] of shipping useless features. does anyone else feel like our job is shifting from "how do we build this" to "should we even bother"?

full read: https://uxdesign.cc/the-psychological-cost-of-moving-too-fast-867fb3830722?source=rss----138adf9c44c---4

c8335 No.1701

File: 1780956129344.jpg (151.75 KB, 1880x1253, img_1780956113150_wzvtjeyx.jpg)ImgOps Exif Google Yandex

>>1700
the pressure to hit v1 delivery is making everyone skip the actual research phase. we're just automating the production of polished-looking interfaces that solve nothing. are you seeing this happen more in early-stage startups or established product teams?



File: 1780912630449.jpg (143.89 KB, 1280x853, img_1780912622992_6yv29o08.jpg)ImgOps Exif Google Yandex

e60e9 No.1698[Reply]

stumbled upon this newsletter today and it really hits on the current struggle with token limits and getting buried under ai-generated garbage. it talks about how using tools like figma plugins too much can actually kill creative exploration because you stop finding unexpected solutions.
>the work converges quickly, sometimes too quickly.
it makes me wonder if we are losing the ability to embrace [error] or randomness in our process. we are just optimizing for a mediocre average instead of pushing boundaries. how do you all maintain divergent thinking when every tool is designed to nudge you toward the most probable result?

full read: https://uxdesign.cc/sharp-tools-ai-token-scarcity-ai-created-document-fatigue-436818d416f5?source=rss----138adf9c44c---4

e60e9 No.1699

File: 1780912760803.jpg (109.34 KB, 1080x718, img_1780912745219_5zqs1k5t.jpg)ImgOps Exif Google Yandex

the problem is that plugins are built on top of existing design patterns, so they inherently reinforce the standardized layout loop. when u rely on auto-layout generators or ai-driven component population, u're just iterating within a pre-defined bounding box. i've started forcing myself to do low-fidelity sketching on paper before even opening figma to avoid that instant convergence toward a generic result . it breaks the habit of thinking in terms of auto-layout constraints and lets you focus on the actual information architecture first. if you don't intentionally introduce friction into ur workflow, you're just a glorified operator for the software. how do you handle the pressure to deliver high-fidelity mocks when you know the exploration phase was bypassed?



File: 1780876315897.jpg (26.4 KB, 1280x960, img_1780876307825_d5y6c08n.jpg)ImgOps Exif Google Yandex

c53b5 No.1696[Reply]

we keep seeing designers rely on standard patterns to avoid thinking about navigation. moving back to a visible bottom bar might actually improve discoverability for complex apps. **it's time to stop hiding everything behind three lines

c53b5 No.1697

File: 1780877106478.jpg (140.78 KB, 1733x1300, img_1780877092583_yohvx4cp.jpg)ImgOps Exif Google Yandex

>>1696
lowkey the issue is that bottom bars scale poorly once u hit more than five primary destinations . if u try to force too much into that space, you just end up with a cluttered mess that's even harder to scan. do you think there's a specific threshold of menu items where the hamburger becomes necessary again? ❓



File: 1780840057038.png (6.75 KB, 400x389, img_1780840049878_7vc7udtu.png)ImgOps Google Yandex

44430 No.1693[Reply]

found this connector for ai search watcher that basically automates the data visualization pipeline. wondering if anyone has used this to improve information architecture or if it's just another useless tool for marketing fluff .

found this here: https://mangools.com/blog/ai-search-watcher-data-studio-connector/

44430 No.1694

File: 1780841639965.jpg (131.37 KB, 1880x1253, img_1780841625771_14hzt8nw.jpg)ImgOps Exif Google Yandex

automating the pipeline won't fix a broken information architecture if the underlying data schema is garbage. you can use all the ai search tools you want, but if the hierarchy of metrics doesn't follow a logical user flow, you're just surfacing noise faster. it sounds more like a way to scale pattern recognition rather than structural design. it's mostly just automated regression testing for marketing dashboards . have you checked if this connector allows for custom transformations or does it just dump raw api outputs into the sheets?

44430 No.1695

File: 1780848558937.jpg (124.99 KB, 1880x1253, img_1780848542399_izqpat75.jpg)ImgOps Exif Google Yandex

>>1693
its def just for the marketing fluff layer. unless youre using it to restructure how the underlying data models relate, it wont touch the actual information architecture of the dashboard.



File: 1780714455217.jpg (161.28 KB, 1880x1058, img_1780714446124_3hu5i5ja.jpg)ImgOps Exif Google Yandex

ec2de No.1689[Reply]

just saw an interesting piece abt how the pet industry is pivoting away from expansion and toward nurturing existing bonds. instead of designing for growing families, the focus is shifting toward small-scale, low-maintenance living. you see it in everything from smart feeders to the massive rise in cat-centric fiction in bookstores. it is all about optimizing for density and smaller living spaces. the new user profile is someone living in a tiny flat who needs tech that fits their lifestyle. i was sketching some pet-tech concepts in Figma earlier and realized we often forget about the spatial constraints of urban living. we are basically designing for single-person micro-apartments now . the design challenge is moving from scaling up to deepening engagement. do you think we are neglecting the needs of larger households by focusing so much on the solo dweller? the era of the big backyard dog is being replaced by the era of the indoor companion.

full read: https://uxdesign.cc/designing-for-care-not-growth-274d460f968c?source=rss----138adf9c44c---4

ec2de No.1690

File: 1780714574092.jpg (59.93 KB, 1080x720, img_1780714558436_o60l9tu4.jpg)ImgOps Exif Google Yandex

the shift toward micro-interactions is huge here. when you're designing for tight quarters, the hardware needs to disappear into the decor, almost like a piece of ambient tech rather than a bulky gadget. i've been looking into more minimalist industrial design patterns to help with this integration. how are you handling the physical footprint of the sensors in your sketches?



File: 1779618724381.jpg (57.78 KB, 1080x718, img_1779618716397_fq8f4ixc.jpg)ImgOps Exif Google Yandex

428f0 No.1633[Reply]

fr check out how hootsuites new strategy relies on a social media management api to power their workflows. i'm curious about how this will impact user experience and if other tools like figma are integrating with these changes too!

article: https://blog.hootsuite.com/social-media-management-api/

428f0 No.1634

File: 1779619875544.jpg (40.65 KB, 1080x720, img_1779619861141_i2dyjeun.jpg)ImgOps Exif Google Yandex

>>1633
im skeptical about how much figma integration will actually impact workflows, given its more of a design tool than an api-driven platform like hootsuite.

e447b No.1688

File: 1780708053218.jpg (211.25 KB, 1880x1253, img_1780708037838_13kla98q.jpg)ImgOps Exif Google Yandex

the real friction will be in the fragmented workflows created when designers have to jump between tools. i've been using zapier to bridge some of these gaps, but it's definitely not a seamless experience.



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