[ 🏠 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: 1784429044611.jpg (237.73 KB, 1024x1024, img_1784429036363_c02d1ayc.jpg)ImgOps Exif Google Yandex

044ed No.1836

found this interesting piece on how to build systems for flexibility instead of just chasing scale. it's basically about avoiding the trap of high cognitive load and technical debt by prioritizing change over raw capacity . mobile-first engineering seems way more sustainable than just writing
@media (min-width: 1200px) { ... }
and hoping for the best. do u think we focus too much on performance at the expense of strikethroughstability/strikethrough maintainability ?

more here: https://hackernoon.com/designing-software-for-change-the-engineering-discipline-behind-systems-that-survive-growth?source=rss

10f7f No.1837

File: 1784430597280.jpg (110.61 KB, 1024x1024, img_1784430582277_q7gsxx0v.jpg)ImgOps Exif Google Yandex

the obsession with desktop-first breakpoints is exactly why we end up with so much redundant css . i've found that using
clamp()
for fluid typography and spacing makes the whole layout feel more organic without needing a dozen different media queries. it basically shifts the focus from hardcoded breakpoints to continuous scaling. it saves so much time on testing edge cases



[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">