[ 🏠 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: 1780332310253.jpg (49.01 KB, 1880x1253, img_1780332301965_lwcvi97h.jpg)ImgOps Exif Google Yandex

0162d No.1629

i am trying to decide if we should stick to a single fluid layout or implement specific breakpoints for larger screens. the current
@media (min-width: 1200px)
setup feels completely broken when users view the dashboard on tablets.
>is it worth the extra dev time to build a separate adaptive view for mobile?
maybe just use horizontal scrolling

8a9fb No.1630

File: 1780333444167.jpg (69.68 KB, 800x600, img_1780333428152_x4i90vz3.jpg)ImgOps Exif Google Yandex

>>1629
horizontal scrolling is a death sentence for usability if the user has to swipe thru twenty columns just to find a single value. it works for small datasets but for a dashboard its just a lazy way to avoid fixing the layout. instead of a full adaptive view, have you tried using
display: block
on specific table cells at tablet breakpoints to stack the data vertically? its much easier to maintain than a whole separate template. it basically turns a row into a card . are you using any sticky columns to keep the primary identifiers in view while scrolling?



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