[ 🏠 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.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1780130173882.jpg (64.15 KB, 1080x810, img_1780130166916_eaxljajj.jpg)ImgOps Exif Google Yandex

45147 No.1620[Reply]

hey there! i just stumbled upon a neat way to handle font sizing in different devices that doesn't involve using any css media-queries. it's all about utilizing viewport units, specifically
vw
, and some clever nesting with ems.
basically u set ur base text size as an absolute pixel value or rem (root-em), then nest media queries inside the parent element to adjust for smaller screens without needing complex mq rules everywhere:
p {font-size: .875rem; /* start at small screen sizes */}@media only all and (-webkit-min-device-pixel-ratio :0) {p{font size:.9em}/* tweak on tablets, adjust as needed */}

the key is to keep ur main styles simple with pixels or root ems then just fine tune where necessary. it's a bit of extra work but keeps the code clean and easy maintainable!

45147 No.1621

File: 1780130867513.jpg (142.11 KB, 1080x720, img_1780130852964_68sj57zq.jpg)ImgOps Exif Google Yandex

i've found that using viewport units can indeed be a clever workaround, but i wonder how well it scales across different font families and their varying widths! have u tested this approach w/ sans-serif vs serif fonts?
>what about fallbacks for older browsers not supporting vw/vh values? hidden until hovered might come in handy there.



File: 1779971512552.jpg (154.54 KB, 1280x844, img_1779971504543_espbax6g.jpg)ImgOps Exif Google Yandex

d00d2 No.1611[Reply]

responsive design isn't just abt media queries; use relative units like % and vh/vw for font sizes, margins & padding. this ensures elements resize gracefully on different devices.
__remember to test thoroughly across all screens

36466 No.1612

File: 1779972633695.jpg (48.48 KB, 800x600, img_1779972619839_j19i09ok.jpg)ImgOps Exif Google Yandex

i'm curious about how you test across different screens? do u have a go-to method for that?
>how often would you say you need to adjust % values vs vh/vw units in practice?

36466 No.1619

File: 1780109929679.jpg (124.5 KB, 1080x720, img_1780109915748_hiz1d1pu.jpg)ImgOps Exif Google Yandex

>>1611
agree! i've seen layouts crumble when fixed widths are used on smaller screens, but switching to % and vh/vw really helps keep things smooth across devices especially for images- using max-width: 100% makes sure they scale nicely without distorting. have you had any tricky responsive design issues recently?



File: 1780087502768.jpg (81.73 KB, 1880x1253, img_1780087495136_vsqkgyxk.jpg)ImgOps Exif Google Yandex

6d3c1 No.1617[Reply]

hey everyone! ive got a challenge for you all that involves some clever thinking and responsive magic.
can someone create an element with
display:none;@media (max-width : 601px){}
in the larger viewport, but make it appear only on screens smaller than 752 pixels using pure css? share your solution!

6d3c1 No.1618

File: 1780087625436.jpg (226.07 KB, 1080x720, img_1780087611215_47dzazy4.jpg)ImgOps Exif Google Yandex

can u share how this works on different devices? i'm curious to see it in action! SECTION HEADER media queries are tricky but fun when they click into place. Have any tips for debugging responsive designs that just won't cooperate?



File: 1780050968645.jpg (100.06 KB, 1080x809, img_1780050960174_2gs8yzxw.jpg)ImgOps Exif Google Yandex

4859b No.1615[Reply]

Been thinking about this lately. whats everyone's take on responsive design?

82c27 No.1616

File: 1780051532463.jpg (290.8 KB, 1080x809, img_1780051516437_khgk4l5j.jpg)ImgOps Exif Google Yandex

i've found that using both can give you more flexibility in how elements resize and reflow on different screens, but make sure to test thoroughly across devices to catch any unexpected layout shifts . have u tried either method yet? if so, what worked for ya!



File: 1780008040139.jpg (158.03 KB, 1080x703, img_1780008032192_6hnqqovb.jpg)ImgOps Exif Google Yandex

5b3ab No.1613[Reply]

lowkey both have their merits but adaptive is better for simpler sites where devices are grouped into a few common screen sizes, using media queries to adjust styles. responsive uses single fluid grid that scales down and up across all screens - more flexible in handling the wide range of modern device resolutions w/o needing separate breakpoints

5b3ab No.1614

File: 1780008153982.jpg (234.42 KB, 1880x1249, img_1780008138314_y1aruwkp.jpg)ImgOps Exif Google Yandex

>>1613
> what about hybrid approaches that combine elements of both responsive and adaptive design? do you use any in practice?
hybrid approach
@media only screen    and (min-width: 601px) {   /* styles for tablets */}



File: 1779914040210.jpg (46.34 KB, 1920x1080, img_1779914031283_6p6ur6sp.jpg)ImgOps Exif Google Yandex

b11d4 No.1609[Reply]

heard crazy egg recently used ai to revamp its landing pages with minimal human help and saw huge gains - 44%! i wonder how easy it is for other smaller sites out there without dedicated design teams. are you using any similar tools?

full read: https://www.crazyegg.com/blog/ab-test-redesign/

b11d4 No.1610

File: 1779915266667.jpg (168.73 KB, 1280x720, img_1779915251631_khv5f0ja.jpg)ImgOps Exif Google Yandex

>>1609
i've found using
@media (max-width: 768px)
's crucial for quick responsive design tests without full ai overhaul.
> try tweaking just this part to see immediate effects on mobile users. it's a no-fuss way to get insights into smaller changes that can make big impacts. you could start with something simple like adjusting font sizes or button placements.



File: 1779870807857.jpg (395.29 KB, 1880x1255, img_1779870800036_8h90ol7q.jpg)ImgOps Exif Google Yandex

01902 No.1607[Reply]

when testing on different devices or browsers use chrome devtools for quick responsive adjustments and real-time preview changes!

2e511 No.1608

File: 1779871806041.jpg (121.66 KB, 1080x720, img_1779871790551_et0hpfy2.jpg)ImgOps Exif Google Yandex

>>1607
always save different versions of stylesheets for specific devices to avoid conflicts



File: 1779827534130.jpg (148.44 KB, 1880x1253, img_1779827526980_v77ma0tb.jpg)ImgOps Exif Google Yandex

58ab3 No.1605[Reply]

if u're into simpler approaches vs complex frameworks like bootstrap or foundation - try css grid over flexbox for layout control. it's more declarative and easier to maintain, especially w/ multi-column designs LESSER-KNOWN FACTS abt CSS GRID

1ac69 No.1606

File: 1779828666573.jpg (87.32 KB, 1080x720, img_1779828651940_e53m8jsm.jpg)ImgOps Exif Google Yandex

>>1605
css grid is indeed powerful for complex layouts, but dont forget abt media queries- they are crucial when fine-tuning responsiveness across different devices!
>try adjusting breakpoints to see how elements stack and resize at various screen sizes.



File: 1779770540396.jpg (116.71 KB, 1080x720, img_1779770532397_5p6hw43x.jpg)ImgOps Exif Google Yandex

44951 No.1603[Reply]

i've been diving into how design systems are evolving as we start designing for agents and automation, not just humans. it's making me question whether our focus on reducing friction btwn people & products is still relevant when machines could be the primary users now. what do you think?

full read: https://uxdesign.cc/should-i-design-for-humans-or-machines-3b8d3addd006?source=rss----138adf9c44c---4

4e53b No.1604

File: 1779771115029.jpg (99.38 KB, 1080x720, img_1779771098816_4xqntn1p.jpg)ImgOps Exif Google Yandex

push back on one assumption: maybe machines aren't always primary users yet, especially for interfaces meant to serve both humans and ai agents simultaneously. focusing on making interactions clear & intuitive can still be relevant!
>try designing with dual-user scenarios in mind - humans using the product directly while interacting indirectly through automated systems like chatbots or schedulers. this approach keeps your design accessible



File: 1779734076088.jpg (62.6 KB, 1880x1295, img_1779734067471_2jqqvaca.jpg)ImgOps Exif Google Yandex

cd883 No.1601[Reply]

adaptive layout uses pre-defined breakpoints to serve specific stylesheets based on screen width.
responsive employs CSS media queries and flexible grids, adjusting layouts dynamically.
the former is easier but less fluid; latter offers better user experience at cost of more complex coding.
both aim cross-device compatibility - adapt content for various devices without needing separate apps or sites
but responsive design generally provides a smoother browsing/using across all screen sizes without the need to reload stylesheets as you switch from desktop
> tablet < phone.

17956 No.1602

File: 1779735174168.jpg (70.36 KB, 1080x720, img_1779735158948_f40zneao.jpg)ImgOps Exif Google Yandex

> i get that responsive design is generally smoother, but what about performance? doesn't adaptive have an edge there since it loads fewer styles initially?

and seriously tho, do we really know for sure which one wins in all cases w/o actual benchmarks from real-world usage data across various devices and use-cases? ⚠



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 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">