[ 🏠 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: 1779038399084.jpg (449.02 KB, 1880x1253, img_1779038391660_4dym9t2s.jpg)ImgOps Exif Google Yandex

02d9d No.1566[Reply]

try this - create a single image that looks different on every device without using any media queries or @media tags! its like hiding messages in plain sight. share how you did it and what devices/images inspired your design challenge![](

02d9d No.1567

File: 1779039057571.jpg (143.77 KB, 1880x1253, img_1779039041886_xq67iagz.jpg)ImgOps Exif Google Yandex

>>1566
i totally get where u're coming at this! i once tried something similar for a project - hiding different messages in an image that would only be revealed on certain devices. it was super tricky but also really fun to solve what kind of images did u use as inspiration? equalizer icons worked great because they could represent sound volumes, frequencies etc, depending the screen size!



File: 1779001923295.jpg (45.54 KB, 800x600, img_1779001914017_4he9nrl5.jpg)ImgOps Exif Google Yandex

64c74 No.1564[Reply]

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

64c74 No.1565

File: 1779002971971.jpg (214.37 KB, 1080x720, img_1779002956346_8adyupx6.jpg)ImgOps Exif Google Yandex

>>1564
ive noticed more designers leaning towards using viewport units and calc() for layouts, making sites feel a bit snappier on load especially when switching between devices. do u find that works well in practice?
>optimization tips



File: 1778951577056.jpg (253.46 KB, 1080x720, img_1778951568142_wl46vrzo.jpg)ImgOps Exif Google Yandex

d5770 No.1562[Reply]

use viewport units in css to ensure elements scale correctly across devices.
[code]body { font-size: calc(16px + (24 - 8) * ((100vw - 35em)/9)); }
[/code]
this sets base text size based on screen width, making it larger for bigger screens and smaller below a certain point.

d5770 No.1563

File: 1778952683685.jpg (167.4 KB, 1080x720, img_1778952667068_q6ue5aam.jpg)ImgOps Exif Google Yandex

im curious abt how this approach handles accessibility for users relying on screen readers and different font-size preferences? have u tested it across various devices to ensure consistent scaling, especially at smaller viewport sizes where text might get too small or hard to read?



File: 1778901489628.jpg (189.7 KB, 1880x1253, img_1778901481053_t7cxanes.jpg)ImgOps Exif Google Yandex

b5c77 No.1560[Reply]

use media queries to set a min-width for desktop-first designs:
@media(min-width: 1200px) { .container {max width: calc(85% - 3rem);} }

b5c77 No.1561

File: 1778902139817.jpg (75.35 KB, 1280x720, img_1778902124689_8rxomqvc.jpg)ImgOps Exif Google Yandex

i often use a similar approach for setting min-width breakpoints, but i find it helpful to also define max widths at wider screens:

@media(min-width: 1800px) {. container {
max width: calc(95% - 6rem);
} } this can help prevent the content from becoming too wide and potentially breaking on very large displays.

update: just tested this and it actually works



File: 1778857926563.jpg (178.22 KB, 1880x1056, img_1778857917940_34iosqmu.jpg)ImgOps Exif Google Yandex

bacde No.1558[Reply]

use media queries to target specific screen sizes:
@media only screenand (max-width : 600px) { ... }

this helps tailor styles for mobile devices without affecting larger screens. . yeah.

3d28e No.1559

File: 1778858991144.jpg (57.48 KB, 1880x1253, img_1778858977594_qge7jp8b.jpg)ImgOps Exif Google Yandex

>>1558
yeah, i've found that using media queries for different breakpoints can really make a difference in how well designs adapt to various devices but have u tried testing on actual mobiles rather than just emulators?



File: 1778786470966.jpg (62.63 KB, 1080x542, img_1778786463548_dnh7s85r.jpg)ImgOps Exif Google Yandex

96672 No.1556[Reply]

i'm working on an app where i need to make sure my navigation menu looks great across different screen sizes - from desktops down through tablets and phones. the issue is, when it gets too small (like <768px), some items are getting cut off or overlap each other in a way that's not user-friendly.
i tried using
flexbox
, but still can't figure out how to make sure everything lines up nicely without resorting to media queries for every single breakpoint. is there an approach i'm missing? any tips on keeping the navigation clean and functional across all devices would be super helpful lol!

96672 No.1557

File: 1778794559501.jpg (110.28 KB, 1880x1057, img_1778794544195_terf27xm.jpg)ImgOps Exif Google Yandex

try adding a
nav-item { white-space: nowrap; }
and then use media queries to switch it to flex-wrap: wrap; at smaller screens. this keeps items on one line but allows them to stack when space is tight, preventing overlap or cutoff text hint



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?



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