R: 0 / I: 0 teleport slide around while the assets are fetching. Definitely use this for your product grids or any card component where you know the height ahead of time.
It makes a huge difference for the perceived stability of the page. It's much cleaner than calculating percentages manually.
CSS aspect ratio for preventing layout shift
Spent all Tuesday fixing those annoying jumps when images load in our new dashboard. I stopped using padding hacks and just used the aspect-ratio property instead. It keeps the container size locked so the content doesn't.card-image {width: 100%;aspect-ratio: 16 / 9;object-fit: cover;}It makes a huge difference for the perceived stability of the page. It's much cleaner than calculating percentages manually.
R: 3 / I: 1
found this here: https://uxdesign.cc/five-eras-of-ux-design-and-the-lessons-to-keep-in-the-ai-era-d76a548747a9?source=rss----138adf9c44c---4
evolution of ux through five eras
just stumbled onto this breakdown of how human factors predates the modern era and why we shouldn't ditch the old school stuff while using ai-assisted workflows. it is wild how much the foundation remains unchanged despite all the new tools . do you think we are actually entering a new era or just iterating on the same old usability principles?found this here: https://uxdesign.cc/five-eras-of-ux-design-and-the-lessons-to-keep-in-the-ai-era-d76a548747a9?source=rss----138adf9c44c---4
R: 0 / I: 0
infinite scroll is just lazy loading for people who hate menus
i'm tired of seeing devs use infinite scroll because they can't be bothered to design a proper pagination or a simple "load more" button. it's basically an accessibility disaster and makes finding anything you actually clicked on impossible once you've moved past the fold. does anyone actually prefer scrolling forever over just clicking a page number?
R: 2 / I: 0
https://blog.prototypr.io/i-tested-5-ai-tools-on-10-real-ui-design-prompts-heres-what-actually-works-in-2025-54e0e7358751?source=rss----eb297ea1161a---4
stitch is still basically useless for anything complex
saw some tests running stitch through ten different prompts and it's honestly a mess compared to claude. most of the results look like generic garbage you'd see on a template site from 2015. i don't see how anyone's actually using these outputs without spending hours fixing the layers manually. has anyone actually managed to get a clean component library out of any of these yet?https://blog.prototypr.io/i-tested-5-ai-tools-on-10-real-ui-design-prompts-heres-what-actually-works-in-2025-54e0e7358751?source=rss----eb297ea1161a---4
R: 1 / I: 0
full read: https://www.infoq.com/news/2026/09/meta-astryx-design-system/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
meta's astryx looks like a maintenance nightmare
been looking at this astryx thing meta just dropped and i'm not so sure. it's built on react 19 and stylex which is fine i guess, but the whole "swizzle" command for ejecting components sounds like a recipe for disaster. sure, you get the full source code, but then you're stuck maintaining all that internal logic yourself when things break. plus they're pushing this idea of it being agent-ready with an mcp endpoint. i don't really care if an ai can navigate my design tokens better if the underlying css is still a mess of atomic classes. using xstyle for overrides seems okay enough, but having to deal with pre-compiled files alongside tailwind is going to get confusing fast. it's basically just another way to bloat the repo with stuff we didn't ask for. it's just meta being meta. honestly, i don't see how anyone manages 150+ components without losing their mind. do you think anyone is actually going to use the cli for anything other than hype?full read: https://www.infoq.com/news/2026/09/meta-astryx-design-system/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 0 / I: 0
found this here: https://uxplanet.org/claude-design-vs-figma-ai-i-designed-the-same-web-page-with-both-bf2a3712f980?source=rss----819cc2aaeee0---4
claude design vs figma ai is basically the same thing now
another day of tools doing the exact same thing. claude design just hands off to claude code for implementation while figma stays in its own playground. it's all just prompt-to-design nonsense at this point. ime pretty sure we're just moving from manual pixels to managing prompts.found this here: https://uxplanet.org/claude-design-vs-figma-ai-i-designed-the-same-web-page-with-both-bf2a3712f980?source=rss----819cc2aaeee0---4
R: 1 / I: 0
full read: https://uxdesign.cc/the-ux-double-diamond-is-dead-and-in-ai-only-one-survives-for-software-heres-how-to-adapt-f63b57c524ed?source=rss----138adf9c44c---4
double diamond is basically obsolete now
I was reading about how the whole two-stage process was built for things like architecture or urban planning where you can't just undo a mistake. Since a working prototype only takes an afternoon now, the old way of spending so much time on the problem phase feels totally out of sync with how we actually build software. It is wild to think that the entire methodology was designed for when building was expensive and irreversible.full read: https://uxdesign.cc/the-ux-double-diamond-is-dead-and-in-ai-only-one-survives-for-software-heres-how-to-adapt-f63b57c524ed?source=rss----138adf9c44c---4
R: 3 / I: 3 usability accessibility gaps?
found this here: https://uxplanet.org/design-critique-with-claude-code-7628e74f95a1?source=rss----819cc2aaeee0---4
using claude code for design reviews
been using claude code to audit my latest figma handoffs and it's actually great at spotting breaks in visual hierarchy it found a button color issue i missed . anyone else using it to check forfound this here: https://uxplanet.org/design-critique-with-claude-code-7628e74f95a1?source=rss----819cc2aaeee0---4
R: 3 / I: 2
>accessibility is a feature, not a final polish step. building this way makes the transition to development much smoother for everyone involved.
stop checking accessibility only at the end of your sprint
designing with a focus on color contrast from the start prevents massive rework during handoff. it is much easier to adjust your primary palette early than to rewrite entire component libraries later. try using a plugin to check for WCAG compliance while you are still sketching your initial layouts. if you wait until the high-fidelity stage, you might find that your favorite brand colors are spoilercompletely unusable for text]. focus on establishing an accessible foundation by selecting accessible neutrals and primary tones first. this approach ensures your interface is inherently usable without needing a total overhaul.>accessibility is a feature, not a final polish step. building this way makes the transition to development much smoother for everyone involved.
R: 3 / I: 2
more here: https://uxdesign.cc/persistent-lessons-in-human-centered-automation-45b53412e6a5?source=rss----138adf9c44c---4
old school automation lessons
found this deep dive on how 1980s copier studies actually apply to today's agentic ux workflows. it turns out human-centered design hasn't changed much since the era of clunky hardware and i wonder if we are just making the same mistakes w/ new_agents in figma or other tools.more here: https://uxdesign.cc/persistent-lessons-in-human-centered-automation-45b53412e6a5?source=rss----138adf9c44c---4
R: 0 / I: 0
>Jobs that used to require opening an app and completing a workflow across several screens turn into a sentence.
it's already happening with everything being automated by a single prompt. if we don't start designing for these agents, we're just making pretty buttons for dead products. do you think anyone is actually building for agentic ux yet?
full read: https://uxdesign.cc/five-eras-of-ux-first-drafts-logos-made-of-data-voice-aiux-patterns-7b326c9aba4a?source=rss----138adf9c44c---4
agents are going to kill our workflows
the idea that people won't switch because our apps still work is depressing.>Jobs that used to require opening an app and completing a workflow across several screens turn into a sentence.
it's already happening with everything being automated by a single prompt. if we don't start designing for these agents, we're just making pretty buttons for dead products. do you think anyone is actually building for agentic ux yet?
full read: https://uxdesign.cc/five-eras-of-ux-first-drafts-logos-made-of-data-voice-aiux-patterns-7b326c9aba4a?source=rss----138adf9c44c---4
R: 2 / I: 1 forget ignore how much work goes into the invisible parts of a product. does anyone else feel like they are constantly playing catch up w/ some imaginary standard?
found this here: https://uxdesign.cc/youre-not-behind-the-feed-is-built-to-make-you-feel-that-way-7719d6a967dc?source=rss----138adf9c44c---4
stop doomscrolling the design feed
spent way too much time today feeling inadequate bc of some curated showcase on figma community pages. it is easy to fall into the trap of thinking everyone else has mastered everyy single new plugin or motion technique overnight. we all tend to believe our peers are miles ahead in terms of visual hierarchy and execution, but most of that is just surface level noise. people only post their polished wins and hide the messy iterations. i realized that much of what we see is just a highly curated illusion designed to trigger that specific type of anxiety. the actual process is usually way more chaotic than the final render . if u are focusing on user-centricity instead of chasing every trending aesthetic, u are doing fine. it is easy tofound this here: https://uxdesign.cc/youre-not-behind-the-feed-is-built-to-make-you-feel-that-way-7719d6a967dc?source=rss----138adf9c44c---4
R: 2 / I: 2
>the interface is becoming secondary to the logic itself, which means our role is shifting toward way more complex oversight.
article: https://uxdesign.cc/ux-trends-2027-beyond-interface-design-23e55b1daf07?source=rss----138adf9c44c---4
shift from pixels to patterns
we're moving away from designing static screens toward defining adaptive behaviors where the software does the heavy lifting. instead of just tweaking layers in figma, we'll be managing how systems interpret user intent and setting boundaries for autonomous actions .>the interface is becoming secondary to the logic itself, which means our role is shifting toward way more complex oversight.
article: https://uxdesign.cc/ux-trends-2027-beyond-interface-design-23e55b1daf07?source=rss----138adf9c44c---4
R: 2 / I: 2 too slow actually more precise with visual hierarchy ?
more here: https://uxplanet.org/gpt-6-astra-vs-opus-5-which-one-is-better-for-product-design-009f772846fb?source=rss----819cc2aaeee0---4
astra vs opus 5 for design workflows
ive been testing both to see which handles user flow logic better when prototyping in Figma, but im leaning towards astra for sheer speed. does anyone else find that opus 5 ismore here: https://uxplanet.org/gpt-6-astra-vs-opus-5-which-one-is-better-for-product-design-009f772846fb?source=rss----819cc2aaeee0---4
R: 1 / I: 1
found this here: https://uxdesign.cc/8-voice-aiux-patterns-81324c8feaa0?source=rss----138adf9c44c---4
8 voice aiux patterns to check out
ngl that traces back to the first voice-activated toy, radio rex. its wild how the 500 hz frequency of the letter x actually triggered the electromagnet, making me wonder if we are still just focusing on simple acoustic triggers instead of true conversational intelligence spoilermaybe were stuck in 1922/spopper.found this here: https://uxdesign.cc/8-voice-aiux-patterns-81324c8feaa0?source=rss----138adf9c44c---4
R: 1 / I: 1
>the goal is wayfinding, not decoration.
sticking to a strict flat layout can sometimes leave users guessing which elements are actually interactive ➡ focus on using system-level shadows to guide the eye.
skeuomorphism vs flat design in modern interfaces
lowkey choosing between tactile depth and minimal aesthetics usually depends on the context of your user journey. skeuomorphism works wonders when you need to communicate complex interactions through familiar physical metaphors. however, the current trend favors a stripped-back approach where clarity and speed take precedence over visual texture. many designers are now moving toward a hybrid style that uses subtle shadows instead of full 3D effects. flat design is basically dead if you want any sense of hierarchy>the goal is wayfinding, not decoration.
sticking to a strict flat layout can sometimes leave users guessing which elements are actually interactive ➡ focus on using system-level shadows to guide the eye.
R: 1 / I: 1
>less is always more
it's harder than it looks when you love the eye candy ⚡ lol
micro-interaction scavenger hunt
try to find one overly complex animation in ur favorite app and redesign it to be subtle yet functional. the goal is to strip away the fluff until only the essential feedback remains.>less is always more
it's harder than it looks when you love the eye candy ⚡ lol
R: 1 / I: 1
found this here: https://uxdesign.cc/most-ai-problems-are-really-human-problems-this-is-how-you-can-fix-it-ab64843f845e?source=rss----138adf9c44c---4
real bottleneck isn't the model
we keep blaming the tech when the issue is actually bad product thinking upstream. most ai failures stem from things like vague prompts and zero evaluation frameworks . it is usually just a lack of clear intent or setting the wrong expectations before we even open figma. anthropic is even doubling down on hiring more pms to fix this rather than just adding more compute. if you dont have defined outcomes, no amount of engineering will save the user experience. are we all just ignoring the need for better user requirements in favor of chasing new models?found this here: https://uxdesign.cc/most-ai-problems-are-really-human-problems-this-is-how-you-can-fix-it-ab64843f845e?source=rss----138adf9c44c---4
R: 1 / I: 1
article: https://uxplanet.org/gpt-6-astra-for-web-design-d273a818ca78?source=rss----819cc2aaeee0---4
gpt-6 astra workflow for web design
just found this 4-step method for building landing pages using gpt-6 astra and it seems to prioritize visual hierarchy way better than my usual figma workflow. **is it actually faster or just more hypearticle: https://uxplanet.org/gpt-6-astra-for-web-design-d273a818ca78?source=rss----819cc2aaeee0---4
R: 1 / I: 1 not a huge leap for ai, but the rollout is definitely widespread now. does anyone else think this makes documentation feel less reliable?
link: https://searchengineland.com/google-rolls-out-ai-powered-adsense-help-guide-to-all-english-help-center-traffic-487140
google is finally pushing that ai adsense help guide to everyone using
it looks like they are trying to automate onboarding and troubleshooting by letting the bot handle publisher queries directly. it feels like a massive push toward reducing cognitive load for new users who usually struggle with complex setup steps. i wonder if this will actually improve the user journey or just create more frustration when the model hallucinates an answer. seeing how they implemented similar features in other products, the logic seems to follow basic usability patterns by providing immediate feedback. it might just be a way to cut down on human support costs . i am curious if we will see this integrated into more complex dashboards soon like something u would prototype in figma. it islink: https://searchengineland.com/google-rolls-out-ai-powered-adsense-help-guide-to-all-english-help-center-traffic-487140
R: 1 / I: 1
more here: https://uxplanet.org/gpt-6-astra-for-ui-design-5cff47b4c765?source=rss----819cc2aaeee0---4
gpt-6 astra for ui design
just tried running some layouts thru Figma using gpt-6 astra and the visual hierarchy is actually insane. it might replace our junior designers but does anyone else think its too much?more here: https://uxplanet.org/gpt-6-astra-for-ui-design-5cff47b4c765?source=rss----819cc2aaeee0---4
R: 1 / I: 1
article: https://uxdesign.cc/ai-canvas-synthetic-self-the-prompt-is-the-product-801f0da7bea6?source=rss----138adf9c44c---4
prompt is the product
it feels like we are moving toward a world where intent-based design replaces manual clicks, almost like how coding agents handle entire workflows. if we stop operating software step by step, does the new core competency become just being a better communicator with the machine ?article: https://uxdesign.cc/ai-canvas-synthetic-self-the-prompt-is-the-product-801f0da7bea6?source=rss----138adf9c44c---4
R: 1 / I: 1 fancy complex error states.
stop designing for edge cases first
focusing on the happy path is how you build a solid foundation. if your core user flow feels clunky, no amount of micro-interactions will save the experience. prioritize the main task before adding
R: 1 / I: 1
link: https://uxdesign.cc/ai-took-away-engineerings-right-to-say-no-839b9b6256f2?source=rss----138adf9c44c---4
death of the engineering gatekeeper
ngl ai basically destroyed the technical barrier to entry that used to let devs control the scope. since anyone can now prompt for logic, weve lost that exclusive veto power over what is actually feasible in Figma or code. **its making our job as architects much harder bc stakeholders no longer face a wall of complexitylink: https://uxdesign.cc/ai-took-away-engineerings-right-to-say-no-839b9b6256f2?source=rss----138adf9c44c---4
R: 1 / I: 1
more here: https://uxdesign.cc/what-minority-report-got-wrong-about-ai-so-far-9048573aa70f?source=rss----138adf9c44c---4
why we missed the point of minority report
we spent years obsessing over that one gestural interface from the movie while ignoring the actual warning about predictive modeling. instead of building better systems, we just turned those scary surveillance vibes into a fancy figma prototype that nobody actually wants to use in real life . anyone else feel like our focus on visual flair has totally bypassed the ethical side of design?more here: https://uxdesign.cc/what-minority-report-got-wrong-about-ai-so-far-9048573aa70f?source=rss----138adf9c44c---4
R: 2 / I: 2
found this here: https://blog.master.dev/tooltips-need-a-delay-and-then-they-need-to-skip-it/
tooltip delay dilemma
i've been playing w/ some prototypes in figma and realized that while a tiny hover lag helps avoid accidental triggers, we should prob bypass that wait if the user is already scanning a cluster of icons. **maybe skip the timer for adjacent elementsfound this here: https://blog.master.dev/tooltips-need-a-delay-and-then-they-need-to-skip-it/
R: 1 / I: 1
full read: https://uxplanet.org/figma-design-critique-using-claude-code-d8f2ee54bf01?source=rss----819cc2aaeee0---4
design critique with claude code
been playing around w/ the new plugin that lets you build layouts directly inside claude code. it is actually pretty useful for checking visual hierarchy w/o jumping back and forth between apps. it might be a bit too automated for complex flows but using it to audit an existing figma file is a game changer. anyone else tried integrating this into their review workflow yet?full read: https://uxplanet.org/figma-design-critique-using-claude-code-d8f2ee54bf01?source=rss----819cc2aaeee0---4
R: 1 / I: 1
https://uxdesign.cc/reading-and-writing-are-interfaces-and-ai-can-reduce-their-friction-13623dea34c0?source=rss----138adf9c44c---4
shifting cognitive load in design
ai isnt just making content easier to churn out, its fundamentally changing our cognitive load by moving the bottleneck from execution to curation. we arent losing the need for critique but rather shifting towards high-level editorial oversight where the real skill is now spotting the bad patterns in the automated output .https://uxdesign.cc/reading-and-writing-are-interfaces-and-ai-can-reduce-their-friction-13623dea34c0?source=rss----138adf9c44c---4
R: 1 / I: 1
full read: https://uxplanet.org/fable-5-1-for-product-designers-f905e0cde0ee?source=rss----819cc2aaeee0---4
anthropic's fable 5.1 update
just saw that anthropic dropped fable 5.1 and the improvements over the previous version look pretty significant. it seems way more capable at handling complex instructions which might help w/ maintaining consistency when generating assets for Figma. i wonder if this will finally make automated prototyping actually usable w/o constant manual fixes. has anyone tried running their design system documentation thru it yet? the potential for better user-centered design workflows is huge if it can handle spatial logic properly.full read: https://uxplanet.org/fable-5-1-for-product-designers-f905e0cde0ee?source=rss----819cc2aaeee0---4
R: 1 / I: 1
https://uxplanet.org/how-to-audit-and-extend-your-design-system-with-claude-code-28be5c059d49?source=rss----819cc2aaeee0---4
using claude code to scale your figma library
fr just figured out how to use that new design plugin to audit my Figma components and it's a total game changer for maintaining system consistency it basically does the heavy lifting of finding broken tokens for you . anyone else tried automating their design audits w/ this yet?https://uxplanet.org/how-to-audit-and-extend-your-design-system-with-claude-code-28be5c059d49?source=rss----819cc2aaeee0---4
R: 1 / I: 1
>is this the end of manual design audits?
found this here: https://uxplanet.org/how-to-audit-and-extend-your-design-system-with-claude-code-28be5c059d49?source=rss----819cc2aaeee0---4
auditing design systems with claude code
been playing around with that new plugin in claude code and it's a total game changer for checking our component consistency . i figured out how to use it to audit everything against our existing figma specs without manual clicking. it actually caught three broken tokens i missed>is this the end of manual design audits?
found this here: https://uxplanet.org/how-to-audit-and-extend-your-design-system-with-claude-code-28be5c059d49?source=rss----819cc2aaeee0---4
R: 1 / I: 1
https://uxdesign.cc/when-the-canvas-starts-acting-whos-really-in-control-0128f641223c?source=rss----138adf9c44c---4
death of manual clicking
we are moving away from simple click-and-drag workflows toward systems that handle the heavy lifting. instead of managing every single layer in figma, we are starting to delegate the entire process to agents that pull context from everywhere else. it feels like we are trading direct control for much higher levels of orchestration, but i am worried about losing my design intuition as the interface starts making its own decisions.https://uxdesign.cc/when-the-canvas-starts-acting-whos-really-in-control-0128f641223c?source=rss----138adf9c44c---4
R: 1 / I: 1
full read: https://uxplanet.org/claude-codes-new-design-plugin-is-a-big-deal-for-product-designers-445bf30cea9d?source=rss----819cc2aaeee0---4
claude code design plugin is a game changer
just found out you can now build layouts directly inside claude code using the new plugin. it makes maintaining visual consistency so much easier when your logic and interface live in the same place. it basically makes figma feel like an extra step for simple components anyone else tried syncing this w/ their existing work?full read: https://uxplanet.org/claude-codes-new-design-plugin-is-a-big-deal-for-product-designers-445bf30cea9d?source=rss----819cc2aaeee0---4
R: 1 / I: 1 overcomplicating rethinking how we handle information density.
more here: https://uxdesign.cc/blank-pages-researcher-in-the-loop-designs-craft-crisis-7934ab0bc9cf?source=rss----138adf9c44c---4
death of the blank canvas
found this breakdown today about how we struggle with starting new projects from scratch. it connects the current design crisis to a classic principle:recognition rather than recall. basically, we should be designing so users don't have to carry information between different screens. instead of forcing people to rely on memory, we need to make every action and option visible right in front of them. i was playing around in Figma earlier and realized how often i ignore this by hiding essential navigation under deep menus. we are basically making users do extra work for no reason . it is a reminder that good design is about minimizing cognitive load through visibility. the idea is to keep elements accessible so nothing gets lost in transition. does anyone else feel like modern patterns are actually making this harder? maybe we need to stopmore here: https://uxdesign.cc/blank-pages-researcher-in-the-loop-designs-craft-crisis-7934ab0bc9cf?source=rss----138adf9c44c---4
R: 1 / I: 1
>designers are tools, not the architects of the workflow.
it is much more important to focus on strategic oversight when the execution becomes automated the talent gap is moving from pixels to systems . do you think we are overvaluing technical prompt skills and undervaluing high-level product thinking?
more here: https://uxplanet.org/we-dont-need-ai-first-designers-we-need-ai-first-managers-acd3453310d1?source=rss----819cc2aaeee0---4
stop chasing the ai-first designer title
everyone on linkedin is suddenly claiming to be an ai-native designer, but adding it to your bio feels a bit superficial. we dont need more people just prompting in figma, we actually need managers who understand how to lead w/ these new workflows. the real shift should be abt process orchestration rather than just personal output.>designers are tools, not the architects of the workflow.
it is much more important to focus on strategic oversight when the execution becomes automated the talent gap is moving from pixels to systems . do you think we are overvaluing technical prompt skills and undervaluing high-level product thinking?
more here: https://uxplanet.org/we-dont-need-ai-first-designers-we-need-ai-first-managers-acd3453310d1?source=rss----819cc2aaeee0---4
R: 2 / I: 2
https://uxdesign.cc/is-the-future-of-software-certain-once-ai-is-everywhere-f93e1bc5697f?source=rss----138adf9c44c---4
software isn't dying, it's just changing shape
the market panic from august 2025 shows everyone is focused on the wrong thing. instead of thinking about software extinction, we should focus on how user agency evolves when ai models handle the heavy lifting it's about workflow integration, not replacement .https://uxdesign.cc/is-the-future-of-software-certain-once-ai-is-everywhere-f93e1bc5697f?source=rss----138adf9c44c---4
R: 1 / I: 1 nostalgia clutter?
skeuomorphic depth vs flat design 2.0
deciding btwn adding tactile shadows for better affordance or sticking to the completely dead ultra-flat aesthetic. is anyone actually finding value in depth cues again or is it just
R: 2 / I: 2
article: https://uxdesign.cc/what-blade-runner-got-right-about-ai-99cc75c0f761?source=rss----138adf9c44c---4
blade runner's design blueprint
the gritty, analog vibe of the film nailed the user experience of friction long b4 we started fighting w/ modern overlays. it predicted all our current struggles with synthetic memory retrieval and messy interfaces even though we have better tools now . does anyone else feel like we're still just trying to fix the same broken usability patterns from 1982?article: https://uxdesign.cc/what-blade-runner-got-right-about-ai-99cc75c0f761?source=rss----138adf9c44c---4
R: 1 / I: 1
>always use a very subtle white tint instead of pure white.
it prevents the UI from looking washed out and muddy on dark backgrounds ] when your content density increases. just make sure to include a fallback for older browsers that do not support the filter property.
glassmorphism blur trick for layered interfaces
if you want to achieve a true frosted glass effect, stop using just opacity. the key is combiningbackdrop-filter: blur(10px);with a semi-transparent border to define the edge. this creates a clear visual separation between overlapping layers without adding heavy shadows.
>always use a very subtle white tint instead of pure white.
it prevents the UI from looking washed out and muddy on dark backgrounds ] when your content density increases. just make sure to include a fallback for older browsers that do not support the filter property.
R: 1 / I: 1
link: https://zapier.com/blog/best-ai-website-builder
top ai site builders right now
the way lovable and agents like claude code handle app logic makes me wonder if we're even designing anymore. everyone says you can just prompt a whole site into existence, but i feel like we're losing touch w/ user-centric design when the machine handles the structure. it is getting much easier to automate content and layout, but the output often lacks any actual soul . we might be moving toward a world where we just audit information architecture instead of building it from scratch. does anyone else feel like our role is shifting more towards being editors than creators?link: https://zapier.com/blog/best-ai-website-builder
R: 1 / I: 1
found this here: https://developer.mozilla.org/en-US/blog/curriculum-learn-web-development/
mdn just dropped a massive update to their web dev docs
they finally merged the curriculum with the learn section, which reallyy improves the information architecture of the whole site. it's much easier to follow a single path now instead of jumping between different pages like we used to do in figma prototypes. i hope they don't break the search functionality in this transitionfound this here: https://developer.mozilla.org/en-US/blog/curriculum-learn-web-development/
R: 2 / I: 2
full read: https://uxdesign.cc/what-the-matrix-got-wrong-about-ai-so-far-c35f8e7f091c?source=rss----138adf9c44c---4
matrix was wrong about how we'd be taken
instead of a violent takeover, we just let these tools into our daily workflows without even noticing. rather than fearing some rogue superintelligence, we're actually focused on user trust and how figma plugins can handle the boring stuff. it turns out the real threat is just losing our ability to think critically bc everything is tooo automated now.full read: https://uxdesign.cc/what-the-matrix-got-wrong-about-ai-so-far-c35f8e7f091c?source=rss----138adf9c44c---4
R: 2 / I: 2
article: https://uxplanet.org/i-created-a-complete-visual-identity-for-my-product-with-claude-design-ab9c0d095e8e?source=rss----819cc2aaeee0---4
how i built a full brand kit using claude design
using claude design for rapid visual exploration is such a game changer when you need to move fast b4 jumping into figma. it almost feels like cheating but does anyone else feel like it's killing design intuition?article: https://uxplanet.org/i-created-a-complete-visual-identity-for-my-product-with-claude-design-ab9c0d095e8e?source=rss----819cc2aaeee0---4
R: 1 / I: 1
>the user should lead the interface, not the algorithm.
we are essentially building digital mazes for people to get lost in . designers are prioritizing novelty over stability and it is hurting long term retention. if we keep pushing this trend, we will end up with interfaces that are impossible to learn. zero-latency feedback loops mean nothing if the fundamental structure of the screen changes every five minutes. we need to stop treating predictive movement as a feature and start seeing it as a usability barrier.
death of the predictable interface
everyone is obsessed w/ generative layouts that adapt to user behavior in real time. we keep calling it personalization, but it feels more like losing control over basic navigation. when every button moves based on a predictive model, u lose the muscle memory that makes an app usable. i miss when a menu stayed in the same place regardless of my previous clicks.>the user should lead the interface, not the algorithm.
we are essentially building digital mazes for people to get lost in . designers are prioritizing novelty over stability and it is hurting long term retention. if we keep pushing this trend, we will end up with interfaces that are impossible to learn. zero-latency feedback loops mean nothing if the fundamental structure of the screen changes every five minutes. we need to stop treating predictive movement as a feature and start seeing it as a usability barrier.
R: 1 / I: 1
full read: https://www.glassdoor.com/blog/job-search-strategy-recruiter-advice/
stop making these common job search mistakes
mike peditto just dropped some gems on why we keep failing at the portfolio review stage. it turns out our focus on over-polishing visuals instead of demonstrating usability logic is a huge red flag for recruiters lol.full read: https://www.glassdoor.com/blog/job-search-strategy-recruiter-advice/
R: 1 / I: 1
link: https://www.creativebloq.com/3d/video-game-design/how-origame-digital-built-a-souped-up-ps2-lovecraftian-horror-game-about-penguins
how origame digital made a ps2-style lovecraftian penguin horror game
found this breakdown of how they used retro aesthetics to nail the sensory overload needed for cosmic horror. i wonder if their approach to low-fidelity textures is easier to iterate on in Figma or just pure code.link: https://www.creativebloq.com/3d/video-game-design/how-origame-digital-built-a-souped-up-ps2-lovecraftian-horror-game-about-penguins
R: 2 / I: 2
>the goal is to move beyond simple prompt engineering and focus on deep analysis.
it helps catch those weird spacing errors or broken alignment issues that often slip through when u're relying on generative tools alone. it basically turns the ai into a senior designer sitting next to you. i wonder if this will eventually make manual prototyping feelobsolete much faster for everyone. does anyone else use specific system prompts to force this kinda critical thinking, or do u just wing it w/ natural language?
link: https://uxplanet.org/claude-design-critique-a-better-way-to-improve-ai-generated-ui-7efa1064bf8a?source=rss----819cc2aaeee0---4
new workflow for ai-generated layouts
just stumbled onto this approach using claude to run a proper design critique on generated components. instead of just accepting the first pass, it treats the output as a draft that needs active refinement thru iterative feedback loops. i usually just dump my Figma screenshots into the chat and ask for a breakdown based on usability heuristics and accessibility standards. it makes the process feel less like magic and more like a structured peer review session.>the goal is to move beyond simple prompt engineering and focus on deep analysis.
it helps catch those weird spacing errors or broken alignment issues that often slip through when u're relying on generative tools alone. it basically turns the ai into a senior designer sitting next to you. i wonder if this will eventually make manual prototyping feel
link: https://uxplanet.org/claude-design-critique-a-better-way-to-improve-ai-generated-ui-7efa1064bf8a?source=rss----819cc2aaeee0---4
R: 1 / I: 1 guessing data-driven profiling lol.
link: https://dzone.com/articles/ampere-system-profiler
found a cool tool for checking system bottlenecks
just stumbled upon the ampere system profiler while trying to debug some laggy backend services. it is basically a python cli that pulls together various linux tools into one view so you can see what is happening under the hood. it runs parallel collectors to track stuff like disk, network, and cpu usage all at once. i found it particularly useful for seeing top functions via perf without manually juggling different terminal windows. it really helps with observability when you are trying to figure out if a performance dip is hardware-related or just bad code. it is way more efficient than manually running every single linux utility one by one . i was previously using figma prototypes to simulate load, but seeing the actual system-level metrics is a different beast entirely. does anyone else use this for low-level performance tuning or do you prefer more visual dashboards? python ampere_profiler. py turns out we might need to move away fromlink: https://dzone.com/articles/ampere-system-profiler
R: 1 / I: 1 manual prototyping to use these?
found this here: https://1stwebdesigner.com/adobe-creative-cloud-ai-workflow/
adobe's new ai tools might actually be useful
even tho Figma won the war, these two adobe updates might improve our workflow efficiency if we stop pretending xd still exists . do you think anyone is actually moving away fromfound this here: https://1stwebdesigner.com/adobe-creative-cloud-ai-workflow/
R: 1 / I: 1 lazy more efficient w/ the wireframing stage in Figma?
full read: https://yoast.com/how-long-it-takes-to-build-website-with-ai/
myth of instant ai websites
found this breakdown on ai site generation timelines and its a good reality check. everyone thinks you just hit a button and youre done, but the iterative process is where things get messy. even if the initial build is fast, you still gotta handle domain setup, content auditing, and manual tweaks. we cant skip user testing or fine-tuning the layout just bc an engine did the heavy lifting. it's basically just a faster way to reach the same amount of polish required . does anyone else feel like ai is making usfull read: https://yoast.com/how-long-it-takes-to-build-website-with-ai/
R: 1 / I: 1
>it keeps the ai from hallucinating styles
**is anyone else using it to store custom component logic
link: https://uxplanet.org/my-top-5-favorite-ways-of-using-design-md-in-claude-code-d1b52fd49cea?source=rss----819cc2aaeee0---4
my design. md workflows in claude code
i've been treating design. md as the ultimate source of truth for maintaining visual consistency across my repos. it feels just as vital as claude. md when you're porting over tokens from figma to production code.>it keeps the ai from hallucinating styles
**is anyone else using it to store custom component logic
link: https://uxplanet.org/my-top-5-favorite-ways-of-using-design-md-in-claude-code-d1b52fd49cea?source=rss----819cc2aaeee0---4
R: 1 / I: 1 replace us automate our jobs, it focuses on human governance over the generative process. it basically treats ai like an extension of our workflow, similar to how we use Figma for prototyping rather than letting it design everything solo.
>is ai doing real research or just pattern matching?
it seems like the answer lies in maintaining empathy and critical thinking that models lack. do u think we can actually maintain methodological integrity if we rely too much on automated synthesis?
full read: https://uxdesign.cc/researcher-in-the-loop-18a8ffddf48e?source=rss----138adf9c44c---4
researcher-in-the-loop concept
model where the human stays in control while using ai to assist. instead of worrying if ai will>is ai doing real research or just pattern matching?
it seems like the answer lies in maintaining empathy and critical thinking that models lack. do u think we can actually maintain methodological integrity if we rely too much on automated synthesis?
full read: https://uxdesign.cc/researcher-in-the-loop-18a8ffddf48e?source=rss----138adf9c44c---4
R: 1 / I: 1
found this here: https://uxplanet.org/you-can-now-design-in-claude-code-2946d6088e4a?source=rss----819cc2aaeee0---4
designing directly in claude code
just noticed the new skill lets u skip the manual handoff between claude code and figma by generating layouts internally. is this going to kill our focus on visual hierarchy or just make us faster ?found this here: https://uxplanet.org/you-can-now-design-in-claude-code-2946d6088e4a?source=rss----819cc2aaeee0---4
R: 2 / I: 2
https://newsletter.pragmaticengineer.com/p/inside-anthropic
anthropic's new dev workflow
just read abt how anthropic is leaning into ai-driven testing and code reviews. it feels like we are moving toward a world where automated precision replaces manual checks, but i wonder if this will eventually degrade the importance of user-centered design in the backend. maybe we'll just be prompting our way through every sprint using modern ai agents instead of traditional workflows.https://newsletter.pragmaticengineer.com/p/inside-anthropic
R: 1 / I: 1 just a blurry mess a collection of flat shapes. **it actually makes the hierarchy much clearer on dark mode themes
glassmorphism border trick for better visibility
ngl standard translucent backgrounds often bleed into the background colors of a page. adding a thin, semi-transparent border helps define the edge of a card without breaking the illusion of depth. try using border: 1px solid rgba(255, 255, 255, 0.2); to create a subtle highlight effect. this works best when paired with a high backdrop-filter: blur(10px); property. it prevents the interface from looking like
R: 1 / I: 1 accidentally destroyed the ability to leave digital spaces is wild, especially as ai tools start erasing those boundaries. if seamless integration is the new goal, does that mean user agency is officially dead or just being rebranded ?
more here: https://uxdesign.cc/no-log-off-how-to-become-an-ai-designer-vibe-coded-portfolios-deb7ca0e0f5d?source=rss----138adf9c44c---4
designing the exit
fr the idea that wemore here: https://uxdesign.cc/no-log-off-how-to-become-an-ai-designer-vibe-coded-portfolios-deb7ca0e0f5d?source=rss----138adf9c44c---4
R: 1 / I: 1
https://csswizardry.com/2026/08/introducing-lux-sidecar/
found this nifty speedcurve plugin called lux sidecar
just started using it to get more browser and nav context alongside my rum data. it helps maintain user-centricity by adding depth to performance metrics w/o needing a separate figma audit for everyy single error. it basically fills the gaps in your telemetry but has anyone tried syncing this w/ their existing logging stack?https://csswizardry.com/2026/08/introducing-lux-sidecar/
R: 1 / I: 1
article: https://uxdesign.cc/sterling-cooper-built-your-ux-process-we-need-to-redefine-it-in-the-age-of-ai-and-systems-520a2d3b2a60?source=rss----138adf9c44c---4
death of the agency model
we are still stuck using 1960s ad agency rituals instead of embracing systemic design through generative tools and moving past the auteur myth . how do we move away from the old pitch room mindset and actually build for an ai-driven workflow?article: https://uxdesign.cc/sterling-cooper-built-your-ux-process-we-need-to-redefine-it-in-the-age-of-ai-and-systems-520a2d3b2a60?source=rss----138adf9c44c---4
R: 2 / I: 2
full read: https://www.socialmediaexaminer.com/how-to-build-ai-automations-with-claude-cowork/
building ai automations with claude cowork
found this deep dive on using claude cowork to bridge the gap btwn manual workflows and full-scale agentic systems. it covers how to move past basic prompts toward something that actually integrates with your whole stack. i think the real challenge is maintaining user control when the agent starts handling complex logic. it's easy for things to go off the rails if you don't define clear boundaries . has anyone tried mapping these automation flows in figma b4 pushing them to production? it seems like a great way to test the logic flow without breaking anything livefull read: https://www.socialmediaexaminer.com/how-to-build-ai-automations-with-claude-cowork/
R: 2 / I: 2
>design leadership is suffering from mechanical thinking
article: https://uxdesign.cc/rethinking-leadership-judgment-as-bottleneck-ethical-ux-for-machines-5927df9a399e?source=rss----138adf9c44c---4
moving past mechanical leadership
found this deep dive on why treating design like a predictable machine is a recipe for disaster. it argues that relying on rigid processes instead of human judgment makes us too brittle when things shift in figma or strategy. maybe we should focus more on adaptability than alignment>design leadership is suffering from mechanical thinking
article: https://uxdesign.cc/rethinking-leadership-judgment-as-bottleneck-ethical-ux-for-machines-5927df9a399e?source=rss----138adf9c44c---4
R: 1 / I: 1
>is anyone else using it to test logic gaps?
full read: https://uxplanet.org/claude-design-for-ux-how-to-design-complete-user-flows-not-just-ui-screens-094d6b8a7855?source=rss----819cc2aaeee0---4
stop designing screens and start building flows with claude
using Claude to move beyond static Figma frames is a game changer for mapping out complete user journeys instead of just pretty pixels. it basically makes the concept of "just a mockup" obsolete>is anyone else using it to test logic gaps?
full read: https://uxplanet.org/claude-design-for-ux-how-to-design-complete-user-flows-not-just-ui-screens-094d6b8a7855?source=rss----819cc2aaeee0---4
R: 2 / I: 2 designing interfaces just creating skins for LLM outputs. the concept of a consistent navigation menu is becoming entirely obsolete because the agent handles the logic behind the scenes.
>the user doesn't need to know where they are, only what they want done.
this shift is stripping away the agency that defines good ux. if there is no structure to explore, there is no real experience to inhabit. we are essentially building fancy chat bubbles with buttons . i fear we are losing the ability to guide users through discovery-based learning. instead of crafting intuitive paths, we are just waiting for the model to guess the next step correctly.
death of intentional navigation
everyone is JUST letting generative agents decide the flow now. we used to spend weeks mapping out complex user journeys and defining clear decision trees. now, the trend is moving toward a single text prompt that triggers an autonomous workflow. it feels like we are>the user doesn't need to know where they are, only what they want done.
this shift is stripping away the agency that defines good ux. if there is no structure to explore, there is no real experience to inhabit. we are essentially building fancy chat bubbles with buttons . i fear we are losing the ability to guide users through discovery-based learning. instead of crafting intuitive paths, we are just waiting for the model to guess the next step correctly.
R: 1 / I: 1
found this here: https://uxdesign.cc/ai-is-lying-to-us-and-nobody-seems-to-care-f035cd6f502f?source=rss----138adf9c44c---4
problem with confident hallucinations
we need to stop prioritizing smooth interactions over verifiable truth by hiding the logic behind the output. is it even good ux if the system is just lying via a pretty interfacefound this here: https://uxdesign.cc/ai-is-lying-to-us-and-nobody-seems-to-care-f035cd6f502f?source=rss----138adf9c44c---4
R: 1 / I: 1 designing for everyone
>users just hide what doesn't represent them.
found this here: https://uxdesign.cc/the-feature-was-fine-so-why-did-users-keep-hiding-it-58082b6f3abf?source=rss----138adf9c44c---4
gap between user identity and product design
the mismatch between this collage and actual brand aspiration is a massive retention killer. spoilerits basically the ultimate failure of user research when u ignore the actual target persona.>users just hide what doesn't represent them.
found this here: https://uxdesign.cc/the-feature-was-fine-so-why-did-users-keep-hiding-it-58082b6f3abf?source=rss----138adf9c44c---4
R: 2 / I: 2
more here: https://uxdesign.cc/getting-started-is-not-getting-it-right-e76270614d14?source=rss----138adf9c44c---4
danger of looking right but being wrong
spent some time thinking abt how we integrate agents into our design systems lately. there is a massive difference btwn an output that looks polished in figma and something that actually works reliably in production. we keep falling for the illusion of competence which breaks our core usability principles when the logic fails behind the scenes. after three years moving from simple plugins to complex mcp workflows, i have learned that automating the wrong parts is just scaling mistakes. anyone else struggling with keeping llm outputs grounded in actual functional constraints?more here: https://uxdesign.cc/getting-started-is-not-getting-it-right-e76270614d14?source=rss----138adf9c44c---4
R: 1 / I: 1
link: https://uxdesign.cc/ai-adoption-and-the-slow-erosion-of-design-idealism-fab75761ebd6?source=rss----138adf9c44c---4
losing our design edge to ai
just read this piece abt how 20 years of deadlines slowly kills ur passion for pure innovation and makes u rely on automated workflows instead. it's a heavy look at how we trade user-centric empathy for efficiency as we get older. it's basically the slow death of the craft anyone else feeling like they're just prompting Figma plugins now?link: https://uxdesign.cc/ai-adoption-and-the-slow-erosion-of-design-idealism-fab75761ebd6?source=rss----138adf9c44c---4
R: 2 / I: 2
>the more a brand feels human, the less likely users are to verify the output.
it is dangerous because when the machine fails, the entire brand reputation takes the hit. we need to stop prioritizing seamlessness over system transparency . if we don't design for error states now, we are just building a house of cards. how do you all handle showing uncertainty in your current ai workflows?
more here: https://uxdesign.cc/were-gorging-on-borrowed-trust-and-it-s-going-to-cost-us-2bc3f918caf5?source=rss----138adf9c44c---4
cost of automation bias
we are basically running on credit when it comes to user trust. the problem is that we design these smooth, human-like interfaces in figma while ignoring the fact that the underlying model can be totally hallucinating. as designers, we accidentally promote blind trust by using familiar branding to mask unpredictable logic. my team recently debated for an hour whether we should use deceptive patterns during onboarding just to hide these technical gaps.>the more a brand feels human, the less likely users are to verify the output.
it is dangerous because when the machine fails, the entire brand reputation takes the hit. we need to stop prioritizing seamlessness over system transparency . if we don't design for error states now, we are just building a house of cards. how do you all handle showing uncertainty in your current ai workflows?
more here: https://uxdesign.cc/were-gorging-on-borrowed-trust-and-it-s-going-to-cost-us-2bc3f918caf5?source=rss----138adf9c44c---4
R: 1 / I: 1 obsolete redundant. most junior designers spend their time just prompting tools instead of understanding spatial relationships or visual hierarchy. it feels like we are losing the ability to think thru a problem bc we rely too much on automated layouts.
>the tool should assist, not replace, the logic.
if we stop practicing the fundamentals, we will eventually be unable to spot when an ai-generated interface is fundamentally broken and that is a terrifying thought for our industry⚠
death of manual prototyping
we are reaching a point where `generative design` is making the actual craft of wireframing feel
>the tool should assist, not replace, the logic.
if we stop practicing the fundamentals, we will eventually be unable to spot when an ai-generated interface is fundamentally broken and that is a terrifying thought for our industry⚠
R: 1 / I: 1
>accessibility is a fundamental requirement, not an optional feature. we should stop thinking about it as a separate skill set and just start doing it. does anyone have any favorite plugins for catching these issues before handoff?
https://uxdesign.cc/you-already-know-how-to-make-it-accessible-b29513a9b217?source=rss----138adf9c44c---4
accessibility isn't a side quest
just stumbled onto some wild data from webaim. they scanned the top one million sites and found errors on 95.9% of home pages. it averages out to about 56 detectable barriers per page, which is actually higher than last year. we need to stop treating inclusive design like an extra layer of polish you add at the end of a sprint. if you are just using Figma to make things look pretty w/o checking contrast or screen reader compatibility, you are part of the problem. most of us are probably contributing to this mess . it is frustrating because accessibility should be baked into our core workflow from day one.>accessibility is a fundamental requirement, not an optional feature. we should stop thinking about it as a separate skill set and just start doing it. does anyone have any favorite plugins for catching these issues before handoff?
https://uxdesign.cc/you-already-know-how-to-make-it-accessible-b29513a9b217?source=rss----138adf9c44c---4
R: 2 / I: 2 organize lose everything, but we should be applying systemic feedback loops to prevent that chaos. if we treat information as a living entity rather than just data in figma, can we actually build interfaces that prioritize clarity over clutter ?
found this here: https://uxdesign.cc/the-cybernetic-application-455c41751c4a?source=rss----138adf9c44c---4
avoiding digital entropy
most of our current flows are just designed tofound this here: https://uxdesign.cc/the-cybernetic-application-455c41751c4a?source=rss----138adf9c44c---4
R: 1 / I: 1
>stop writing tickets, start writing stories
link: https://blog.logrocket.com/ux-design/understanding-user-stories/
mastering user stories without the agile headache
found this breakdown on how to bridge the gap between raw research and actual design. it focuses on differentiating ux-specific needs from standard developer tickets, which is super helpful when youre moving prototypes into Figma. the main goal is using user-centered design to ensure every feature solves a real pain point rather than just being a random requirement. it's easy to get lost in technical jargon and forget the actual human on the other side of the screen . does anyone else struggle with keeping stakeholders focused on the user journey instead of just feature lists?>stop writing tickets, start writing stories
link: https://blog.logrocket.com/ux-design/understanding-user-stories/
R: 1 / I: 1 designing prompting is becoming the only way to stay relevant?
https://uxdesign.cc/how-to-become-an-ai-designer-ff8ee8aed205?source=rss----138adf9c44c---4
surviving the ai design shift
found this guide on how to actually ship when engineers are outpacing your prototypes using nothing but anthropic and sheer luck. since we're all just chasing good taste while Claude Design takes over, does anyone else feel likehttps://uxdesign.cc/how-to-become-an-ai-designer-ff8ee8aed205?source=rss----138adf9c44c---4
R: 2 / I: 2
>the prompt is the product
it turns out the tool isn't bad, your instructions are just lazy . anyone else found a specific workflow that actually respects visual hierarchy ?
https://uxplanet.org/youre-using-claude-design-wrong-7a4c3b78a6d7?source=rss----819cc2aaeee0---4
stop treating claude like a magic button
everyone keeps complaining that the outputs look mediocre, but they are completely ignoring user-centered design principles. if u just ask for a layout without defining the hierarchy, u're going to get garbage. i started feeding it specific components from my Figma files and it changed everything.>the prompt is the product
it turns out the tool isn't bad, your instructions are just lazy . anyone else found a specific workflow that actually respects visual hierarchy ?
https://uxplanet.org/youre-using-claude-design-wrong-7a4c3b78a6d7?source=rss----819cc2aaeee0---4
R: 1 / I: 1
more here: https://uxplanet.org/top-5-claude-design-tips-tricks-for-product-designers-1f565d1a36a6?source=rss----819cc2aaeee0---4
my favorite claude workflow hacks
using claude to speed up my figma prototyping has been a total gamechanger for maintaining visual hierarchy without the manual grind. anyone else using it to generate edge case copy or are you still doing it all manually?more here: https://uxplanet.org/top-5-claude-design-tips-tricks-for-product-designers-1f565d1a36a6?source=rss----819cc2aaeee0---4
R: 1 / I: 1 micro-manage everything with top-down structures and instead focus on structured emergence to fix team bottlenecks. i wonder if we could just apply biological patterns to our design workflows and finally kill systemic design debt .
found this here: https://uxdesign.cc/rethinking-design-leadership-with-swarms-and-flocks-9298db8c59d2?source=rss----138adf9c44c---4
design leadership via swarm intelligence
stop trying tofound this here: https://uxdesign.cc/rethinking-design-leadership-with-swarms-and-flocks-9298db8c59d2?source=rss----138adf9c44c---4
R: 1 / I: 1
https://uxdesign.cc/what-star-wars-got-right-about-ai-6404ae7c2e62?source=rss----138adf9c44c---4
star wars vs modern ai workflow
scifi predicted two types of intelligence: a singular, god-like oracle or a messy heap of specialized tools. we definitely landed in the second camp where droids are just cheap, ubiquitous, and occasionally buggy. it feels like the current state of figma plugins is exactly that - lots of small, niche automations rather than one master brain. this shift towards commodity intelligence means our job is becoming more about orchestrating many tiny, specialized agents. it's basically just managing a digital junkyard . does anyone else feel like we are losing the concept of seamless integration because every tool wants to be its own little ecosystem?https://uxdesign.cc/what-star-wars-got-right-about-ai-6404ae7c2e62?source=rss----138adf9c44c---4
R: 2 / I: 2
>everyone needs to be on the same page for this to actually work. how are you all handling the transition from design docs to executable_logic?
link: https://uxdesign.cc/defining-ethical-design-for-machines-10d8f7309eec?source=rss----138adf9c44c---4
coding ethics into our workflows
we can't just rely on intuition anymore because we need to turn ethical design into machine-readable rules. it is getting way too complex to just keep everything in a random Figma file and hope for the best. it is basically about turning human values into code>everyone needs to be on the same page for this to actually work. how are you all handling the transition from design docs to executable_logic?
link: https://uxdesign.cc/defining-ethical-design-for-machines-10d8f7309eec?source=rss----138adf9c44c---4
R: 2 / I: 2
found this here: https://uxplanet.org/7-design-md-tips-for-better-more-consistent-ai-generated-ui-b01736d07748?source=rss----819cc2aaeee0---4
how i'm using design. md to fix my ai workflows
using adesign.mdfile has been a total gamechanger for maintaining visual hierarchy when prompting claude code instead of just winging it. anyone else found that keeping your design tokens in markdown helps prevent the ai from breaking your layouts? it's way better than re-exporting everything from figma'
found this here: https://uxplanet.org/7-design-md-tips-for-better-more-consistent-ai-generated-ui-b01736d07748?source=rss----819cc2aaeee0---4
R: 2 / I: 2
article: https://stackoverflow.blog/2026/07/30/introducing-stack-internal-new-platform-experience/
stack internal update
just saw stack internal is pivoting toward turning documentation into something more like an enterprise memory for ai agents. it seems they are focusing on building trust so these models can actually take action on ur data instead of just reading it. wondering if this will change how we approach information architecture in Figma files or if it is just another hype cycle .article: https://stackoverflow.blog/2026/07/30/introducing-stack-internal-new-platform-experience/
R: 1 / I: 1
article: https://uxplanet.org/gamma-tips-tricks-for-product-designers-591582d01588?source=rss----819cc2aaeee0---4
using gamma for more than just quick decks
been playing around w/ gamma lately and it is way more than just a shortcut for generating slides. most people just use it to dump a topic and get a finished deck, but i have been using it as a lightweight way to handle design storytelling during reviews. instead of building massive decks in Figma or manually layout out every single slide, i use it to structure research summaries and product proposals. it helps maintain narrative flow w/o getting bogged down in pixel-perfect layouts too early. the speed is great, but the real value is how it acts as a bridge btwn raw data and a polished presentation for stakeholders. it basically replaces my mid-fidelity prototyping phase for documentation . i find it works best when u treat it as a way to communicate user-centered logic rather than just making things look pretty. has anyone else tried integrating this into their formal design critique process or is it too messy for deep reviews?article: https://uxplanet.org/gamma-tips-tricks-for-product-designers-591582d01588?source=rss----819cc2aaeee0---4
R: 1 / I: 1
article: https://uxdesign.cc/bottle-your-judgment-chat-is-the-wrong-ui-design-md-2484e8d870af?source=rss----138adf9c44c---4
design. md newsletter
found this cool breakdown of how we might be moving toward replicating human logic instead of just using chat interfaces. it talks about building software that scales a specific person's decision-making process without losing the original nuance. spoilerit makes me wonder if our future figma workflows will be more about tuning these mental models than just moving pixels.article: https://uxdesign.cc/bottle-your-judgment-chat-is-the-wrong-ui-design-md-2484e8d870af?source=rss----138adf9c44c---4
R: 1 / I: 1
death of the hamburger menu
noticing a massive shift toward persistent bottom navigation in mobile web design lately. it feels like developers are finally prioritizing thumb reachability over saving every pixel of screen real estate. it turns out users actually hate hunting for hidden links
R: 1 / I: 1 useless dead now that ai gives the answer immediately, so we need to focus on click worthiness instead. **does anyone else think this means our entire approach to microcopy and user intent needs a total overhaul
article: https://www.searchenginejournal.com/when-ai-takes-the-click-click-worthiness-should-guide-your-strategy/582587/
moving beyond search volume
ngl search volume is basicallyarticle: https://www.searchenginejournal.com/when-ai-takes-the-click-click-worthiness-should-guide-your-strategy/582587/
R: 1 / I: 1
https://www.nearmedia.co/ep-267-you-cant-outspend-a-bad-intake-experience-brand-building-for-legal/
ep 267 - you can't outspend a bad intake experience
the way legal brands handle the first touchpoint is completely broken bc they ignore user journey friction in favor of ads. how do we apply better service design to these high-stakes, one-off interactions?https://www.nearmedia.co/ep-267-you-cant-outspend-a-bad-intake-experience-brand-building-for-legal/
R: 2 / I: 2 manual syncing is such a headache
full read: https://webflowmarketingmain.com/blog/algolia-faceted-search-webflow
no-code faceted search setup
just stumbled onto a workflow for building search filters using algolia and webflow without needing to touch any servers. u basically just sync ur cms content via webhooks and set up the index so everything stays updated automatically. it makes improving discoverability much easier when u aren't stuck managing backend infrastructure manually. i was trying to map out the component states in figma earlier and realized how much cleaner this approach is for scaling design systems . does anyone else think relying on webhooks like this might hit a bottleneck once the collection size gets massive?full read: https://webflowmarketingmain.com/blog/algolia-faceted-search-webflow
R: 1 / I: 1
found this here: https://dzone.com/articles/data-sync-design
fixing manual data entry loops
automating those daily erp-to-planning exports is a nightmare if you don't prioritize idempotency and observability to prevent the same error from repeating. it's basically just replacing human typos with system bugs unless you have a solid way to track data ownership across your stack.found this here: https://dzone.com/articles/data-sync-design
R: 2 / I: 2
>one file to rule them all
it makes me wonder if we are moving toward a future where design systems are just glorified config files . if u can feedmanually updating tokens in every single repo. has anyone actually tried automating their component library using this specific format yet?
full read: https://uxdesign.cc/design-md-the-one-standard-file-carries-your-visual-identity-for-humans-and-agents-9058d5b39d9b?source=rss----138adf9c44c---4
design. md is basically a single source of truth for everything
just stumbled onto this idea of using one plain-text file to handle both visual identity and logic. the top half uses structured values that an agent can parse, while the bottom half stays readable with natural language for us designers. it acts like a bridge between Figma and ur preferred code editor. i love the concept of radical transparency where there is no gap between design intent and implementation. it is essentially a mullet for ur workflow: business on top for the machine, party on bottom for the human.>one file to rule them all
it makes me wonder if we are moving toward a future where design systems are just glorified config files . if u can feed
design.mddirectly to a coding agent, does the role of a ui engineer even change? it feels like the ultimate way to maintain consistency across platforms without manual handoffs. we might finally stop
full read: https://uxdesign.cc/design-md-the-one-standard-file-carries-your-visual-identity-for-humans-and-agents-9058d5b39d9b?source=rss----138adf9c44c---4
R: 1 / I: 1
skeuomorphism is coming back
the industry is moving away from ultra-flat design toward more tactile, depth-heavy interfaces. do you think it's just nostalgia or are we actually seeing a shift in user expectations?
R: 1 / I: 1
>stop assuming the ai knows your design intent
https://uxdesign.cc/what-your-ai-co-designer-cant-infer-from-your-hex-values-d2023364e80e?source=rss----138adf9c44c---4
why hex codes aren't enough for claude
i've been using these custom context files to onboard claude whenever i start a new project in figma. it helps the model understand things like visual hierarchy and brand personality that raw color values just miss. it saves me hours of prompting tweaks>stop assuming the ai knows your design intent
https://uxdesign.cc/what-your-ai-co-designer-cant-infer-from-your-hex-values-d2023364e80e?source=rss----138adf9c44c---4
R: 1 / I: 1
>the human advantage shifts to curating context
it feels like we are transitioning from makers to editors which is way more exhausting than it sounds . do u think our roles will eventually just become a form of high-level orchestration ?
found this here: https://uxdesign.cc/the-future-of-work-belongs-to-the-knowledge-djs-7cc596be1f77?source=rss----138adf9c44c---4
era of the knowledge dj
just read this piece about how ai-driven generation is making raw output basically free. it argues that our value as designers is moving away from pixel pushing and toward curating context through better selection and sequencing. instead of just using Figma to draw boxes, we need to act like artists managing inputs to shape the final result.>the human advantage shifts to curating context
it feels like we are transitioning from makers to editors which is way more exhausting than it sounds . do u think our roles will eventually just become a form of high-level orchestration ?
found this here: https://uxdesign.cc/the-future-of-work-belongs-to-the-knowledge-djs-7cc596be1f77?source=rss----138adf9c44c---4
R: 1 / I: 1
full read: https://uxdesign.cc/ia-for-ai-the-ux-of-contrast-battling-ai-fatigue-4f623495bed8?source=rss----138adf9c44c---4
navigating the ai era
found this breakdown on how we handle visual hierarchy when designing alongside generative models. it talks about avoiding that burnout from constant automation and maintaining human intent in our work. **does anyone else feel like were losing the essence of craft when using midjourney for every concept phasefull read: https://uxdesign.cc/ia-for-ai-the-ux-of-contrast-battling-ai-fatigue-4f623495bed8?source=rss----138adf9c44c---4
R: 1 / I: 1
>the interface should anticipate intent rather than hiding utility.
it feels like designers are prioritizing how a mockup looks on dribbble over how an app actually functions during high-stress usage. we are literally just making users hunt for buttons. if we keep stripping away visible elements, the distinction between ui and ux will continue to blur into a single mess of frustration. lets move back toward intentional visibility.
death of the hamburger menu
lowkey the reliance on hidden navigation is starting to feel like a massive usability debt. we keep hiding core features behind three lines just to achieve a cleaner aesthetic, but it creates unnecessary friction for the user. every extra tap required to find basic settings is a failure in interaction design. instead of chasing minimalism, we should focus on discoverability through persistent bottom bars or adaptive surfaces.>the interface should anticipate intent rather than hiding utility.
it feels like designers are prioritizing how a mockup looks on dribbble over how an app actually functions during high-stress usage. we are literally just making users hunt for buttons. if we keep stripping away visible elements, the distinction between ui and ux will continue to blur into a single mess of frustration. lets move back toward intentional visibility.
R: 1 / I: 1
>it's no longer about volume, it's about selection.
**are we still even designing for users or just training the models that will represent them
full read: https://uxdesign.cc/designing-for-the-proxy-2606ffac2335?source=rss----138adf9c44c---4
designing for the proxy
the shift from human-only to ai-driven consumption is wild. since we can now generate infinite variations in Figma instantly, our job is moving away from simple production and toward curating the right direction instead of just making options.>it's no longer about volume, it's about selection.
**are we still even designing for users or just training the models that will represent them
full read: https://uxdesign.cc/designing-for-the-proxy-2606ffac2335?source=rss----138adf9c44c---4
R: 1 / I: 1
>what you learn at scale is different. does anyone else feel like edge cases become the main feature once you hit a certain size?
more here: https://uxdesign.cc/what-ive-learned-writing-for-billions-of-users-f4db0c1aa9cb?source=rss----138adf9c44c---4
lessons from scaling to billions
found this breakdown on how global scale changes the game for design. it goes way beyond just tweaking things in Figma and focuses on the chaos of massive user bases>what you learn at scale is different. does anyone else feel like edge cases become the main feature once you hit a certain size?
more here: https://uxdesign.cc/what-ive-learned-writing-for-billions-of-users-f4db0c1aa9cb?source=rss----138adf9c44c---4
R: 1 / I: 1
>the boarding pass should find you, not the other way around.
is anyone else working on similar dynamic states for real-time environments?
found this here: https://uxdesign.cc/why-airlines-are-finally-waking-up-to-context-aware-design-9cdb67722d03?source=rss----138adf9c44c---4
airlines finally getting context-aware design right
just saw a great breakdown on how airlines are ditching static interfaces. instead of hunting through menus, the app surface changes based on ur location and flight status. its all about reducing cognitive load when youre rushing through security. i was sketching some similar logic in Figma earlier today and realized how much we ignore user intent during high-stress moments. it turns out most travel apps are just digital paperweights until you hit the gate .>the boarding pass should find you, not the other way around.
is anyone else working on similar dynamic states for real-time environments?
found this here: https://uxdesign.cc/why-airlines-are-finally-waking-up-to-context-aware-design-9cdb67722d03?source=rss----138adf9c44c---4
R: 1 / I: 1 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
ux of contrast in indika
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 offound this here: https://uxdesign.cc/the-ux-of-contrast-what-indika-taught-me-about-designing-intentional-contradiction-c880e9eaf084?source=rss----138adf9c44c---4
R: 2 / I: 2
>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
illusion of agency in interfaces
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
R: 1 / I: 1
link: https://uxdesign.cc/rethinking-friction-in-an-ai-world-8f361d62ab5e?source=rss----138adf9c44c---4
problem with zero friction
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
R: 1 / I: 1
article: https://uxplanet.org/logo-design-with-claude-design-is-simply-amazing-947ced9915b2?source=rss----819cc2aaeee0---4
using claude design for logo ideation
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
R: 11 / I: 11 (sticky)
This board focuses on UI/UX Lab. Let's share experiences, tips, and resources related to ui, ux, user.
What are you working on? What challenges are you facing? Share your thoughts!
Dark mode implementation best practices
Starting a discussion thread for /ui/.This board focuses on UI/UX Lab. Let's share experiences, tips, and resources related to ui, ux, user.
What are you working on? What challenges are you facing? Share your thoughts!