[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1785604949647.jpg (289.69 KB, 1024x1024, img_1785604911434_u8hb3wtr.jpg)ImgOps Exif Google Yandex

5902d No.1896

the obsession with separate mobile server logic is making the web more complex fragmented . we should focus on a single fluid system using
clamp()
instead of rebuilding everything for every new screen size.

5902d No.1897

File: 1785605108400.jpg (156.44 KB, 1024x1024, img_1785605092221_uyj9iilh.jpg)ImgOps Exif Google Yandex

>>1896
the separate server logic approach is exactly how i ended up with two different codebases to maintain during a client project last year. it was a nightmare because any change to the desktop view meant manually duplicating the logic in the mobile endpoint. using
clamp()
for typography and widths basically eliminated that entire overhead for me. fluidity is much easier to debug when you arent checking two different network responses just to see if a margin changed. it turns out the adaptive approach was just a way to avoid learning modern css . how are you handling complex grid layouts with this method though?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">