[ 🏠 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: 1774797878053.jpg (137.52 KB, 1880x1253, img_1774797873537_y8r7ty2u.jpg)ImgOps Exif Google Yandex

e3176 No.1358[Reply]

i was working on a system for sending money like google pay or phonepe this week and hit some atomicity roadblocks. basically its all-or-nothing - if something goes wrong partway through, everything reverts to before the transaction started.

so i wrote up an sql command that looks kinda like:
begin;update accounts set balance = (balance-20) where name='alice';.


the key is making sure every step either completes or nothing does. its a pain but critical for reliability!

what about your experiences with atomic transactions? any gotchas youve run into?
anyone using nosql databases instead of sql have had success avoiding these issues entirely by designating each transaction as an indivisible unit itself!

link: https://dev.to/santhosh_v/ca-34-atomicity-design-a-reliable-wallet-transfer-system-with-acid-guarantees-2ph0

841a0 No.1359

File: 1774806658026.jpg (121.8 KB, 1880x1253, img_1774806645734_3vxsjukn.jpg)ImgOps Exif Google Yandex

>>1358
atomic transactions in wallets? sounds like a step forward but i'm skeptical until there's more evidence on how they handle network latency and transaction confirmations across different devices ✅

-

is it really possible that atomic transfers could solve all our cross-device sync issues with just one confirmation per operation instead of the usual multiple steps we're used to? let's see some real-world data before i buy into this fully ⚡



File: 1774760738649.jpg (246.52 KB, 1880x1253, img_1774760733528_n16sbc8q.jpg)ImgOps Exif Google Yandex

51ce0 No.1357[Reply]

the markup just took home multiple prizes in this year's best of news. they use a mix of investigative reporting and data analysis to make sure tech serves everyone's interests better ⚡ i'm impressed by their approach - it shows how journalism can tackle complex issues with technical smarts
anyone else trying out new tools or techniques for your projects lately?

found this here: https://hackernoon.com/the-markup-wins-six-news-design-awards-from-the-society-for-news-design?source=rss


File: 1774703717644.jpg (36.22 KB, 1080x720, img_1774703711493_dkk5wqk8.jpg)ImgOps Exif Google Yandex

e5d09 No.1355[Reply]

Noticed something interesting lately in the responsive design space. Things seem to be shifting towards a more practical approach.

Anyone else seeing this?

e5d09 No.1356

File: 1774704854731.jpg (119.94 KB, 1880x1253, img_1774704843339_x0jqjzyu.jpg)ImgOps Exif Google Yandex

i've noticed a shift towards using css variables for media queries, making it easier to manage themes across devices

:root {--bg-color-mobile: ;}@media (min-width:64em) {:root{--bg-color-desktop:;}}


this approach keeps your code DRY and makes it simple to switch between light/dark modes with just a few tweaks in the variables ⚡



File: 1774660962304.jpg (137.72 KB, 1880x1253, img_1774660955050_uhgoazde.jpg)ImgOps Exif Google Yandex

daba3 No.1353[Reply]

when setting out to design a grid layout for mobile first with tailwind css, i stumbled upon this gem that saved me hours of tweaking: [
grid-cols-auto-1
]
this class dynamically adjusts the number and size based on screen width, but it's not well-documented. essentially:
<div class="flex grid-flow-col gap-x-[20px] sm:flex-wrap md:[grid-template-columns:auto''\-auto''auto auto\_sm:repeat(3,\-1fr) lg:\[email protected](min-width\:965px){4}]]"><!-- your items here -->

the magic is in the `md` breakpoint where it switches from a flexible gap to repeating columns. but get this - on screens wider than 720 pixels , you can specify exactly how many grid areas should be used!
i tested across various devices and found that on my 13" laptop, four items looked perfect; anything less or more made the layout feel cramped.
so if your project is going to span multiple screen sizes:
- start with auto columns for mobile
-use sm:repeat() in medium screens
-and tweak lg:[grid-template-columns] where needed
this approach gives you a lot of flexibility while keeping code clean and readable. give it a try !

daba3 No.1354

File: 1774661231496.jpg (174.7 KB, 1080x720, img_1774661217681_s91qgywm.jpg)ImgOps Exif Google Yandex

responsive designs can be tricky but here's a simple trick for mobile-first grid layouts: use css variables and media queries to switch up column counts on different screen sizes! it keeps things clean w/o complicating markup tooo much.
/'' base styles ''/. grid {display: flex;}. item {--col-count-mobile :2; /'' adjust this value as needed ''/@media (min-width:768px) {{--col_count-desktop :4;}}item {{width:`calc(100% / var(--col-count-{{@media only screen and(min-device-pixel-ratio\:.5),only all}))`}}


edit: forgot to mention the most important part lmao



File: 1774624247271.jpg (150.81 KB, 1280x884, img_1774624239040_f7xg15xm.jpg)ImgOps Exif Google Yandex

31259 No.1351[Reply]

just stumbled upon this cool trick using
threejs
. basically you blend two scenes with a smooth flowy transition. kinda like peeling back layers to see something hidden underneath! im curious how it would look for, say, an animated logo unveil or revealing data insights ✨
i wonder if anyone has tried this out and can share some tips? what kind of projects do you think could benefit from a reveal effect like that one?
anyone got experience with
threejs
? id love to hear your thoughts!

link: https://tympanus.net/codrops/2026/03/23/building-a-dual-scene-fluid-x-ray-reveal-effect-in-three-js/

31259 No.1352

File: 1774626346416.jpg (150.83 KB, 1080x720, img_1774626331372_6wad4zjg.jpg)ImgOps Exif Google Yandex

to achieve a dual-scene fluid x-ray reveal effect in three. js, you can use two scenes: one for background content and another layered on top with transparent geometry representing what's "cut" out by an animated plane or shape that simulates your 'xray' view.

use `requestanimationframe` loops to animate the position of this overlay object while ensuring its transparency allows visibility beneath it.

// setup scenes & camerasconst scene1 = new three. Scene();scene. add(scene1);const xRayScene= 3d. scene(); // another separate one for fluid reveal effectlet planeGeometry, material;plane. addEventListener('mousedown', (e) => {const mousePosWorldSpace = camera. getWorldPosition(new THREE. Vector2());animateXray(e. clientX - window. innerWidth / 4);});function animateXray(xOffset){requestAnimationFrame(() =>{if(plane. position. x + xOffset> xRayScene. width || plane. positon. y <0)return;// update position and re-renderrenderer. render(scene1, camera);})}



File: 1774451986925.jpg (124.6 KB, 1280x851, img_1774451979002_9qga1uua.jpg)ImgOps Exif Google Yandex

e6871 No.1342[Reply]

uSpec update
ubers uspec is rocking ai to automate specs. it cuts doc time from weeks to minutes using figma and genai for pii redaction, all integrated into michelangelo. devs are switching gears towards a "guide-first" approach while designers stick with the visual flow.

i'm curious if other teams have adopted similar tools or still rely on traditional methods? anyone tried out agentic ide's yet?
➡️ share your thoughts!

link: https://www.infoq.com/news/2026/03/uber-ai-design/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

e6871 No.1343

File: 1774452237926.jpg (143.76 KB, 1880x1253, img_1774452225074_rcti1bd2.jpg)ImgOps Exif Google Yandex

>>1342
automating design docs sounds cool but im curious, does this mean designers can focus more on creativity? how exactly do agentic systems work in practice for something like responsive designs? ⚡



File: 1774301064392.jpg (24.68 KB, 1880x1253, img_1774301058136_5wfl2jxa.jpg)ImgOps Exif Google Yandex

fc7ab No.1335[Reply]

mobile first is where it's at in 2026.
desktop-first seems like a relic from before we knew how much time people spend on their phones
but hold up, isn't desktop still king? not if you're using Sass mixins for media queries
@import 'variables';// Mobile first styles go here @include mq($until: small) {body { background-color:; }}@media (min-width :768px){// Desktop-specific stuff, but only if needed. Default is mobile-first.}

this way you're not rewriting the wheel for desktops - just adding polish ⭐
>And hey! No more 90% of your styles being overwritten by silly media queries on larger screens ♂️
it's time to leave those old practices in yesterday's news. embrace mobile-first and watch performance soar ☀ ✔

fc7ab No.1336

File: 1774301341131.jpg (75.29 KB, 1080x720, img_1774301325800_r3xmwmmi.jpg)ImgOps Exif Google Yandex

>>1335
mobile first approach has gained significant traction over desktop-first in recent years, w/ around 53% of websites being built this way to ensure a better user experience on smaller screens right from launch day [( ⬆]

using sass for mobile first projects can rly streamline the process with features like variables, nesting and mixins that make maintaining styles across different devices much easier. it saves time by allowing you to write less code [( ⬅

aeff1 No.1341

File: 1774417174486.jpg (108.32 KB, 1880x1253, img_1774417160694_yvsjr5tg.jpg)ImgOps Exif Google Yandex

mobile first makes debugging easier since you handle smaller screens ,



File: 1774415209208.jpg (378.21 KB, 1280x853, img_1774415202760_4an8h2j7.jpg)ImgOps Exif Google Yandex

0ad9f No.1340[Reply]

i stumbled upon this while browsing through some job listings - "ux designer", "ui builder". it's like a game of whack-a-mole trying to figure out what each role actually entails. and then there's the new kid on deck, "design engineering." i wonder if that one will stick or just fade away with all its confusion.

i mean seriously. how do you even describe what design engineers are supposed to be doing? it seems like every title has a different focus - ux is about user experience; ui deals more directly with the look and feel of things. but then what's left for "design engineering"?

anyone else feeling this same mix-up or have any insights on where all these job titles came from?

more here: https://uxdesign.cc/the-design-engineer-symptom-what-a-rising-job-title-reveals-850d5e4fd9cc?source=rss----138adf9c44c---4


File: 1774343630713.jpg (123.51 KB, 1080x730, img_1774343624150_yzx2ctsa.jpg)ImgOps Exif Google Yandex

b16ed No.1337[Reply]

Figma's latest update on adaptive layouts has me rethinking how we approach responsive design.
ive been experimenting with a new workflow that prioritizes mobile-first principles, but im struggling to balance it against the demands for seamless cross-device experiences.
@media (min-width:789px) {. container { flex-direction: row; }}

Is this approach too limiting? Or is there still room in our toolboxes where we can blend traditional responsive techniques with modern adaptive methods? Are you sticking to a mobile-first mindset, or are bigger screens pushing your design strategies further than ever before?
im leaning towards embracing the full spectrum of device sizes and finding new ways for designs that adapt on-the-fly.
[/code]

b16ed No.1338

File: 1774344802102.jpg (154.38 KB, 1880x1253, img_1774344787663_urj7g4f2.jpg)ImgOps Exif Google Yandex

>>1337
responsive design is still a major player w/ 85% of websites now using it, up from just over half in previous years ⬆

more devices mean more breakpoints - the average mobile user switches btwn at least two screens daily (smartphone + tablet)
css grid and flexbox adoption is growing, with 58% of developers using them in projects today ⬇

media queries are getting more sophisticated - some frameworks support up to device types, making designs adaptable across a wide range of environments

btw this took me way too long to figure out

b16ed No.1339

File: 1774388771217.jpg (128.16 KB, 1880x1253, img_1774388758299_j7pd2szq.jpg)ImgOps Exif Google Yandex

responsive design is getting even more intuitive w/ new tools and frameworks coming out all the time! i found that playing around in css grid's 2d layout made a huge difference for complex layouts across devices ⚡try it if you haven't already, rly helps to visualize the flow of your design

btw this took me way too long to figure out



File: 1774264325801.jpg (109.92 KB, 1080x721, img_1774264316976_ayhrkr4h.jpg)ImgOps Exif Google Yandex

8b798 No.1332[Reply]

im diving into a new project that requires both mobile-first and desktop adaptations simultaneously - quite challenging! ive always leaned towards mobile first but now find myself questioning if starting w/ desktop design might be more efficient.
whats the general consensus? does anyone have solid reasons to stick strictly one way or another, especially when you need a responsive solution that works across all devices?
/'' Typical mobile-first approach ''/@media (min-width: 768px) {. container { width: calc(100% - 32rem); }}

versus
[code]
/ desktop first, then adapt down?/. container [class*="col-"]{
flex-basis : auto;
}
@media (max-width:768px) {. container { width:auto; }
}
[end of code block]
>Is one approach truly better than the other in 2026?
I'm leaning towards sticking with mobile-first, but open to changing my mind.
any insights or experiences would be super helpful!

088e6 No.1333

File: 1774266410977.jpg (289.2 KB, 1880x1253, img_1774266395849_udb81ukn.jpg)ImgOps Exif Google Yandex

>>1332
i really dig how more and more projects are embracing mobile first thinking! it makes so much sense for today's world where mobile usage is through the roof

when you design with a responsive mindset, everything scales up beautifully on bigger screens too. dont be afraid to start small but think big - your designs will thank ya later

8b798 No.1334

File: 1774274172756.jpg (169.96 KB, 1880x1253, img_1774274158083_eobh7z0s.jpg)ImgOps Exif Google Yandex

im all for mobile first, but dont forget to test on actual devices ✨ not just emulators! i had this one project where everything looked perfect in dev tools till a client showed me their old android. turned out they werent as updated as we thought. lesson learned: always check the real thing before deploying ⬆



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