Re:Mobile-First CSS: Is It Time for a Rethink?
by dawnerd on Monday June 20, 2022 @01:46AM
(#31806732)
It’s kinda what happens when designers use 1024 or 1200 as desktop but don’t consider tablet at all. No one wants to spend the money on it so mobile ends up getting used up to wider desktop breakpoints. We’re guilting too if only showing desktop in tailwinds lg:*
Re:Mobile-First CSS: Is It Time for a Rethink?
by clairity on Sunday June 19, 2022 @07:27PM
(#31804546)
yah, i’ve found that there are a couple “natural” breakpoints that depend on min- / max-content, where things are single column under about 400-500px (~40-50ch), 2 or 3 column above that, and either width constrained above ~1200px or more content columns collapse up. we’re needing fewer and fewer media queries to accomplish this however, which is nice.
It's just as frustrating to use a site on a desktop that insists on a mobile layout until I make the window uncomfortably wide. (I assume this is tablet-focused design run amok.)
So, for a while now I've found it fruitful to regularly resize the browser between min and max width as I work (and sometimes vertically).
Rather than worrying about someone's device-size chart, I tend to build in more breakpoints focused on transitioning as the dimensions approach points where the content feels too crowded or too sparse, or where the UI/X affordances are creaking.
(Though this entails more of the regression testing that the source cites as a con.)