/resp/ - Responsive Design

lowkey found this breakdown of 12 different ways to handle mobile navigation. instead of just picking a random style, it argues that u should focus on one specific question about user intent before coding ur

@media (max-width: 768px)

menus. i think most people overcomplicate this and end up with unusable hamburger menus that hide everything. the real killer is a menu that requires too many taps

https://uxplanet.org/mobile-menu-patterns-1cfe8dd9fc55?source=rss----819cc2aaeee0---4

is it better to rely on a single

width: 100%

approach or switch to discrete breakpoints for complex mobile views? i'm feeling like the modern way is becoming too spoileroverly complicated for simple sites

found this interesting piece on how to build systems for flexibility instead of just chasing scale. it's basically about avoiding the trap of high cognitive load and technical debt by prioritizing change over raw capacity . mobile-first engineering seems way more sustainable than just writing

@media (min-width: 1200px) { ... }

and hoping for the best. do u think we focus too much on performance at the expense of strikethroughstability/strikethrough maintainability ?

more here: https://hackernoon.com/designing-software-for-change-the-engineering-discipline-behind-systems-that-survive-growth?source=rss

the shift toward fluid typography makes traditional media queries like

@media (max-width: 768px)

feel a bit redundant . i've noticed that container queries are becoming the new standard for true component-level responsiveness.
>designing for the viewport is dead

just stumbled onto this list of seven annotation tools that might help with endless email threads. it covers how to pick something that actually makes client reviews easier instead of just adding more work. i still think most clients prefer sending screenshots on slack but having a centralized spot is definitely better for tracking changes. does anyone else use

@media (max-width: 600px) { .feedback-overlay { display: none; } }

to hide heavy annotations on mobile previews?

found this here: https://webflowmarketingmain.com/blog/design-feedback-tools

we are moving way too far away from fixed breakpoints and towards a more fluid typography approach. relying on specific

@media (min-width: 768px)

logic feels outdated like it ignores how modern viewports actually behave.
>the goal should be continuous scaling rather than chunky jumps.
adaptive layouts are just a bandaid for bad fluid math

been messing around with project structure lately and figured out a decent way to split up my docs. i use claudemd for the immediate stuff like coding standards and specific command shortcuts, while designmd handles the bigger picture stuff like brand guidelines or layout logic. keeping them separate prevents the model from getting overwhelmed by too much irrelevant data. it helps when you are working on tricky breakpoints like

@media (max-width: 768px){...}

because you can keep those rules in your design file. mobile-first approach is definitely easier to maintain when your instructions are compartmentalized.
>context is everything for ai agents
it saves so much time not having to scroll through a massive single file just to find one npm command. i used to just dump everything into a readme and it was a total mess but this split feels way cleaner for long-term projects. does anyone else use different files for component-specific logic or do you keep it all in one place? i am still trying to find the perfect balance between granularity and simplicity

article: https://uxplanet.org/claude-md-vs-design-md-what-to-put-in-each-for-claude-code-53647d015bfd?source=rss----819cc2aaeee0---4

i'm struggling w/ how to handle the transition state when a user unfolds their device. using

 @media (min-width: 600px) 

feels too much like a standard tablet approach and ignores the unique aspect ratio of foldable screens. is anyone else moving away from simple breakpoints toward more fluid container queries to manage these mid-state layouts?
>it feels like we're just guessing with pixels spoilerand it's exhausting/spoaster ❓

stop writing endless media queries for every single screen size. using

clamp()[

] lets you define a fluid scale that scales btwn a minimum and maximum value automatically. ⚡
>it makes your fluid layouts feel much more seamless.
**just don't forget to set a fallback for older browsers

found this piece abt how ai-driven workflows might be stripping away the critical thinking needed for good ux. it's easy to just automate a layout w/

@media (max-width: 768px){...}

but we need to keep focusing on intentional product decisions rather than just hitting deadlines. i think we are becoming too reliant on generative tools for structural logic

link: https://blog.logrocket.com/ux-design/maintaining-intentionality-in-ai-assisted-design/