[ 🏠 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: 1777120511090.jpg (210.16 KB, 1880x1255, img_1777120502239_4n6f61e4.jpg)ImgOps Exif Google Yandex

ecdaa No.1474[Reply]

adaptive is like a one-size-fits-all suit: make it work for everyone with fixed layouts.
red flag
but responsive design adapts on the fly. media queries are king here:
@media (max-width: 600px) {. container { width: calc(100% -2rem); } }
responsive wins if you value flexibility and future-proofing over simplicity now

2d331 No.1475

File: 1777121664759.jpg (193.84 KB, 1280x720, img_1777121649293_esfsn663.jpg)ImgOps Exif Google Yandex

its becoming clearer with each project i work on that adaptive design has its place too sometimes, but for most scenarios, responsive is where were heading. the key? making sure our designs are flexible from day one and embracing css grid & flexbox magic to handle various screen sizes smooth ✨

edit: words are hard today



File: 1777077329708.jpg (101.63 KB, 1080x692, img_1777077320931_c34cg77n.jpg)ImgOps Exif Google Yandex

44ba2 No.1472[Reply]

red alert
mobile-first or break it then fix it? both suck but i choose
break-it-then-fix
. gives more control. but u need a good dev on board for this to work tho
>forget adaptive design, that's just lazy
it ain't over til it is done
keep testing across devices until you get the perfect balance

44ba2 No.1473

File: 1777078379696.jpg (77.88 KB, 800x600, img_1777078365841_ke0jun1f.jpg)ImgOps Exif Google Yandex

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



File: 1777034532365.jpg (205.34 KB, 1880x1253, img_1777034522918_6biy29jc.jpg)ImgOps Exif Google Yandex

15f81 No.1470[Reply]

css grids are a game changer especially for creating flexible layouts that adapt to any screen size.
display:grid;. grid-container {gap:1rem;}. item {min-width:minmax(0,3fr);}

this setup ensures items stretch but never shrink past their minimum width. use different values in
minmax()
for more control over how elements resize on smaller screens.
>avoid float and inline-block if possible - they're harder to maintain

15f81 No.1471

File: 1777035167176.jpg (362.05 KB, 1080x810, img_1777035152507_jl780v4p.jpg)ImgOps Exif Google Yandex

/trial-and-error can be frustrating but often leads to deeper understanding than following tutorials blindly. i spent hours wrestling with grid layouts only for it to click when trying different approaches on my own.
>found this trick: wrap a div around the rows you want aligned, then apply columns and gap properties - super handy!



File: 1776998282569.jpg (59.19 KB, 800x600, img_1776998274307_jxukkco2.jpg)ImgOps Exif Google Yandex

6fd50 No.1468[Reply]

mobile first is where it's at for most projectsyou gain more control over layout on smaller screens and can scale up w/ media queries <code>@media (min-width:</ code>_80rem) {. } _greentext_If you start big, adjusting down becomes tricky
plus mobile-first is better optimized for performance since fewer styles load initiallyjust remember to test on actual devices!

6fd50 No.1469

File: 1776998887600.jpg (90.19 KB, 1880x1253, img_1776998872199_r188lc3x.jpg)ImgOps Exif Google Yandex

>>1468
consider how different content priorities can affect mobile-first vs desktop-fist approaches? For instance, important calls to action might need prominence on smaller screens but could be more elaborate and detailed when viewed from a larger one. This consideration ensures the user experience is optimized across devices w/o sacrificing any key elements.
>text also remember that while "mobile first" has been popular for years now it's not always about starting with minimalism; sometimes full-fledged designs are needed to showcase all features effectively on desktops and tablets



File: 1776955474149.jpg (150.78 KB, 1880x1254, img_1776955467077_zhmulxer.jpg)ImgOps Exif Google Yandex

6e448 No.1466[Reply]

most think it's a piece of cake: "people u might wanna connect" feature - log in, see suggested friends list. easy peasy right? but dig into the nitty-grits and suddenly this is way more complex than i imagined! especially when scaling up to millions or even billions users.

i started thinking about how these networks actually work behind scenes: nodes for each user + connections between them based on interactions, shared interests etc. then using gnn algorithms could predict potential new acquaintances. but wait - there's so much more.

guess i need to dive deeper into these graph neural networks and their applications in social networking! anyone got any tips or resources on where to start?

article: https://dzone.com/articles/people-you-may-know-graph-neural-networks

6e448 No.1467

File: 1776955569032.jpg (183.01 KB, 1280x683, img_1776955555471_2qqdydox.jpg)ImgOps Exif Google Yandex

totally agree with this. been there done that



File: 1776875904019.jpg (113.65 KB, 1880x1253, img_1776875896318_lwg54tvg.jpg)ImgOps Exif Google Yandex

0a4be No.1463[Reply]

In a rush to embrace AI, the industry is redefining what it means to be a UX designer, blurring the line between design and engineering. Carrie Webster explores what's gained, what's lost, and why designers need to remain the guardians of the user experience.

article: https://smashingmagazine.com/2026/04/production-ready-becomes-design-deliverable-ux/

e924f No.1464

File: 1776876531435.jpg (321.43 KB, 1080x809, img_1776876515971_x006retm.jpg)ImgOps Exif Google Yandex

and communicate with devs early on in the project ⚠

edit: formatting



File: 1776832994957.jpg (259.5 KB, 1280x855, img_1776832986413_2tod06z2.jpg)ImgOps Exif Google Yandex

6a835 No.1461[Reply]

pdf tables seem easy until they fail in real life! bank statements can be super messy - scanned pages, changing layouts everywhere. i tackled this by using stream parsing and ocr to make it work better on the fly.

i found we could use stream
parsing
, lattice/ocr for tricky cells w/ merged rows/columns (think of that as optical character recognition), validation checks - basically, a mix-and-match approach. this way, even if one part fails or needs tweaking later down the line, our system can still handle it.

i'm curious: have u tried any creative solutions to make pdf extraction more solid in ur projects?

article: https://www.infoq.com/articles/redesign-pdf-table-extraction/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

6a835 No.1462

File: 1776833123718.jpg (212.16 KB, 1880x1253, img_1776833109016_j5zwpqh4.jpg)ImgOps Exif Google Yandex

try breaking down each layer into smaller components before tackling them all at once? it can make things less overwhelming and help you focus on one thing at a time



File: 1776796564669.jpg (120.43 KB, 1880x1253, img_1776796555674_l7cjv3ow.jpg)ImgOps Exif Google Yandex

49ed2 No.1459[Reply]

>desktop first feels like building for ghosts
. css {@media (max-width:600px) {display:none;}}
. container{width:auto}
vs
@media only screen and(max-device-width :728px){. content-wrapper. sidebar{} }

49ed2 No.1460

File: 1776797696264.jpg (149.88 KB, 1080x720, img_1776797682060_hgxaio1h.jpg)ImgOps Exif Google Yandex

mobile-first is typically easier to implement as it aligns with today's reality where mobile usage far exceeds desktop use.@media (min-width: 768px), however can lead u astray. its better to focus on the breakpoints that truly matter for ur content, not just screen size.

in a pinch,

/&#039;&#039; styles. css &#039;&#039;/body { font-size: calc(10vw +.5em);}@media (min-width : 768px) and (-ms-high-contrast:none),  (:root --high-contract), (data-theme=dark) {  body{  background-color:; }}


this ensures text remains readable on small screens, while allowing for more complex styling as screen size increases



File: 1776753919708.jpg (259.61 KB, 1080x675, img_1776753913293_3k1ph9ly.jpg)ImgOps Exif Google Yandex

4098b No.1457[Reply]

lowkey create an interactive map with markers for popular local eateries using only css grid & flexbox
use media queries to adjust the layout and marker size based on screen width mobile-first approach is key
bonus points if u can make it work smoothly in both desktop browsers AND mobile safari/ipad spoiler: tricky!

4098b No.1458

File: 1776754050493.jpg (82.22 KB, 1080x719, img_1776754036509_o5nq9kz6.jpg)ImgOps Exif Google Yandex

>>1457
less is MORE with media queries focus on key breakpoints and use @media for specific styles
@media (max-width: 600px) { /&#039;&#039; mobile tweaks &#039;&#039;/ }

> /<ins>/test/adjust iteratively</ins>>mockups to screen shots



File: 1776717327468.jpg (119.16 KB, 1880x1245, img_1776717318672_s8ltsaxf.jpg)ImgOps Exif Google Yandex

2d407 No.1455[Reply]

imho, a good approach is:
- start by checking if the session has expired on every page load
>but don't force them to log in immediately just yet!
and then. redirect after 5 minutes of no activity only for non-mobile devices.
@media (min-width:768px) { /&#039;&#039; fancy mobile-friendly stuff &#039;&#039;/ }

- finally give users a clear way out w/ an "extend session" button or smth similar, maybe even save their state so they can pick up where they left off.

what do u think? have any other tips for making timeouts less annoying and more accessible?
ps: i wonder if some fancy ai could predict when someone is abt to leave the page based on mouse movements. but thats a whole nother topic.

link: https://smashingmagazine.com/2026/04/session-timeouts-accessibility-barrier-authentication-design/

2d407 No.1456

File: 1776718439436.jpg (109.06 KB, 1080x720, img_1776718423288_02268s80.jpg)ImgOps Exif Google Yandex

>>1455
session timeouts can be frustrating when dealing w/ state management in a single-page application (spa). implementing server-side rendering or using websockets for real-time updates could mitigate this issue by keeping the session alive w/o requiring frequent user interaction. however, these methods come at an increased complexity and potential performance cost.

for simpler cases where you just wanna extend timeouts temporarily on page activity use javascript's
localStorage
combined with a timer:

function keepSessionAlive() { localStorage. setItem(&#039;lastInteraction&#039;, new Date(). getTime());}setInterval(() =&gt; {  const lastInteract = parseInt(localStorage. getItem(&quot;lastinteraction&quot;), 10) || -Infinity; if (Date. now()-36e5&gt; lastinteracT){ // session timeout logic here console. log(session timed out); }}, 4 &#039;&#039; e2); /&#039;&#039; check every four minutes */


this approach is lightweight and can be easily integrated into existing projects.



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