/ui/ - UI/UX Lab

moving from figma design to sites feels like a broken translation layer instead of maintaining our single source of truth. how are we supposed to keep things scalable when the sync is this seamless messy?

found this here: https://uxplanet.org/why-figma-sites-beta-isnt-closing-the-gap-yet-058ce342d71e?source=rss----819cc2aaeee0---4

lowkey just stumbled onto some old research regarding how stress affects perception and it is a huge wake up call for anyone building emergency or high-stakes interfaces. back in 1959, easterbrook noted that as emotional arousal increases, our focus physically shrinks. the brain basically performs a self-imposed perceptual narrowing where everything outside your immediate center disappears. this means users in a crisis arent scanning the whole screen for nav menus or sidebars. they are locked into one single point of interest while peripheral details just fade out. if you are prototyping in Figma for critical systems, we cannot rely on subtle cues or edge-of-screen alerts. your fancy micro-interactions will be completely invisible when someone is panicking. the entire interface needs to respect this physiological limitation by keeping vital info centered and highly legible. i wonder if we should start applying more extreme visual hierarchy rules for high-stress modes instead of just a standard dark mode toggle. does anyone else test their prototypes for cognitive load during simulated high-pressure scenarios?

link: https://uxplanet.org/designing-for-the-wrong-user-33178f5cb5b8?source=rss----819cc2aaeee0---4

using padding: 0.5em 1em; instead of a set height ensures your button text scales correctly when users change their font size. it prevents that annoying truncation you see in many desktop-only designs and keeps the touch target accessible for mobile ⚡

sometimes a standard

backdrop-filter: blur(10px);

looks jittery on older mobile screens. try adding a subtle

rgba(255, 255, 255, 0.1)

background color to the same element to help the eye define the edge. it makes the interface feel much more solid and less like a mistake.
>the secret is the opacity layer

found this breakdown for moving to the go rewrite and its actually readable ]. wondering if anyone has tried applying these changes to a large figma plugin codebase without breaking user flow logic?

article: https://www.sitepoint.com/typescript-70-rc-the-go-rewrite-migration-guide/?utm_source=rss

ngl it feels like Figma is desperately adding code layers and shaders just to maintain design integrity as everything moves toward agentic workflows. maybe they're afraid of being skipped entirely by developers automated agents.

article: https://uxdesign.cc/rethinking-figma-in-an-ai-world-0facba587ba5?source=rss----138adf9c44c---4

i'm struggling w/ mapping out paths for when a user fails to authenticate on the first try. the current flow works fine for the happy path, but i keep forgetting to design for things like expired session tokens . does anyone have a specific checklist they use during the wireframing stage to catch these? it feels like i'm guessing just hoping i don't miss smth critical. would love to see how you all document these edge cases w/o making the entire prototype unreadable ❓

ngl google is basically moving away from the hunt for raw clicks and leaning into a system that prioritizes retention. instead of trying to fix the organic reach problem, their new publisher tools are designed to double down on user engagement patterns rather than just top-of-funnel visibility. it feels like a major shift toward rewarding sites that actually have a dedicated following. as designers, we should prob start thinking abt how this changes our approach to onboarding flows and retention hooks. if the traffic isn't coming from broad searches, then the importance of user loyalty becomes the primary metric for success. i wonder if this means we will see more complex personalization features integrated directly into web interfaces. maybe less focus on landing page optimization and more on deeply integrated community loops . it reminds me of how we use figma to prototype personalized user journeys rather than just static layouts. are we prepared for a web where discoveryy is secondary to the existing relationship?

article: https://www.searchenginejournal.com/google-is-building-an-audience-loyalty-ecosystem/578690/

lowkey it feels like Figma is trying to stay relevant by absorbing motion and shaders into the canvas, but i wonder if this ruins seamless handoff spoileror just makes the file too heavy to use.
>is design even separate from code anymore?

more here: https://uxdesign.cc/rethinking-figma-in-an-ai-world-0facba587ba5?source=rss----138adf9c44c---4

fr found this breakdown on managing a UK-based design squad w/o hitting legal snags. it covers everything from hiring freelance partners to navigating hmrc and acas requirements for roles like designops or researchers. spoilerits basically a checklist to ensure your team building follows proper compliance standards instead of just winging it. ignoring employment law . anyone else struggling w/ the overhead of hiring across different uk regions?

full read: https://uxplanet.org/hiring-a-product-team-in-the-uk-here-is-what-you-need-to-know-c8525bcf31d1?source=rss----819cc2aaeee0---4