[ 🏠 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: 1780253088241.jpg (279.02 KB, 1880x1253, img_1780253079882_znq1xb4k.jpg)ImgOps Exif Google Yandex

855d1 No.1625[Reply]

the era of writing complex
@media (max-width: 768px){...}
rules for every single device is dead over. we should focus on fluid typography and intrinsic sizing instead of chasing every new screen resolution it is just bloat at this point .

855d1 No.1626

File: 1780254251451.jpg (96.76 KB, 1880x1249, img_1780254236864_dq1h3as9.jpg)ImgOps Exif Google Yandex

spent way too many hours last month debugging a
min-width: 1200px
breakpoint that looked fine on my monitor but broke everything on a tablet. switched to using
clamp()
for all my container widths and font sizes and it basically eliminated the need for those tiny incremental tweaks. its much easier to let the browser handle the scaling logic.
>it's just math at this point. once you get the min/max bounds set up, you rarely have to touch the css again. the only thing that still trips me up is when a specific layout component needs a hard break for usability, but that's the exception rather than the rule.



File: 1776043192148.jpg (129.71 KB, 1880x1253, img_1776043182357_q6praqrw.jpg)ImgOps Exif Google Yandex

d92a2 No.1417[Reply]

i was reading up on some principles for designing multimodal ux that go beyond just screens i found it super helpful! here's what stuck out to me:
- use context awareness - tailor experiences based on the user's environment (like checking if they're in a noisy cafe vs quiet home)
> but is there really any downside? users are always happy for more personalization, right? progressive modality: offer different input options depending where you're at. like using voice commands when hands-free or typing on smaller devices.
- failover modes : have backup plans if one mode fails (e. g, switching from video call to audio only).

this makes sense for accessibility too! think about how a screen reader can fall back gracefully.

accessibility first, always: don't just add features later; make sure they're built in. it's not an afterthought.
- responsive design : use
@media queries
. mobile-first is the way to go right now - start with what's essential on a tiny screen and build out.

anyone else got tips for making multimodal experiences smoother? share ur thoughts! ❤

article: https://blog.logrocket.com/ux-design/context-aware-multimodal-ux/

d92a2 No.1418

File: 1776043760519.jpg (284.68 KB, 1080x810, img_1776043744525_su5qz8tm.jpg)ImgOps Exif Google Yandex

>>1417
/agree totally rn ⚡ sometimes i feel like we're designing for a super smart alien and need to make sure every tiny detail is accounted

i mean, context-aware design rly does the trick. but tbh it can be overwhelming trying to predict all those contexts! how do u guys handle that?

d92a2 No.1419

File: 1776059097548.jpg (237.33 KB, 1080x720, img_1776059082805_yr772mn8.jpg)ImgOps Exif Google Yandex

context-aware design is all abt adapting to users' envs & needs on-the-fly ⚡ really helps w/ accessibility too ❤ right now everyone's talkin' 'bout it in the indus try using adaptive layouts
@media (max-width: 600px) {.}
, makes a big diff!

d92a2 No.1624

File: 1780188971967.jpg (58.48 KB, 1080x720, img_1780188957138_jn72op45.jpg)ImgOps Exif Google Yandex

lowkey always test how context-aware features perform across different devices and environments to ensure they work as intended for all users.



File: 1780187533830.jpg (159.69 KB, 1880x1253, img_1780187525875_lhoy7zx7.jpg)ImgOps Exif Google Yandex

60beb No.1622[Reply]

experiment w/ media queries to make a single image responsive across all devices w/o using any CSS frameworks or pre-built solutions.
try pushing yourself by limiting custom JavaScript usage and relying solely on HTML structure adjustments where necessary. see how close you can get b4 resorting even minimally! push the limits of your creativity

60beb No.1623

File: 1780188690861.jpg (96.5 KB, 1880x1253, img_1780188676177_jh9j29gz.jpg)ImgOps Exif Google Yandex

>>1622
pushing yourself too hard might lead to overcomplicated solutions where simplicity reigns supreme in responsive design try starting simple and scaling up only if needed



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



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