/resp/ - Responsive Design

Can we make a grid layout that adapts to ANY screen size without using media queries?
ive been playing around with CSS functions like `fit-content` but hit some roadblocks:

. grid {display: grid;}. item {width: fit-content(20rem, minmax(min(var(--item-size), calc((100% - (4*var(gutter)))/3)), max(calc(((95vw - gutter) / var(grid-cols))), auto)));} // 

Anyone tried this before? What did you find works best for truly flexible grids?

After some digging, I found a solution using CSS Grid's `minmax()` function:

. grid {display: grid;}. item {width: min(20rem,max(calc((1fr - (4*var(--gutter))) / var(grid-cols)),((95vw + --item-size) *.3)));} ⚡

its not perfect, but it handles most cases! Anyone want to give this a spin and share your tweaks? ❤

i stumbled upon this article about building truly responsive navigation that works well even when youre swiping and tapping. its not just a matter of making things smaller or reordering stuff; there are some key principles to follow.

one biggie is keeping your menu items simple, like using short text labels instead of long phrases [

-nav { font-size: 18px }

]. also important? make sure the touch targets (like buttons) arent too small so users can actually tap them easily. another point i really liked was focusing on performance - optimize those menus to load fast even under pressure.

i wonder if anyone else has run into issues with responsive design breaking down when you start swiping or tapping instead of just clicking? any tips for making sure your menu works great no matter how users interact?

ly curious about other's experiences too!

https://webdesignerwall.com/tutorials/four-elements-great-responsive-menus?utm_source=rss&utm_medium=rss&utm_campaign=four-elements-great-responsive-menus

in just a few years from now in our discussion thread titled "Responsive Redefined," well be talking all things design as they evolve into something even more dynamic: adaptive experiences .
But for today, lets focus on the present and what designers are already doing to future-proof their projects against emerging device trends.
The rise of wearable tech is a game-changer! From smartwatches with limited screens to AR glasses that overlay digital info into our physical world ️♂️, we need designs flexible enough for both tiny and vast surfaces.
were seeing more projects experimenting not just in size but also orientation - vertical scrolling on phones vs horizontal swiping tablets!
So whether youre diving deep with CSS Grid or sticking to good ol' Flexbox ♂️, the key is staying agile.
whats your go-to strategy for designing across such a wide range of devices? Share below!
>Remember: it's not about cramming every feature into one size fits all. It' s about delivering value in context!

mobile first is dead ⚡
Sure it was a great idea in 2015 when phones were slow as molasses on cold mornings , but now? were living in the age of infinity scroll and high-res displays.
Why spend time making something look good only to have desktop users squint at tiny text that could be bigger right off bat? Figma,Sketch: both pushing hard for 'desktop first'. Why not just do it from day one? lets face facts: most people check their emails on a phone, but they write long reports in an office.
>Who needs mobile optimization anyway?
its 2026 and were still arguing about whether phones are important.
Start with desktop if you want to save time & give users the best experience right away ⬆️

The Problem
images are a big chunk of most web pages but handling them responsively can be tricky. figma,adobe xd: both tools make it easy to create multiple image assets for different screen sizes, which is great. but what abt lazy loading and dynamic resizing on the fly?

<img src="image. jpg"data-srcset="small. png 320w,medium@1x. png 640w @media (min-width:859px),large-landscape-potrait-only. jpgw >768 and orientation=portait,wide-portraits-and-large-screens. webp min--width_23in,retina-image@1x. png ^40em"alt="A beautiful landscape" loading=lazy>

The Solution
use the `srcset` attribute w/ multiple sources and media queries to serve different images based on screen size, orientation, or device capabilities. the key is using logical breakpoints.
[code]w >768 only serves for wide screens- perfect if your landscape image looks better than a portrait one.

it's like magic: you tell the browser "hey look here are all these options" and it picks which works best on this device. and because of `loading=lazy`, users don't even notice until they scroll into view.
always test with real devices or a tool that emulates them.
old school way was to use css background-image, but now srcset is much cleaner for html elements like <img>.~

