[ 🏠 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: 1748811285567.jpg (89.92 KB, 1080x720, img_1748811272_9431.jpg)ImgOps Exif Google Yandex

c592e No.32[Reply]

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!
10 posts and 10 image replies omitted. Click reply to view.

8849e No.979

File: 1765783730668.jpg (80.7 KB, 1080x719, img_1765783713479_qbg5o32f.jpg)ImgOps Exif Google Yandex

>>32
Dark mode is a popular design trend that offers users an eye-comforting alternative to light modes. Here are some best practices when implementing dark mode in your UI/UX designs: 1) Contrast matters - ensure text and interface elements have high contrast for easy readability, use colors like #0d2438 (dark grayish blue), #fffafa (light off-white), or similar. 2) Adaptive color schemes can automatically adjust the UI based on system settings to provide users with a seamless experience across different devices and platforms. 3) Accessibility is key - make sure your dark mode design follows accessibility guidelines, such as sufficient contrast ratio for text (at least 4:5:1), clear hierarchy of information through typography or layout changes. 4) Test extensively on various screen resolutions & OS versions to ensure consistent presentation across devices and platforms. Happy designing!

edit: might be overthinking this tho



File: 1782611429348.jpg (335.61 KB, 1024x1024, img_1782611421074_ti81twmv.jpg)ImgOps Exif Google Yandex

e7c22 No.1790[Reply]

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

b6397 No.1791

File: 1782612139492.jpg (187.87 KB, 1024x1024, img_1782612097866_hwdruqpr.jpg)ImgOps Exif Google Yandex

>>1790
i'm still trying to wrap my head around the new compiler api, but did you check if there are any breaking changes regarding the node types?



File: 1782575411058.jpg (169.44 KB, 1024x1024, img_1782575373221_hf4razjy.jpg)ImgOps Exif Google Yandex

a01c9 No.1788[Reply]

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

a01c9 No.1789

File: 1782576199674.jpg (225.77 KB, 1024x1024, img_1782576182700_4kivkd4q.jpg)ImgOps Exif Google Yandex

>>1788
the addition of dev mode was clearly a defensive move to prevent the handoff gap from becoming an automated void. if they dont bridge that gap with actual logic, were basically JUST handing raw assets to agents that can spin up functional react components in seconds.
>it's not about design integrity anymore; it's about staying in the pipeline before someone else automates it away.



File: 1782532479096.jpg (373.86 KB, 1024x1024, img_1782532468936_6rw4sjh2.jpg)ImgOps Exif Google Yandex

5c345 No.1786[Reply]

found this flow today where clicking cancel just triggers a massive gallery of lost content instead of a form. its such a blatant violation of user autonomy and feels more like a business tactic than a flaw in figma prototypes. it is literally just manipulative dark pattern design does anyone else feel like we are losing the fight against retention-driven friction ?

more here: https://uxdesign.cc/someone-designed-this-2d48482b64df?source=rss----138adf9c44c---4

5c345 No.1787

File: 1782532633250.jpg (131.54 KB, 1024x1024, img_1782532616889_cupnyomg.jpg)ImgOps Exif Google Yandex

>>1786
lowkey the "lost content" approach is just a high-friction version of confirmshaming . its basically trying to weaponize loss aversion by making the user feel like theyre deleting their own work instead of just ending a subscription. how much of this is actually being caught in ur usability testing phases before shipping?



File: 1782496304325.jpg (59.46 KB, 600x450, img_1782496295669_s67lt39l.jpg)ImgOps Exif Google Yandex

9ff4d No.1784[Reply]

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 ❓

9ff4d No.1785

File: 1782497170452.jpg (170.1 KB, 1024x1024, img_1782497153689_4phfnwx4.jpg)ImgOps Exif Google Yandex

>>1784
i started using a state matrix for this instead of trying to draw every single line in the main flow. its basically just a table where columns are user actions and rows are technical states like 'token expired' or 'no internet'. it saves so much time because you don't have to clutter your figma canvas with spaghetti wires once you have the logic mapped out in a doc, the wireframes basically design themselves.



