/ui/ - UI/UX Lab

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.md

directly 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 manually 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

most of our current flows are just designed to 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

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?

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

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

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 phase

full read: https://uxdesign.cc/ia-for-ai-the-ux-of-contrast-battling-ai-fatigue-4f623495bed8?source=rss----138adf9c44c---4

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.

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

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

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