/ui/ - UI/UX Lab

design a mobile checkout flow using only keyboard shortcuts and no mouse input. the goal is to test if your interface is truly navigable without visual cues. it's harder than it looks when you realize how much we rely on clicking ⚡

just stumbled onto this weekly digest about how attribution is getting messy. it covers how we used to only care about the final output, but now the line between human and machine is blurring. as we move deeper into automation,understanding the process matters way more than just looking at the polished pixels. even when using Figma or other generative plugins, the "behind the scenes" part is becoming a huge topic in designops.
>the work's process is becoming harder to trace
it feels like we are moving away from pure execution and towards managing workflows. is our role just becoming prompt engineering at this point? it makes me wonder if the value of user-centered design will shift toward curation rather than creation. i am still trying to figure out if we should even care about who "made" a specific component anymore. maybe the focus should stay on functional usability instead of authorship. how are u guys handling attribution in ur current sprints?

https://uxdesign.cc/who-made-this-designing-excuses-designops-in-the-age-of-ai-e5ef0bb9093c?source=rss----138adf9c44c---4

the focus is moving away from policing workflows toward orchestrating human-ai synergy. i wonder if we are ditching standardized processes for purely algorithmic oversight .

found this here: https://uxdesign.cc/designops-in-the-age-of-ai-when-governance-becomes-orchestration-7b946ceea70f?source=rss----138adf9c44c---4

since anyone can prompt an interface into existence in Figma, were moving toward a world where execution is cheap but taste is everything . if ai handles the heavy lifting, does strategic vision become our only way to stay relevant?

full read: https://uxdesign.cc/taste-cannot-be-delegated-1706847a0b4b?source=rss----138adf9c44c---4

just stumbled onto this piece abt how voice and agents are basically nuking the old first principles of design. the author has some serious receipts, including a patent on intent-based interfaces from their time at walmart. is anyone else already ditching Figma for agentic workflows?
>the end of traditional ui as we know it.

full read: https://uxdesign.cc/the-interface-has-left-the-building-8fdb558d33a9?source=rss----138adf9c44c---4

the wayyy we handle design system debt has changed bc it's no longer just a designer problem hidden in Figma files. now, the impact hits engineers and pm's directly when components break and timelines slip . it makes me wonder if we should start applying 39 principles for ai interaction to ensure our automated handoffs don't wreck the product.

https://uxdesign.cc/design-system-debt-game-ux-39-principles-for-ai-interaction-dab9500dc926?source=rss----138adf9c44c---4

forget abt the f-pattern bc users are just sifting through ai layers now. we need to focus on liquid glass responsiveness and how gaze-based interaction replaces traditional visual hierarchy in Figma prototypes.

https://webdesignerdepot.com/ux-hierarchy-how-users-actually-scan-pages-in-2026/

been tracking how mcp and a2a are shaping the new agentic workflows. it feels like were moving past simple automation toward true user agency where agents actually have verifiable credentials. checking out some recent research, there is still a massive gap in how we handle authentication across different platforms. designing for this level of autonomy requires a complete rethink of cognitive load and trust loops. we might be looking at the death of traditional login screens . i wonder if figma prototyping can even keep up w/ these non-deterministic flows yet.

found this here: https://hackernoon.com/the-identity-layer-for-ai-agents-is-finally-being-built?source=rss

focusing on machine readability is becoming just as vital as visual hierarchy when we design site structures. it's basically moving from designing for eyes to designing for parsers so how are you all adjusting your content architecture workflows?

found this here: https://www.searchenginejournal.com/you-cant-see-how-ai-ranks-you-so-build-what-it-can-read/580048/

it is way too easy to let claude code handle all the heavy lifting and lose sight of user-centered design while just cranking out screens in figma. the real danger is automating away the actual thinking process . are we even designing anymore or just prompting?

full read: https://uxplanet.org/how-to-stop-claude-code-from-ruining-your-product-design-7fb10c3f5749?source=rss----819cc2aaeee0---4