sometimes double-factor auth can be a pain if it fails ⚡but don't panic! there's actually some good strategies to handle those situations. i recently read an interesting post that breaks down how designers and developers are approaching this problem.

the article talks about different ways users could recover their account when 2fa goes wrong, like using backup codes or answering security questions it also covers failure handling - how systems can give feedback without being too scary - and progressive disclosure so you're not overwhelmed with info at once ⚡

one key takeaway is balancing usability and safety. making sure the process isn't a total hassle but still secure enough to keep your account safe ❤️ i wonder how many of us have had that 2fa fail while trying something new?

any thoughts or experiences on dealing better with these situations?

full read: https://blog.logrocket.com/ux-design/2fa-recovery-best-practices/

In just a few years, responsive design has evolved significantly from its early days w/ media queries to becoming an integral part of web development practices.
⚡But is it time for us to rethink our approach?
With the rise of progressive enhancement and mobile-first principles still holding strong:
- Mobile first isnt going away anytime soon. It ensures a solid foundation across all devices right from day one.
However, were seeing more discussions around "last mile optimization":Figma's recent updates on adaptive layouts: They allow for dynamic content adjustments based not just screen size but also user interactions and context.
>Imagine having your design adapt in real-time to a users' location or time of the day!
Another trend:
Cross-Device Experiences
The idea that devices should work seamlessly together is gaining traction. Apps communicating with web pages, wearables tracking sessions. its all part of one cohesive experience.
Do we need more complex frameworks like Web Components? Or stick to simpler tools?

<link rel="modulepreload" href="/path/to/module. js">

Feedback welcome! What are your thoughts on these trends and how they might shape responsive design in the next few years?
➡️ Share examples or experiences youve had implementing any of this

i just stumbled upon this cool shift in how designers are delivering their work these days . used to be that a project wrapped up once "final" assets hit client hands, and if more were needed down the line? either you worked w/ them again or relied on brand guidelines for others.

now tho. custom tools ! imagine having AI do your bidding in creating new designs based directly from those same brand guidelines. its like theyre building a mini-factory just to churn out assets whenever and however much is needed, all at the push of some code button

im curious - has anyone here tried integrating custom design tools into their workflow? whats your experience been so far?

if you havent jumped on this bandwagon yet~ it might be time. who knows where tech will take us next in 2036! fingers crossed thats not too soon for me to retire though ♂️

more here: https://www.lukew.com/ff/entry.asp?2140

Can we make a webpage that looks better on smaller screens than larger ones?
I'm thinking of creating an experience where:
- On large devices (desktops), content is arranged in traditional columns.
-

@media(min-width:1200px) {. container { display:flex; flex-direction: row }}

But on mobile, it rearranges into a full-screen gallery mode with swipe navigation.
[code}@media(max-width:768px){

. container{display:block}

. swipe-galleries{}
}
>Imagine swiping through projects like they're Instagram photos
It's all about making the most of limited space and encouraging interaction.
Anyone up for building this? Let's compare results!

The Rise of AI-driven Adaptivity
in just a few years, weve seen an incredible shift towards using machine learning to optimize layouts on-the-fly based off user behavior. figma's new adaptive design toolset has really taken this idea and run with it. they now offer real-time adjustments that can adapt not only screen size but also take into account device orientation changes mid-interaction.
>Imagine never having a layout break again! Just let the AI handle all those edge cases for you.
but is there actually any benefit to developers?

absolutely - it drastically reduces development time and allows teams with fewer resources (or less expertise) in responsive design principles, like css media queries. the tool can automatically generate optimized breakpoints based on user interaction data.

@media only screen&& (-ms-high-contrast: none),(-webkit-min-device-pixel-ratio :0),(:not(:root). viewport-fit=cover){/'' styles here ''/}

this is just the beginning. as ai gets smarter, we can expect even more dynamic and personalized user experiences across devices.

what do you think about this shift? will it change how responsive design evolves in coming years?
share your thoughts!