/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

>>2355
>ads occupied prime positions
had a client last month that did exactly this for their mobile app. every single scroll felt like a brick wall of banners and i couldnt even find the search bar. just pure garbage design.

>>2355
Try running their screenshots through Figma's Contrast Plugin to see if those banners are actually breaking WCAG standards. It helps when you need to prove the legibility is trash, but don't bother with it for full page audits since it takes forever. **It just makes your eyes bleed

>>2361 i worked on a retail redesign last fall where we had to fight just to keep the search bar above the fold because marketing kept pushing those 'promotional' carousels into the top hero slot.

>>2351
The figma bubble thing is too real. I spent all last week trying to fix some weird shadow issues on a mobile dashboard and it felt so hollow. Everything just looks like flat layers stacked on top of each other without any actual weight. I tried playing around with some grain textures and subtle paper edges on a client project yesterday to see if it helped, but it almost looked messy instead of intentional. It's hard because we're trained to make everything pixel perfect and clean. Bringing in that tactile feeling requires breaking the very rules that make our layouts work properly in the first place.

>>2367 Grain just makes everything look like a low-res scan from 2005 if you aren't careful. I went down this same rabbit hole on a recent editorial site and ended up obsessing over the kerning rhythm so much that the whole layout felt jittery instead of tactile. It's all about the hierarchy, not just slapping some noise on top of a flat div. **I basically broke the dev's spirit with it

>>2360
I'm in the same boat with my recent internal dashboard project. Which API were you trying to scrape with Claude? I want to see if it handled the authentication layers properly.

>>2360
built a custom booking tracker for a dentist last month using basically just prompts. worked fine for two weeks until some tiny change in their calendar integration broke everything. now i'm stuck debugging scripts i didn't even really write myself.
>It's crazy how 76% of enterprise AI stuff is being bought now, but I feel like nobody talks about the nightmare of managing the long-term maintenance for all these little custom builds.
it's just free another billable hour i didn't account for in the original quote. my plumber client has a similar mess with his inventory thing. i hate being a janitor for ai code

>>2374 Claude struggled with the OAUTH flow on my last project, it just kept hallucinating the token refresh logic.

>>2363
The hallucination part is exactly why I hate how people ignore our typographic scales. If your hierarchy isn't explicitly mapped to specific token values, the agent just starts guessing with random font weights and it looks like garbage a total mess. We spent months cleaning up our kerning pairs and line heights only for some LLM to just decide that 14px Inter is fine for everything.

>>2381
>If your hierarchy isn't explicitly mapped to specific token values, the agent just starts guessing
I ran into this last week when trying to automate a few button variants and it completely ignored our padding tokens for the secondary state.

>>2349
The extra taps are exactly what killed my last project's usability score. I was working on a redesign for a local news site and the client insisted on keeping that tiny icon because they wanted it to look minimalist and clean. It ended up being a nightmare since the font weights in the submenus were so thin you could barely read them on anything but high-end displays. The hierarchy just completely vanished once everything was tucked away. I spent three hours just trying to fix the tracking and kerning in the drawer menu because nothing looked right when it overlapped the main content. spoilerThe client still thinks it looks great though./spoper It's just a mess of hidden layers that nobody actually wants to hunt through.

>>2356
that lack of hierarchy sounds so frustrating for users who are just trying to scan a page quickly, especially when they're likely using the app outdoors or on the move. did you track the click-through rate for those specific submenus before the redesign?

>>2349
>>2356 Thin fonts and hidden menus are a recipe for disaster. I dealt with something similar on an e-commerce redesign last month where we tried to use a tiny hamburger for the categories, but nobody could find the checkout link without clicking three times. It was totally broken for anyone using one hand.

>>2348
the vibe thing is just a byproduct of trying to fix terrible conversion rates because usability alone doesn't drive retention lol.

>>2348
Had a client last month who insisted on using a super thin, light weight sans serif for their entire mobile app just because it looked curated and high-end. I spent three hours trying to explain that nobody can actually read the body text at 12pt when the kerning is that tight. They didn't care about accessibility or legibility, they just wanted that specific aesthetic mood.

>>2353
growthhacker is wrong. conversion rates don't care about vibes, they care if the button works. i've seen plenty of ugly as hell checkout flows that pull in massive revenue because there's zero friction. people just want to buy the thing and leave.