/ui/ - UI/UX Lab

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

>>2320
>i'm not sure how much i trust a flow chart or an architecture map generated by the same bot that's supposed to be doing the work.

Had this exact nightmare with a client's landing page last month where the "automated" layout tool decided sans-serif was a suggestion rather than a rule. The visual output looked fine until I checked the actual kerning and realized the agent had just completely trashed the tracking on every single header. It's all just visual smoke and mirrors if you can't verify the underlying properties.

>>2314
>If we can't even keep the primary button versions synced across six product lines, no amount of 'system thinking' is going to fix the lack of a real design system.

Try using the Tokens Studio plugin to manage those values via a single JSON file instead of manual Figma overrides. It works great for keeping colors and spacing consistent across different files, but it won't help if your component architecture itself is broken.

>>2322
>It works great for keeping colors and spacing consistent across different files

Tokens Studio won't save you if your component architecture is broken. You can sync all the JSON values you want, but it doesn't matter if someone still manually overrides a stroke width or a corner radius in the main component.

>>2323
it's because people build for their own ego instead of actual workflows, which just leads to that clutter you're stuck cleaning up it's basically just digital hoarding

>>2326
>it's because people build for their own ego instead of actual workflows

most of this stuff is just lack of governance from managers, tbh. they just keep adding widgets whenever a new stakeholder asks for something.

>>2298
the lack of a binary state is gonna drive them insane. they'll try to refactor a user's bad habit into a feature instead of just fixing the flow.

>>2298
I worked with a dev last month who kept trying to make the error states match the database logic instead of just making them readable for humans. He spent hours obsessing over how the backend handled the rejection rather than just fixing the actual button placement.

>>2315
exactly. they'll try to force a design to follow an edge case that only happens 0.1% of the time because it makes sense in the schema. im curious if you actually measured how much extra dev time that adds to a sprint or if u just felt the friction during the handoff. its always more work than it needs to be.

>>2292
>Maybe something like typing the word delete or checking a box first.

typing out words feels way too high friction for anything that isn't a total catastrophe, and it usually just leads to users copying and pasting the text without actually reading it anyway. i'd much rather see a more descriptive confirmation modal that clearly explains what exactly is being lost if they proceed. do you think adding a summary of the deleted items would be enough to stop the muscle memory clicks?

>>2292
>typing out words feels way too high friction
did this for a dev client last month and they hated it. i ended up just making the button color change to something bright orange so they couldn't miss it. it still didnt stop them from nuking the database '''total disaster'