Mobile-First CSS: Is It Time for a Rethink?

Re:Mobile-First CSS: Is It Time for a Rethink? by grishka on Monday June 20, 2022 @07:02AM (#31808808)

All of this is built upon the misguided premise that the same markup could work both for mobile and for desktop. It can't unless it's text and images only. Different interaction paradigms call for different positioning of elements, different nesting, different density, etc. You do really have to have two sets of templates if you want to support mobile devices.

[ Parent | on HN ]

Re:Mobile-First CSS: Is It Time for a Rethink? by eyelidlessness on Monday June 20, 2022 @09:04AM (#31809857)

> Different interaction paradigms call for different positioning of elements, different nesting, different density, etc.

I’ve challenged this on HN before, but I’ll take a different approach. Can you describe a scenario where these fundamentally can’t be achieved with the same markup? I’ve never encountered one, in over a decade of developing responsive apps and sites.

[ Parent | on HN ]

Re:Mobile-First CSS: Is It Time for a Rethink? by grishka on Monday June 20, 2022 @03:51PM (#31814909)

For example, in my project, I have these two layouts, desktop and mobile: https://imgur.com/a/Jj7XcCO

They maybe can be done with the same markup, but it'd be much more work and some duplication, too. And of course it's absolutely unacceptable to redesign your UIs to make it easier to reuse markup — remember, developer experience doesn't matter if the end result is shit.

[ Parent | on HN ]

Re:Mobile-First CSS: Is It Time for a Rethink? by naniwaduni on Monday June 20, 2022 @07:15AM (#31808918)

It's easy to forget, but a lot of the web is text and images (and a lot of the rest would be better if it were).

Not all of it, sure, but more than our profession likes to make it out to be.

[ Parent | on HN ]