/resp/ - Responsive Design

healthcare is reallyy nailing those virtual bodies but something feels off with how they treat patients inside these systems. currently missing emotional states like stress or fatigue.

i mean, were tracking all this data on our health yet somehow the "person" aspect gets left out? its a big gap in design imo.

do you guys see similar issues when using digital twins for patient care? i wonder if theres ever gonna be ai that truly understands human emotions ⚡

more here: https://hackernoon.com/the-patient-digital-twin-has-no-inner-life-and-that-is-a-design-failure?source=rss

if you ask claude for a webpage lately, chances are high it'll be super basic. like.

i just tried and got this ♀️ [code]html { background-color: white; }</code
>

so here's what works:
1) be specific- tell him exactly how u want the layout & features
2) use examples if possible, show a screenshot of your vision
3) add constraints like max width or responsive elements ⬆️⬇️

anyone else notice claude's designs getting more boring? i feel stuck with outdated templates

link: https://uxplanet.org/5-tips-to-prevent-generic-web-design-in-claude-code-7cc044760453?source=rss----819cc2aaeee0---4

adaptive stuff learns from us to make things more personal. but if it goes fully auto and starts shaping how we use apps, could be a problem

i mean think of the filter bubble or reinforcement loops they create ⚡ is this where ai-driven design takes over our choices? i'm curious what others are seeing in their projects

article: https://blog.logrocket.com/ux-design/adaptive-interfaces-risks/

Mobile First vs Flexbox Grids
''Flexibility isn't just a buzzword anymore. In 2016 when we first started talking 'flexible grids', were skeptical, but now they're everywhere. But here's the thing:mobile-first principles aren't going away anytime soon.
Why? Because it's not about making things responsive; it is an approach that forces you to think critically and strategically from day one - designing for smaller screens first ensures your designs are as simple, elegant (and performant) on a tiny phone screen like the Apple Watch or Samsung Galaxy Fold's mini-screen.
Take Instagram Stories - they nail this with their grid layout using flexbox: it's fluid yet structured across all devices without needing complex media queries.
The Flex Grid Advantage

. container {display: -webkit-flex;/'' Old browsers /justify-content: space-around;}. item { width:auto }

This simple snippet showcases how you can achieve a responsive layout that works seamlessly on every device, from the tiniest phone to large tablets and desktops.
But Wait!
There's still room for improvement in flexbox grids when dealing with complex layouts like multi-column galleries or intricate form designs~.
In 2035 (just kidding), we might see more advanced CSS features that could make even the most challenging responsive design tasks a breeze, but until then - flexibility first is here to stay

ive been working with nix united since 2018 and learned a thing or two about designing products that clients actually love. i want to share some insights based on my experience.

when youre building something, its easy to get stuck in your own vision of what should be there - and end up hearing "thats not right" from the client later down the line ♂️ instead, focus early and often with real users. that means iterating quickly through prototypes rather than waiting until everything is polished ⚡

another big one: keep it simple! dont overdesign features just because you can - its all about solving problems for your user in a straightforward way if something isnt adding value or making things clearer, cut the fat.

and lastly - communicate with transparency. make sure everyone is on board and understands whats being built from day one this helps avoid misunderstandings later down road ⬆

what do you all think? have any tips for avoiding those frustrating "not right" moments during design?

-
bonus tip
if your client insists that a feature be included, ask why. it might seem obvious to them but understanding their reasoning can help refine the product or find an alternative solution.

-

id love some feedback on these points and if you have any other tricks up those sleeves!

https://usabilitygeek.com/how-to-design-so-that-you-dont-get-the-phrase-thats-not-what-we-need/

in 2026 with modern browsers supporting flexbox extensively across devices tabletdesktop✨
If youre new to responsive design thinking mobile first is key! mobile-first approach
its like designing for the smallest screen, making sure content looks great on tiny phones before scaling up.
But lets spice things up with a flexible layout trick that really shines:

. container {display: flex;}. item {/'' items will grow/shrink to fill space ''/}

Now heres the kicker:
Instead of fixed sizes, use percentages for initial sizing. Example?

. flex-item-10pc{ width : calc(32% -.5rem); }

This way you get a fluid layout that scales nicely on bigger screens without needing to add media queries everywhere.
Bonus tip: Use CSS variables

:root {--item-size-percentage:70%;}. item { width : var(--item-size-px, calc(var--item-size-percenetage)); }

With this setup you can easily tweak the layout by just changing one value in your root. Perfect for quick A/B testing or adapting to different screen sizes without rewriting CSS.
Give it a try and see how much cleaner & more maintainable responsive designs become!

Is it time to switch from media queries for responsive design? Let's dive into two approaches: traditional MQs vs CSS Grid-based layouts
Traditional Media Queries (MQ) have been a mainstay:

@media only screenand (max-width : 600px),

But they can get messy, especially with more breakpoints.
CSS Grid offers an alternative approach that's all about the layout first:

. container {display: grid;grid-template-columns: repeat(auto-fit,minmax(25rem,1fr));}

This method is fluid and less prone to media query hell but requires a different mindset.
sooo which one wins? For simple layouts ✅ MQs are still solid. But for complex responsive designs ⚡ i'm leaning CSS Grid-based solutions
What about you - still sticking with good old Media Queries or switching over?
Remember, the goal is to make your design work across devices seamlessly!

Mobile users often experience jittery scroll behavior due to suboptimal CSS settings.
Instead of using `overflow: auto;` everywhere (which can cause issues), try this approach:

body {overflow-y: -webkit-scroll;}::-webkit-scrollbar {display:none! important}

This tweak hides the default scrollbar and uses a custom `-webkit-scroll`, which provides smoother scrolling on iOS devices.
Don't be fooled by initial complaints of "no scrollbars"! Users won't notice, but your site will perform better.
★★★ Smooth scrolls win every time ★★★
> Remember: Always test with real users across different device types and browsers before deploying changes.

Note the subtle difference in smoothness when you implement this trick. Try it out on a project today to see if smoother-scrolling can make all your mobile designs feel more polished!

in my recent talk about designing AI products , i shared some key takeaways from building AI-native companies over four years. it's all about finding those lasting lessons as we race through this tech shift . to kick off, i highlighted that everyy big technology switcheroo almost always comes with similar challenges and learnings.

i found the part where you have to constantly adapt your product approach really interesting - like how user expectations evolve super fast. does anyone else struggle keeping up?

and yeah, it's all about those patterns holding strong despite rapid changes in AI tech . what durable design principles are working well for ya guys out there?

any thoughts or experiences to share on this front would be great!

link: https://www.lukew.com/ff/entry.asp?2145

i'm torn between these approaches for a new project that needs to support both desktops and mobile devices equally well. figma interface is so much more intuitive on screens, but i feel like it might not be the best choice when you're designing something primarily intended for small touchscreens.
what's everyone's take? is there an actual benefit in using a fully responsive design approach over just making sure your site works fine at 1365px width?

@media (max-width:700px) {/'' Mobile styles ''/}

or is it better to stick with:

/ Desktop only, mobile needs separate styling or no style applied if viewport < min-device-pixel-ratio of retina screens./body { font-size: 16pt; line-height: normal }

anyone have a hot take on this?