[ 🏠 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: 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: 1776918913692.jpg (247.74 KB, 1080x721, img_1776918905884_fdwwyi4x.jpg)ImgOps Exif Google Yandex

9433b No.1465[Reply]

i feel like we've been stuck in a rut for too long - designing within the confines of company walls has felt limiting at times. but maybe 2026 marks something different?

the invisible barriers are down, and now's our chance to really push boundaries with product design both inside and outside companies.
i wonder how this will change things. could it be time for a major shift in the way we see value?

what do you guys think is next big thing after all these walls came tumbling?

more here: https://uxdesign.cc/product-design-in-2026-the-beginning-of-a-fantastic-voyage-fb6866c907ac?source=rss----138adf9c44c---4


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,

/'' styles. css ''/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) { /'' mobile tweaks ''/ }

> /<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.



File: 1776674316813.jpg (311.59 KB, 1280x720, img_1776674307133_edjacizi.jpg)ImgOps Exif Google Yandex

d0923 No.1453[Reply]

Anthropic Labs, the Claude-maker's AI safety and research division, on Friday launched Claude Design, a new service in research preview The post Anthropic launches Claude Design, a Figma and Canva rival built on Claude appeared first on The New Stack.

full read: https://thenewstack.io/anthropic-claude-design-launch/

d0923 No.1454

File: 1776674758563.jpg (110.34 KB, 1080x810, img_1776674742654_7kxlfhwo.jpg)ImgOps Exif Google Yandex

claude's supposed prowess might be overhyped - lots of ai are text-heavy but fall flat in design visuals and ux nuances Figma & 'canva' excel at bc they're built on user feedback loops not just algos. plus, reliance solely on an assistant can stifle creativity rather than enhancing it.
>just another tool with a steep learning curve for those who expect magic buttons to solve everything



File: 1776631386070.jpg (215.51 KB, 1080x720, img_1776631378142_r06myosb.jpg)ImgOps Exif Google Yandex

91a99 No.1451[Reply]

i think mobile is king now but some big sites still prefer to build for deskies then adapt.
if ur site/app needs speed and ubiquity go mob fi. else, desk-fi might serve older tech better.
but with css grid flexbox r everywhere - the battle's over? not so fast. design systems like
system-ui
, web components on mobile lag behind desktops in perf & interactivity.
so is it time to rethink our approach again?
anyone got a new perspective or best practice theyre sticking by?
>we'll see what 2036 brings

91a99 No.1452

File: 1776631492291.jpg (96.76 KB, 1880x1249, img_1776631476566_hjhfcalo.jpg)ImgOps Exif Google Yandex

mobile first is great for ensuring designs are accessible on small screens but forcing it as a one-size-fits-all approach can be limiting and inefficient Responsive design should adapt to the device context, not stick rigidly to any single strategy. Some sites need more real estate from day 1, especially if they're heavy with content or interactive elements that benefit greatly from larger screens ⬆

edit: i was wrong nope i was right



File: 1776588165330.jpg (128 KB, 1080x718, img_1776588157826_u2fznvgc.jpg)ImgOps Exif Google Yandex

fb297 No.1449[Reply]

i feel like we're wired to create something amazing with our hands (or fingers), but the digital world is all "consume consume." how do u balance that?

imagine a designer at day's end. they've reviewed ai-generated ideas, replied slack messages nonstop about design stuff not even related anymore scrolled through dribbble hoping for inspiration - just to deliver another iteration of something familiar.

what's ur go-to method when the creation vs consumption tug-of-war comes knocking?

found this here: https://uxdesign.cc/are-we-makers-by-nature-or-consumers-by-design-0a63abb301f0?source=rss----138adf9c44c---4

fb297 No.1450

File: 1776588266042.jpg (171.49 KB, 1880x1253, img_1776588251292_p80pu9q1.jpg)ImgOps Exif Google Yandex

>>1449
ngl when designing for both makers and consumers consider using breakpoints wisely to ensure a smooth experience across devices.
>especially focus on how elements stack or resize as you move between screens. avoid overly complex layouts that might confuse either group.

test w/ real users from each target demographic early in the process.

edit: should clarify this is just what worked for me



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