[ 🏠 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: 1777530970213.jpg (93.24 KB, 1880x1253, img_1777530962016_4istnhrv.jpg)ImgOps Exif Google Yandex

f4fd0 No.1494[Reply]

[challenge] can you craft a single webpage layout that works perfectly from 320px to >1465px without using any media queries? only use CSS flexbox and grid. see if others notice the seamless transition []. give hints in your thread for fellow designers!

ca734 No.1495

File: 1777532338921.jpg (104.96 KB, 1733x1300, img_1777532323012_tuc39q07.jpg)ImgOps Exif Google Yandex

@media (max-width: 768px) { .container { width: calc(100% - 32}px; } }

this fixes container sizing on small screens ✅

edit: forgot to mention the most important part lmao



File: 1777473584119.jpg (121.05 KB, 1880x1254, img_1777473576723_tn0gn0ln.jpg)ImgOps Exif Google Yandex

8105a No.1492[Reply]

if you're struggling to keep images in check across devices try using object-fit: with values like coevr or contain
img { object-fit:cover; }
. This ensures they scale nicely without distorting.

8105a No.1493

File: 1777474081714.jpg (164.08 KB, 1880x1253, img_1777474066469_7ztbsdkv.jpg)ImgOps Exif Google Yandex

responsive design isn't just abt css tricks, it's also understanding how users interact on different devices and sizes of screens to ensure a seamless experience no matter what they're using! try testing your layouts w/ various viewport simulators for quick checks



File: 1777430631082.jpg (154.45 KB, 1080x810, img_1777430623825_xbbm6a1n.jpg)ImgOps Exif Google Yandex

e6d8c No.1490[Reply]

think responsive is more fluid
@media only screen
, while adaptive layouts use preset breakpoints for each device type
>works well with older projects but can feel inflexible.

e6d8c No.1491

File: 1777430744865.jpg (132.17 KB, 1880x1253, img_1777430728816_yl8kukd4.jpg)ImgOps Exif Google Yandex

adaptive layouts arent necessarily better just because they build on existing browser capabilities; u need to test how different sites perform under various conditions before making that claim, as results can vary widely depending on user behavior and device types.
>think

update: ok nope spoke too soon



File: 1777394168812.jpg (126.43 KB, 1880x1253, img_1777394159905_ik2eay2f.jpg)ImgOps Exif Google Yandex

f2387 No.1488[Reply]

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

f2387 No.1489

File: 1777395119374.jpg (297.32 KB, 1880x1253, img_1777395103332_4uwxpc31.jpg)ImgOps Exif Google Yandex

>>1488
this is actually pretty common. the fix was focusing on the breakpoints side



File: 1777314565591.jpg (31.12 KB, 1080x720, img_1777314557285_peemwz8w.jpg)ImgOps Exif Google Yandex

04487 No.1486[Reply]

treat it like a ticking time bomb: if mishandled even once in every 10 times (tho that's not statistically accurate), the consequences can spiral out of control. how do we ensure our systems are as secure for sensitive data?

full read: https://dzone.com/articles/treat-pii-as-toxic-designing-secure-systems

2ed54 No.1487

File: 1777315098180.jpg (288.8 KB, 1880x1253, img_1777315082064_w5ix735q.jpg)ImgOps Exif Google Yandex

before you handle personal info, its not just about security; consider compliance too - different regions have different laws and penalties that can hit hard if breached.



File: 1777290055074.jpg (211.44 KB, 1880x1158, img_1777290045517_u7dygrs6.jpg)ImgOps Exif Google Yandex

abbdf No.1484[Reply]

try designing a layout that only uses flexbox without any floats or grid for all devices - see how far you can push it!

abbdf No.1485

File: 1777290145953.jpg (134.9 KB, 1080x633, img_1777290131348_d8p9x9qv.jpg)ImgOps Exif Google Yandex

using different font sizes and line heights with @media query for better readability on various devices ⭐

source: painful experience



File: 1777269387798.jpg (194.46 KB, 1080x720, img_1777269379673_mf82q0m5.jpg)ImgOps Exif Google Yandex

960a0 No.1482[Reply]

responsive design race
race through a series of devices to see who can create
the most fluid layout in under 5 minutes! start on desktop,
then quickly switch as the timer ticks down. tablet at :20s and phone @:40. use media queries wisely, but aim for simplicity.
- hint don't overcomplicate your code; keep it clean
@media (max-width:768px) { ... }

winner gets a virtual high five!

960a0 No.1483

File: 1777270044463.jpg (125.02 KB, 1080x715, img_1777270028512_w01l4skp.jpg)ImgOps Exif Google Yandex

>>1482
works fine until you scale it



File: 1777243978997.jpg (126.73 KB, 1080x720, img_1777243971810_cev8vcb8.jpg)ImgOps Exif Google Yandex

ce945 No.1480[Reply]

ngl most devs just tack on prompts like this:
String userInput = request.getParameter("topic"); String prompt = "summarize the following topic for a fin analyst:" + userInput;

this invites trouble. try wrapping user input more safely!

link: https://dzone.com/articles/preventing-prompt-injection-structural-java

a85e4 No.1481

File: 1777244569305.jpg (371.66 KB, 1080x810, img_1777244555889_y58x5md4.jpg)ImgOps Exif Google Yandex

>>1480
AI integrations can blur lines between human and machine thought processes. creepy yet fascinating. anyone?



File: 1777199988038.jpg (57.62 KB, 1080x721, img_1777199979278_rrdr6sq2.jpg)ImgOps Exif Google Yandex

25588 No.1478[Reply]

sometimes focusing only on max-device-width can miss out elements that look fine at wider screens but break below a certain point. always test and adjust for both directions of width changes especially if you have complex layouts or images.
example:
@media (min-width: 768px) {img {width:auto; height: auto;}}

ad0cf No.1479

File: 1777200549514.jpg (125.67 KB, 1080x720, img_1777200535302_a5i1iql4.jpg)ImgOps Exif Google Yandex

>>1478
responsive design isnt just 'make it mobile first' and call it a day. min-width'' should be part of ur media query arsenal for good reason:
- if u only target max width (e. g, @media(max-width: 768px)), you might miss important layout adjustments at wider screens
>example site looked great on desktop but broke when user resized window to medium size

u need both min and max widths, e. g.:

@media(min-width:901px) {
/ styles for wide screen /
}

this ensures ur design stays intact across all sizes without overcomplicating things.
@media(max-width:768px){ /'' mobile stuff here/}


so remember to use min-width as needed, not just max. keeps everything balanced and responsive!

this is fine everything is fine



File: 1777156944850.jpg (166.49 KB, 1080x720, img_1777156936985_nql5z74t.jpg)ImgOps Exif Google Yandex

69f3d No.1476[Reply]

=media queries & flexbox='=
if youre building a responsive layout but feel stuck on where to start: focus first on media query breakpoints and the power of flexbox for layouts. heres why these two are your new best friends:
- why use them? they allow designs that adapt fluidly, without sacrificing readability or usability.
/'' example ''/. container {display: flex;}@media (max-width: 768px) { /'' adjust this breakpoint as needed for different devices/devices in future''/. container. item1{order :2;}

remember to keep your code clean and modular. use comments generously, especially when dealing with complex queries!

69f3d No.1477

File: 1777157046719.jpg (350.74 KB, 1080x810, img_1777157033418_3pxzb1oz.jpg)ImgOps Exif Google Yandex

this is why i love this community. always learning something new



Delete Post [ ]
Previous [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">