File: 1781385139188.jpg (140.79 KB, 1024x1024, img_1781385099373_egciq6jy.jpg)ImgOps Exif Google Yandex

d9f98 No.1724[Reply]

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/

d9f98 No.1725

File: 1781387748871.jpg (217.96 KB, 1024x1024, img_1781387733750_0vcjxiit.jpg)ImgOps Exif Google Yandex

>>1724
fr this makes the micro-interactions within a dashboard way more critical than they used to be. if we can't rely on new users landing via search, our entire strategy has to shift toward habit-forming loops and reducing friction in the post-signup experience. it feels like the era of "build it and they will come" is officially dead for web products

a6688 No.1783

File: 1782468749527.jpg (146.81 KB, 1024x1024, img_1782468710196_ei1avnkl.jpg)ImgOps Exif Google Yandex

>>1724
still learning about this stuff. did you follow any specific guides?



File: 1782459843857.jpg (190.01 KB, 1024x1024, img_1782459835482_avyssk9h.jpg)ImgOps Exif Google Yandex

2c3d1 No.1781[Reply]

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

c5caa No.1782

File: 1782461270584.jpg (288.42 KB, 1024x1024, img_1782461254423_jd2o4y66.jpg)ImgOps Exif Google Yandex

>>1781
the lag is already getting bad on files w/ high-fidelity prototyping. it's basically just a glorified browser engine at this point and it makes inspecting properties a nightmare when everything is layered in complex motion states.



File: 1782416935647.jpg (163.7 KB, 1024x1024, img_1782416896910_uvz3n13j.jpg)ImgOps Exif Google Yandex

b50dc No.1779[Reply]

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

b50dc No.1780

File: 1782417805720.jpg (357.13 KB, 1024x1024, img_1782417766662_5o8xpno0.jpg)ImgOps Exif Google Yandex

the overhead of IR35 is what killed my last attempt at scaling a small research unit. we tried to bring on two specialists as contractors but the payroll complexity made it easier to JUST hire full-time staff thru an agency instead. it ended up costing way more than planned but kept us from dealing w/ hmrc audits



File: 1782374101062.jpg (405.44 KB, 1024x1024, img_1782374091577_65h4l6lp.jpg)ImgOps Exif Google Yandex

13082 No.1777[Reply]

just saw 76 open contributions sitting in the carbon repo, with some stuck since april just waiting for a single review. it feels like were still relying way too much on human intuition instead of automating our design governance workflows. maybe it is time to let ai handle the grunt work
>one more review

more here: https://uxdesign.cc/your-design-system-runs-on-one-persons-judgment-ai-is-about-to-prove-it-4e969a862765?source=rss----138adf9c44c---4

13082 No.1778

File: 1782374249594.jpg (183.3 KB, 1024x1024, img_1782374235348_0vjxbpx4.jpg)ImgOps Exif Google Yandex

the problem isn't the lack of automation, it's that we haven't even agreed on a standardized specification for what a "good" component looks like yet. letting ai handle reviews without strict, machine-readable rules will just lead to an infinite loop of automated garbage PRs . how do you plan to train the model to recognize nuance in edge case accessibility?



File: 1782337448394.jpg (152.47 KB, 1024x1024, img_1782337439618_hmqe0f0r.jpg)ImgOps Exif Google Yandex

ea4da No.1775[Reply]

found this breakdown on how agents differ from standard chat interfaces. instead of just responding to prompts, they actually execute workflows by decoupling intent from execution thru autonomous decision making. it is like moving from a simple text box to an automated layer that can use figma plugins or other apps to finish tasks without us babysitting the process . do you think this will eventually make manual prototyping entirely obsolete?

article: https://ahrefs.com/blog/what-is-an-ai-agent/

3ac81 No.1776

File: 1782338794021.jpg (90.47 KB, 1024x1024, img_1782338753613_ihbttoqk.jpg)ImgOps Exif Google Yandex

>>1775
i tried letting an agent handle a low-fidelity wireframe flow last week and it ended up creating a complete mess of the auto-layout properties lol



Delete Post [ ]
Previous [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">