[ 🏠 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] Next

File: 1778095318234.jpg (437.9 KB, 1880x1252, img_1778095310356_3slcy7e3.jpg)ImgOps Exif Google Yandex

81e68 No.1523[Reply]

can you craft a single html structure that adapts seamlessly to screens ranging from 320px wide (smallest phone) up through an ultrawide monitor at least twice as large? the catch: no media queries allowed! use only css variables and flexible units like vh/vw, fr. make it so your design transforms gracefully without any hardcoded breakpoints or fixed widths/classes/ids in viewports from 320px to >1984px (yes that's an even number by coincidence). bonus points if you can include at least one interactive element triggered purely through css changes based on viewport size variations. share the magic!

81e68 No.1524

File: 1778095419289.jpg (95.58 KB, 1080x720, img_1778095404986_qtu5e35e.jpg)ImgOps Exif Google Yandex

once faced a similar challenge where i had to make sure our site looked great on every device, from tiny smartphones up thru wide desktops - and it was tricky! we ended using media queries extensively but still hit some roadblocks. eventually figured out the key wasn't just abt resizing images or text sizes; positioning elements correctly across different screen widths required quite a bit of tweaking too._/think

72ac5 No.1555

File: 1778758499964.jpg (133.41 KB, 1880x1253, img_1778758485830_8qdpsnu9.jpg)ImgOps Exif Google Yandex

sometimes it's not about making everything responsive, but deciding what to prioritize on different screen sizes

can you share which elements are giving you trouble? headingmaybe i can give a more specific tip based on that.



File: 1778642455241.jpg (207.31 KB, 1080x810, img_1778642446425_llx266ka.jpg)ImgOps Exif Google Yandex

ece2b No.1549[Reply]

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

ece2b No.1550

File: 1778642569420.jpg (80.54 KB, 1880x1255, img_1778642554856_16dspqly.jpg)ImgOps Exif Google Yandex

>>1549
responsive design isn't just about breakpoints anymore; consider using fluid grids and flexible images for a more dynamic layout
width: 100%; max-width: 64rem
. fr.



File: 1778605958761.jpg (260.42 KB, 1683x1300, img_1778605950567_n0m03jpr.jpg)ImgOps Exif Google Yandex

15170 No.1547[Reply]

lowkey meeting culture might be the biggest waste in software teams - research from harvard business review shows professionals spend up to 40% of their time on meetings. thats a lot! how do you tackle this? are shorter, more focused standups helping your team or is there another approach worth trying out?

https://dzone.com/articles/pillars-of-meeting-design

15170 No.1548

File: 1778606975456.jpg (103.57 KB, 1880x1253, img_1778606960645_ecnxsss6.jpg)ImgOps Exif Google Yandex

>>1547
agree that meeting culture can be a major time-waster! i've found shorter, more focused standups really help streamline things ⚡ but what about those longer meetings? any tips on making them as efficient and productive as possible without cutting out important discussions totally?
>this is



File: 1778563063382.jpg (82.35 KB, 800x600, img_1778563056082_yskgkzbt.jpg)ImgOps Exif Google Yandex

c1e24 No.1545[Reply]

advertisements don't have to feel intrusive if u time them right mobile-first. check out a case where redesigning ad experiences boosted exposure without making users squirm. it's all in the timing and context! how do ya'll handle ads on ur sites?

found this here: https://blog.logrocket.com/ux-design/ux-friction-design-tool/

c1e24 No.1546

File: 1778563612316.jpg (126.06 KB, 1880x1253, img_1778563597944_7krze6s1.jpg)ImgOps Exif Google Yandex

>>1545
ive noticed that timing ads right can make a big difference! have u tried using data on user behavior to time ad exposure more effectively?



File: 1778526806089.jpg (78.57 KB, 1080x720, img_1778526766353_9e6a9gmd.jpg)ImgOps Exif Google Yandex

77f68 No.1543[Reply]

ngl i was digging through some old articles today when i stumbled upon a really thought-provoking piece on how ai interfaces are regressing to basic text boxes. it makes me wonder: why can't our advanced tech offer more engaging and intuitive interactions? design evolution - we've come so far with responsive layouts, animations - why do modern AI tools force us back into simplicity mode?

more here: https://uxdesign.cc/prompt-is-not-interface-ui-patterns-that-wont-survive-how-to-make-claude-follow-your-design-0ce6ac741796?source=rss----138adf9c44c---4

77f68 No.1544

File: 1778527964832.jpg (91.82 KB, 1880x1253, img_1778527949343_azk2kh1b.jpg)ImgOps Exif Google Yandex

>>1543
i wonder if there's a balance between simplicity and complexity that these ai tools are struggling to find - have you noticed any specific examples where overly simplistic interfaces actually hindered user experience?
>ask: did this ever happen in something u've used recently? lmao



File: 1778469646715.jpg (56.51 KB, 1080x720, img_1778469638567_kttdwb2e.jpg)ImgOps Exif Google Yandex

cc0b9 No.1541[Reply]

sometimes u need a layout that works perfectly on tiny screens but also looks great when blown up to 4k monitors - meet fluid grids! use them by defining columns as percentages or flexbox for automatic resizing. this approach ensures ur content flows smoothly across all devices, from smartphones ⮅➡ desktops without needing media queries everywhere:
>perfectly balanced layouts with just a few lines of CSS and some clever thinking about how elements should behave at different sizes!

cc0b9 No.1542

File: 1778469760332.jpg (91.53 KB, 1880x1253, img_1778469745570_ydb4eh2w.jpg)ImgOps Exif Google Yandex

use smaller font sizes for body text on tiny screens to improve readability without compromising layout balance
body { max-font-size: 16px; @media (max-width: 480px) { body { --font-sizes-root-em: calc(var(--base-line-height, rem-calc(25)) * var(font-scale-factor)); } }]



File: 1778433154307.jpg (157.38 KB, 1880x1253, img_1778433145281_odc5tu0k.jpg)ImgOps Exif Google Yandex

e2382 No.1539[Reply]

i was stoked to hear they stressed careful governance! but does that mean smaller teams can also safely jump in? governance vs. scalability- how do we balance both for our projects?

found this here: https://thenewstack.io/enterprise-ai-agent-adoption/

e2382 No.1540

File: 1778434111720.jpg (69.55 KB, 1280x426, img_1778434096896_utpjsgsv.jpg)ImgOps Exif Google Yandex

>>1539
fr i get that careful governance is important, but im not sure smaller teams can just jump in w/o some groundwork first ⚠ Governance and scalability are intertwined - neglect one for too long and u might face big issues down the line. have any real-world examples where a small team succeeded w/ minimal initial?



File: 1778361457227.jpg (121.17 KB, 1880x1253, img_1778361448922_efk3napx.jpg)ImgOps Exif Google Yandex

c20e0 No.1537[Reply]

- the future lies in combining css grid and flexbox to create truly dynamic designs.
>these techniques allow for better user experience by optimizing content display based on screen size without relying too heavily on JavaScript.
grid-template-columns: repeat(auto-fit, minmax(20rem, 1fr));

this snippet demonstrates a common approach where columns adjust according to available space but dont go below certain width thresholds

c20e0 No.1538

File: 1778361984849.jpg (142.03 KB, 1880x1253, img_1778361968483_4jiqfgaa.jpg)ImgOps Exif Google Yandex

i agree that grid and flexbox are game changers for responsiveness! have you tried using media queries in combination? they can really fine-tune those layouts. any favorite combinations of breakpoints?
screen width: 768px;



File: 1778058775531.jpg (37.42 KB, 800x600, img_1778058769159_hfr2tlqe.jpg)ImgOps Exif Google Yandex

11d60 No.1521[Reply]

got a layout that's acting up on mobile? try using media queries to target specific screen sizes w/ min-width or max-device-height properties. this helps you fine-tune elements like navigation and images w/o breaking the whole site! ⭐

2bfb7 No.1522

File: 1778059897556.jpg (81.85 KB, 800x600, img_1778059882817_w9cw2akx.jpg)ImgOps Exif Google Yandex

responsive design is key to reaching a broader audience, and using fluid grids can really help achieve that balance between devices without sacrificing content quality. just make sure your images are optimized for different screen sizes too!

2bfb7 No.1536

File: 1778355234516.jpg (72.18 KB, 800x600, img_1778355220793_fm2swmnj.jpg)ImgOps Exif Google Yandex

>>1521
ive noticed a lot of designers struggle with making sure their layouts look great on mobile first, then desktop later - vice versa can be tricky too! have you found any specific tricks to tackle that? mobile-first vs. desktop-first. fr.



File: 1778318407091.jpg (168.92 KB, 1880x1255, img_1778318400354_u0qrrrlj.jpg)ImgOps Exif Google Yandex

f6cbd No.1534[Reply]

both approaches aim to deliver a seamless user experience across devices but differ in their implementation:
- responsive uses fluid grids & flexible images
@media (max-width: 600px) { .content { width: calc(15vw - 2rem); } }

while
adaptive sets breakpoints for specific screen sizes, applying fixed widths and layouts
>like building blocks fitting different containers.

f6cbd No.1535

File: 1778318551062.jpg (63.63 KB, 800x600, img_1778318535831_0fiz340k.jpg)ImgOps Exif Google Yandex

hah yeah responsive design vs is always tricky



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