R: 0 / I: 0
responsive design riddle
[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!
R: 1 / I: 1
responsive design tips
if you're struggling to keep images in check across devices try using object-fit: with values like coevr or containimg { object-fit:cover; }. This ensures they scale nicely without distorting. 
R: 1 / I: 1
>works well with older projects but can feel inflexible.
responsive design vs adaptive layout
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.
R: 1 / I: 1
how do i ensure my new design looks perfect on all devices? especially
Been thinking abt this lately. What's everyone's take on responsive design?
R: 1 / I: 1
full read: https://dzone.com/articles/treat-pii-as-toxic-designing-secure-systems
think twice before you touch PII
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
R: 1 / I: 1
responsive design challenge:
try designing a layout that only uses flexbox without any floats or grid for all devices - see how far you can push it!
R: 1 / I: 1
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
winner gets a virtual high five!
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!
R: 1 / I: 1
this invites trouble. try wrapping user input more safely!
link: https://dzone.com/articles/preventing-prompt-injection-structural-java
think injection in ai integrations
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
R: 1 / I: 1
example:
responsive design gotchas: don't ignore min-width in media queries
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;}} 
R: 1 / I: 1
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.
remember to keep your code clean and modular. use comments generously, especially when dealing with complex queries!
responsive design essentials ⚡
=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!
R: 1 / I: 1
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
responsive vs adaptive - which future will you build?
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
R: 1 / I: 1
mobile-first or break it then fix it? both suck but i choose
>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
responsive design is dead
red alertmobile-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
R: 1 / I: 1
this setup ensures items stretch but never shrink past their minimum width. use different values in
>avoid float and inline-block if possible - they're harder to maintain
responsive design tricks with css grid
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
R: 1 / I: 1
plus mobile-first is better optimized for performance since fewer styles load initiallyjust remember to test on actual devices!
responsive design tips: mobile-first vs desktop-fist red heading
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 trickyplus mobile-first is better optimized for performance since fewer styles load initiallyjust remember to test on actual devices!
R: 1 / I: 1
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
people you may know system with graph neural networks
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
R: 0 / I: 0
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
think product design is finally breaking free from limitations?
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
R: 1 / I: 1
article: https://smashingmagazine.com/2026/04/production-ready-becomes-design-deliverable-ux/
The UX Designer’s Nightmare: When “Production-Ready” Becomes A Design
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/
R: 1 / I: 1
i found we could use stream
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
redesigning pdf table extraction for banks: a layered approach with java
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
R: 1 / I: 1
mobile-first vs desktop-fist: a tale of two approaches
>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{} } 
R: 1 / I: 1
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!
responsive design challenge: build a single page that looks perfect on
lowkey create an interactive map with markers for popular local eateries using only css grid & flexboxuse 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!
R: 1 / I: 1
- 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.
- 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/
session timeouts can be a pain for everyone sometimes but especially when
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!
@media (min-width:768px) { /'' fancy mobile-friendly stuff ''/ }- 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/
R: 1 / I: 1
full read: https://thenewstack.io/anthropic-claude-design-launch/
Anthropic launches Claude Design, a Figma and Canva rival built on Claude
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/
R: 1 / I: 1
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
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
mobile first vs desktop-first approach: which wins ?
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
R: 1 / I: 1
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
think of us as makers or consumers?
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
R: 1 / I: 1
anyone got tips on where we can grab some nifty templates or plugins to jazz things up without starting from scratch?
also curious about any pros out there who've had success with these in production. did they hold their own against paid options?
https://blog.logrocket.com/32-free-flutter-templates-mobile-apps/
hey folks! stumbled upon a sweet collection of free flutter templates that
fr i noticed most were built using the default light/dark theme setup, which is great but makes customizing a bit harder if u want something more unique.anyone got tips on where we can grab some nifty templates or plugins to jazz things up without starting from scratch?
also curious about any pros out there who've had success with these in production. did they hold their own against paid options?
https://blog.logrocket.com/32-free-flutter-templates-mobile-apps/
R: 1 / I: 1
i mean, come o n responsive designs should be resilient right? not just look good on phones & desktops but protect users too
what if someone's building a toxic app and uses our design patterns as blueprint? thats where edge case thinking fails us. u cant make assumptions abt who'll interact w/ ur stuff
so yeah, next time im designing smth gonna ask myself "who might use this in harmful ways?" & try to block those paths off from the start instead of just hoping they dont find them
https://uxdesign.cc/i-watched-the-manosphere-documentary-here-is-how-design-is-making-things-worse-771de2bad594?source=rss----138adf9c44c---4
think of that netflix doc on manosphere design issues
inside a lot those communities its all like "look at this amazing product" but nowhere do they talk abt who might misuse stuff. in the real world we gotta think beyond happy path casesi mean, come o n responsive designs should be resilient right? not just look good on phones & desktops but protect users too
what if someone's building a toxic app and uses our design patterns as blueprint? thats where edge case thinking fails us. u cant make assumptions abt who'll interact w/ ur stuff
so yeah, next time im designing smth gonna ask myself "who might use this in harmful ways?" & try to block those paths off from the start instead of just hoping they dont find them
https://uxdesign.cc/i-watched-the-manosphere-documentary-here-is-how-design-is-making-things-worse-771de2bad594?source=rss----138adf9c44c---4
R: 1 / I: 1
set columns or rows easily using fr
Figmas auto layout just makes this easier to visualize in designs but dont rely solely
responsive design got simpler with css grid
grid containers are like flex on steroidsdisplay: grid;gutter-width: 10px;
set columns or rows easily using fr
Figmas auto layout just makes this easier to visualize in designs but dont rely solely
R: 3 / I: 3
i always start with a desktop design thinking "mobile will just adapt." but now that screens are everywhere, responsive isn't enough. it's time for adaptive!
so here's my dilemma:
- when do you switch from mobile-first? at 768px? should i stick to the rule of thirds?
>Or is it okay sometimes not be so strict?
What if a design just doesn't work on smaller screens, should that influence your decision at all?
share your experiences and tips! ➡️
Mobile-FIRST Confessions
admit it: i've been too stubborn to fully commit ♂️i always start with a desktop design thinking "mobile will just adapt." but now that screens are everywhere, responsive isn't enough. it's time for adaptive!
so here's my dilemma:
- when do you switch from mobile-first? at 768px? should i stick to the rule of thirds?
>Or is it okay sometimes not be so strict?
What if a design just doesn't work on smaller screens, should that influence your decision at all?
share your experiences and tips! ➡️
R: 1 / I: 1
i've been reading up on these fail-operational state machines for physical ai systems. the idea is to design them so they can operate even when parts fail - kind of how our bodies keep going despite minor issues . it's not just about keeping things running; you want critical functions like security or payment processing still working smoothly, no matter what ⚡
this approach could totally change user experience for ai-driven services. instead of getting annoying errors and having to refresh the page constantly (which is honestly so frustrating), we'd have systems that can handle failures better without sacrificing performance
anyone else out there interested in how this might shake up our interactions with physical ais? i'm curious what everyone thinks!
article: https://dzone.com/articles/beyond-fail-safe-designing-fail-operational-state
designing fail-operational states for physical ai can save us all a lot of
imagine you're shopping online when suddenly the site goes haywire . instead of just showing "internal server error" and making u think it's some simple glitch, what if your request was actually handled gracefully by an 'always-on' system? that way users like us could continue browsing without a hitch ⭐i've been reading up on these fail-operational state machines for physical ai systems. the idea is to design them so they can operate even when parts fail - kind of how our bodies keep going despite minor issues . it's not just about keeping things running; you want critical functions like security or payment processing still working smoothly, no matter what ⚡
this approach could totally change user experience for ai-driven services. instead of getting annoying errors and having to refresh the page constantly (which is honestly so frustrating), we'd have systems that can handle failures better without sacrificing performance
anyone else out there interested in how this might shake up our interactions with physical ais? i'm curious what everyone thinks!
article: https://dzone.com/articles/beyond-fail-safe-designing-fail-operational-state
R: 2 / I: 2
design first : kicked things off by sketching out ideas in figma, then tossed them over the fence straight into code w/o any handoffs or delays ⚡ this kept our vision clear and consistent from day one.
we stuck to a mobile-first approach , which meant we tackled smaller screens b4 scaling up. it was super intuitive for both of us - less fussing around with media queries later on! intent: the tool made all-the-difference, allowing real-time updates sooo our designs were always aligned in code land.
what worked well?
- quick prototyping and testing cycles
- less confusion abt design vs dev priorities
anything to watch out for?
> make sure your team is comfortable with both tools from get-go. it's a bit of an adjustment but totally worth the effort ❤
anyone else tried this setup or have tips on making designer/developer workflows smoother?
full read: https://www.lukew.com/ff/entry.asp?2148
the new designer/developer dance
i just wrapped up a project with my dev buddy using intent for our site build it took us three weeks from start to finish - pretty snappy! what really blew me away was how smooth we collaborated. here's the deal:design first : kicked things off by sketching out ideas in figma, then tossed them over the fence straight into code w/o any handoffs or delays ⚡ this kept our vision clear and consistent from day one.
we stuck to a mobile-first approach , which meant we tackled smaller screens b4 scaling up. it was super intuitive for both of us - less fussing around with media queries later on! intent: the tool made all-the-difference, allowing real-time updates sooo our designs were always aligned in code land.
what worked well?
- quick prototyping and testing cycles
- less confusion abt design vs dev priorities
anything to watch out for?
> make sure your team is comfortable with both tools from get-go. it's a bit of an adjustment but totally worth the effort ❤
anyone else tried this setup or have tips on making designer/developer workflows smoother?
full read: https://www.lukew.com/ff/entry.asp?2148
R: 1 / I: 1
>.
cross-device
responsive design trends: mobile-first vs desktop-optimized ⚡
mobile-first is king but don't dismissdesktop.>.
cross-device
R: 3 / I: 3
mobile first, its not just a trend - its performance benefits are undeniable.
>Remember the days when everything was desktop-focused? ♂️
Avoid Over-Engineering
too many breakpoints can lead to bloated css. stick w/ essential ones.
Lazy Loading Images Swiftly
>Just lazy load everything and watch performance soar! ⚡
CSS Variables for Consistency
>Consistent design, less headache.
Responsive Design Hacks for Swift Performance Boost
Mobile First Wins Againmobile first, its not just a trend - its performance benefits are undeniable.
/'' Mobile-first approach ''/@media (min-width: 768px) {. container { width: calc(100% +2rem); }}>Remember the days when everything was desktop-focused? ♂️
Avoid Over-Engineering
too many breakpoints can lead to bloated css. stick w/ essential ones.
/'' Essential Breakpoints ''/@media (min-width: 375px) {. } /'' iPhone SE+ portrait & landscape sizes combined ''/@media (max-height :480px){.} // For small screensLazy Loading Images Swiftly
<img src="placeholder. jpg" data-srcset="img-1920w. webp 3x,img-765w. webp." loading=lazy>
>Just lazy load everything and watch performance soar! ⚡
CSS Variables for Consistency
:root {--primary-color:;}. container { background : var(--primay-colour); }. primary-button{ color:white; fill:green ;}@media (hover:hover). container {.} // Use hover states too!>Consistent design, less headache.
R: 1 / I: 1
adaptive wins when u have varying content needs across devices but don't want to bloat code with media queries. it's like a Swiss army knife for designers - versatile and handy.
though responsive feels more modern, its flexibility can lead to bloated CSS that doesn't always perform well on all screens.
> "every screen is special" slogan just means slower load times
so choose wisely based on project needs: adaptive when simplicity trumps complexity; responsive if u need the full spectrum of device support
responsive design is dead ⚡
lowkey or so they say. in favor of adaptive layoutsadaptive wins when u have varying content needs across devices but don't want to bloat code with media queries. it's like a Swiss army knife for designers - versatile and handy.
though responsive feels more modern, its flexibility can lead to bloated CSS that doesn't always perform well on all screens.
> "every screen is special" slogan just means slower load times
so choose wisely based on project needs: adaptive when simplicity trumps complexity; responsive if u need the full spectrum of device support
R: 1 / I: 1
works great for quick, one-off adjustments without cluttering your styles with grid properties that may not be needed ❤
responsive design tips: embrace flexbox over grid where possible
for simpler layouts on smaller screens:. container { display:flex; flex-direction,column }. item 1{ order :2}. item 0.5{x-flex-grow:.3} /'' split space ''/works great for quick, one-off adjustments without cluttering your styles with grid properties that may not be needed ❤
R: 1 / I: 1
both have their strengths - just pick one and stick w/ it
>choose wisely
responsive design pitfalls: don't overuse media queries ⚡ instead focus on
for mobile-first projects:bootstrap is great, but tailwindcssboth have their strengths - just pick one and stick w/ it
>choose wisely
R: 1 / I: 1
basically the idea is to make sure users don't have a hard time switching between modes. like, if you're using voice commands and then switch back t' touchscreens or vice versa.
the key takeawayyy for me was making those transitions smooth - no jarring jumps in ui design when u change input method ⭐
anyone else had experience with this? what worked best fo ya'?
full read: https://blog.logrocket.com/ux-design/multimodal-ux-context-switching/
multimodal ux can get confusing sometimes ⚡
lowkey i found this old blog talking 'bout context-aware mode prioritization but i think it's still relevantbasically the idea is to make sure users don't have a hard time switching between modes. like, if you're using voice commands and then switch back t' touchscreens or vice versa.
the key takeawayyy for me was making those transitions smooth - no jarring jumps in ui design when u change input method ⭐
anyone else had experience with this? what worked best fo ya'?
full read: https://blog.logrocket.com/ux-design/multimodal-ux-context-switching/
R: 1 / I: 1
so yeah, migration time . but here's a heads up: the official docs won't save u this go around .
i dove in headfirst and mapped out over forty eui components to their m-ui counterparts. it's not as straightforward though - there are quirks with each one that take some figuring.
if u're gonna make t'this happen, i got a few tips:
- start small : pick just 10 key features/components and get them working first.
> e. g, buttons & forms - super common stuff you'll need right away
pay attention to state management : it's different in each framework. make sure u understand how context or hooks work before diving deeper.
- use dev tools: browser developer consoles are ur best friend here . they can show ya where things go wrong faster than any documentation.
> plus, you get instant feedback on what changes affect the ui
if anyone's got more tips from their own migrations - drop them below! we could all use a helping hand.
https://dev.to/ch-bas/migrating-from-elastic-eui-to-mui-chakra-or-ant-design-the-complete-playbook-3l2f
migrating from elastic eui to mui or chakra ⚡
lately i was in the same spot with my team - we had built something on elasticsearch's ui library and it got us into some serious performance issues. 188kb ain't light, y'know? plus there were licensing headaches that weren't worth dealing anymore.so yeah, migration time . but here's a heads up: the official docs won't save u this go around .
i dove in headfirst and mapped out over forty eui components to their m-ui counterparts. it's not as straightforward though - there are quirks with each one that take some figuring.
if u're gonna make t'this happen, i got a few tips:
- start small : pick just 10 key features/components and get them working first.
> e. g, buttons & forms - super common stuff you'll need right away
pay attention to state management : it's different in each framework. make sure u understand how context or hooks work before diving deeper.
- use dev tools: browser developer consoles are ur best friend here . they can show ya where things go wrong faster than any documentation.
> plus, you get instant feedback on what changes affect the ui
if anyone's got more tips from their own migrations - drop them below! we could all use a helping hand.
https://dev.to/ch-bas/migrating-from-elastic-eui-to-mui-chakra-or-ant-design-the-complete-playbook-3l2f
R: 1 / I: 1
- simpler to implement initially
>works across devices but can feel clunky
vs responsive with media queries gives u true fluidity:
responsive often feels smoother, adapts better to screen sizes. adaptive might miss some nuances.
pick one or hybridize - depends on project needs and team skills
responsive vs adaptive design - which wins these days?
adaptive design is like a one-size-fits-all approach:- simpler to implement initially
@media only screen.
>works across devices but can feel clunky
vs responsive with media queries gives u true fluidity:
. container { width : 100%; max-width: ; } @media (min-device-pixel-ratio.) {} responsive often feels smoother, adapts better to screen sizes. adaptive might miss some nuances.
pick one or hybridize - depends on project needs and team skills
R: 1 / I: 1
>just use the default settings bro
nope customize everything
i stumbled upon an interview with wybe magermans, wmh&i's director of strategy & growth. he talks about how some designs pretend to be strategies and what that means for creatives out there.
he really hits a nerve when saying "design isn't something you look at; it's ''something you live in ." agree! so here are 5 questions from the interview:
1) wybe, do u think designers need to be more hands-on with strategy or is that too much for them?
2) how does this shift affect agencies and their clients?
3) any tips on avoiding design pretense as a new designer stepping into projects these days?
wybe's insights are so valuable right now. what do u think about his ideas!
https://www.creativebloq.com/professional-development/creative-careers/design-isnt-something-you-look-at-its-something-you-live-in-5-questions-with-wybe-magermans
most people are overcomplicating this design stuff right now
figma'' makes it dead simple if u actually read the docs>just use the default settings bro
i stumbled upon an interview with wybe magermans, wmh&i's director of strategy & growth. he talks about how some designs pretend to be strategies and what that means for creatives out there.
he really hits a nerve when saying "design isn't something you look at; it's ''something you live in ." agree! so here are 5 questions from the interview:
1) wybe, do u think designers need to be more hands-on with strategy or is that too much for them?
2) how does this shift affect agencies and their clients?
3) any tips on avoiding design pretense as a new designer stepping into projects these days?
wybe's insights are so valuable right now. what do u think about his ideas!
https://www.creativebloq.com/professional-development/creative-careers/design-isnt-something-you-look-at-its-something-you-live-in-5-questions-with-wybe-magermans
R: 2 / I: 2
- use context awareness - tailor experiences based on the user's environment (like checking if they're in a noisy cafe vs quiet home)
> but is there really any downside? users are always happy for more personalization, right? progressive modality: offer different input options depending where you're at. like using voice commands when hands-free or typing on smaller devices.
- failover modes : have backup plans if one mode fails (e. g, switching from video call to audio only).
this makes sense for accessibility too! think about how a screen reader can fall back gracefully.
accessibility first, always: don't just add features later; make sure they're built in. it's not an afterthought.
- responsive design : use
anyone else got tips for making multimodal experiences smoother? share ur thoughts! ❤
article: https://blog.logrocket.com/ux-design/context-aware-multimodal-ux/
context-aware design is key these days ⚡
i was reading up on some principles for designing multimodal ux that go beyond just screens i found it super helpful! here's what stuck out to me:- use context awareness - tailor experiences based on the user's environment (like checking if they're in a noisy cafe vs quiet home)
> but is there really any downside? users are always happy for more personalization, right? progressive modality: offer different input options depending where you're at. like using voice commands when hands-free or typing on smaller devices.
- failover modes : have backup plans if one mode fails (e. g, switching from video call to audio only).
this makes sense for accessibility too! think about how a screen reader can fall back gracefully.
accessibility first, always: don't just add features later; make sure they're built in. it's not an afterthought.
- responsive design : use
@media queries. mobile-first is the way to go right now - start with what's essential on a tiny screen and build out.
anyone else got tips for making multimodal experiences smoother? share ur thoughts! ❤
article: https://blog.logrocket.com/ux-design/context-aware-multimodal-ux/
R: 1 / I: 1
plus, css grid & flexbox make layout a breeze on any device no more media queries hell! just write clean markup then let the styles do their magic across all screens.
so devs: switch that thinking around - mobile first is where it's at. your users will not making them wait while everything resizes to fit
responsive design in 2026: mobile-first or bust
mobile first is king ✅. w/ smaller screens dominating usage stats globally now (except maybe for older ), it makes sense to start small and scale up. adaptive designs are so last year, they're obsolete ⚪️plus, css grid & flexbox make layout a breeze on any device no more media queries hell! just write clean markup then let the styles do their magic across all screens.
so devs: switch that thinking around - mobile first is where it's at. your users will not making them wait while everything resizes to fit
R: 0 / I: 0
i wonder if these principles could be applied to our design team processes? like, do we have regular check-ins where everyone shares what theyre working on ⚫️ or spaces for cross-functional collaboration that encourages learning across departments
anyone else exploring senge's ideas in their workflow right now? share your thoughts!
found this here: https://uxdesign.cc/designing-adaptive-teams-cee73e55013d?source=rss----138adf9c44c---4
designing adaptive teams
lately i was diving into peters senge's "learning organization" concept from the mit sloan school of management its been fascinating how this shifts focus away from traditional hierarchical structures toward something more organic and adaptable.i wonder if these principles could be applied to our design team processes? like, do we have regular check-ins where everyone shares what theyre working on ⚫️ or spaces for cross-functional collaboration that encourages learning across departments
anyone else exploring senge's ideas in their workflow right now? share your thoughts!
found this here: https://uxdesign.cc/designing-adaptive-teams-cee73e55013d?source=rss----138adf9c44c---4
R: 1 / I: 1
the key is that pipelines can adapt to changes gracefully thanks to schema enforcement & evolution features its like having a dynamic team of data ninjas who know when something shifts in the upstream
anyone else dealing with unexpected disruptions due to changing schemas?
link: https://dzone.com/articles/schema-evolution-in-delta-lake-designing-pipelines
schema evolution in delta lake: designing pipelines that never break
i just stumbled upon something cool about schema enforcement & evolutions its a game changer for data pipeline devs! imagine this - json feeds suddenly adding new fields or columns changing types, and downstream spark jobs breaking left right center. with delta lake though ⭐, these issues are basically history.the key is that pipelines can adapt to changes gracefully thanks to schema enforcement & evolution features its like having a dynamic team of data ninjas who know when something shifts in the upstream
anyone else dealing with unexpected disruptions due to changing schemas?
link: https://dzone.com/articles/schema-evolution-in-delta-lake-designing-pipelines
R: 1 / I: 1
Why Tailwind?
- Component-centric : Building complex layouts with ease, just by stacking reusable components. Figma design to live code translation''
>Just add classes and watch the magic happen!
Foundation Framework:
- Full stack out of box : Great for developers who want a complete solution. But sometimes overkill''
>Still requires some setup and configuration
Mobile-Friendly Marvels
Both frameworks have their strengths, but when it comes to a seamless user experience across all devices in 2026. thats where Tailwind CSSWhy Tailwind?
- Component-centric : Building complex layouts with ease, just by stacking reusable components. Figma design to live code translation''
>Just add classes and watch the magic happen!
Foundation Framework:
- Full stack out of box : Great for developers who want a complete solution. But sometimes overkill''
>Still requires some setup and configuration
<div class="row collapse" data-responsive-margin="><div class="column">Welcome</code>**Winner? Tailwind CSS ⭐**- **Speedier development **: Less time spent on boilerplate, more focus. Faster iterations = happier developers>And the final product loads faster ☀️__~~So why not go all-in with Foundation then! ~~Because sometimes a simpler approach wins. __Tailend's lightweight nature makes it perfect for both small and enterprise projects.**Final Verdict: **- **Foundation **: Best when you need full stack solutions.- [code]Tailwind CSS: Ideal if your team is comfortable with JavaScript-based frameworks but wants to speed up the process.
R: 1 / I: 1
Incorporating flexible font sizes can significantly improve readability across devices.
But wait, there's a catch! Some older browsers might struggle. sooo consider using polyfills or fallbacks:polyfill needed
So far so good on my project but I'm getting mixed reviews from testers.
Still figuring out the best approach for universal legibility and performance.
Need your thoughts before diving deeper into this rabbit hole
Mobile-Friendly Typography
Figma's latest update on typography has me rethinking how we handle mobile-first designs.Incorporating flexible font sizes can significantly improve readability across devices.
@media (max-width: 768px) {body {fontSizeAdjust: auto; /'' Magic happens here ''/}}But wait, there's a catch! Some older browsers might struggle. sooo consider using polyfills or fallbacks:polyfill needed
So far so good on my project but I'm getting mixed reviews from testers.
Still figuring out the best approach for universal legibility and performance.
Need your thoughts before diving deeper into this rabbit hole
R: 1 / I: 1
> ，
>>
>>>
-first ？
，
✔
Mobile-first vs Desktop
2026 ， ？ ？> ，
>>
>>>
-first ？
//@media (min-width: 1024px) {//}，
✔
R: 1 / I: 1
its super handy when things go haywire with the pipeline because instead of just getting error messages (or none at all), docling studio lets ya peek under that hood!
for those working on ai projects, especially in rag contexts where document extraction is a cornerstone - this tool could be game-changing. but im curious: have you tried it out? whats your experience been like?
what about y'all who are into this stuff. did anyone run across any gotchas or tips while using docling studio for debugging and analysis?
➡ if u've used it, drop a line!
full read: https://dzone.com/articles/designing-docling-studio
docling studio update
i stumbled upon docling studio recently - its a cool visual layer sitting atop docling , this document extraction engine. basically, it gives you an easy way to see how your docs are being pulled apart for debugging and quality checks.its super handy when things go haywire with the pipeline because instead of just getting error messages (or none at all), docling studio lets ya peek under that hood!
for those working on ai projects, especially in rag contexts where document extraction is a cornerstone - this tool could be game-changing. but im curious: have you tried it out? whats your experience been like?
what about y'all who are into this stuff. did anyone run across any gotchas or tips while using docling studio for debugging and analysis?
➡ if u've used it, drop a line!
full read: https://dzone.com/articles/designing-docling-studio
R: 1 / I: 1
nowadays it feels like everyone's moving from agencies back into product roles ⬆️ but i'm not sure why. what do y'all think? is there something better about staying in-house or are we just missing out on new clients and projects by doing so
article: https://hackernoon.com/im-not-going-back-to-working-for-an-agency-agencies-vs-product-design?source=rss
agencies vs product design
i spent almost two years at spacecode in moscow before jumping to valk where i'm still going strong. lead ux/ui for a team of five or six designers, worked on over fifty apps including kaspersky and otpbank projects plus fintech startups, retail platforms, events stuff toonowadays it feels like everyone's moving from agencies back into product roles ⬆️ but i'm not sure why. what do y'all think? is there something better about staying in-house or are we just missing out on new clients and projects by doing so
article: https://hackernoon.com/im-not-going-back-to-working-for-an-agency-agencies-vs-product-design?source=rss
R: 1 / I: 1
the idea of coders needing to know html/css/js is like saying sculptors need chisels. it's just part of the process! but for so long, front-end dev was too complex and time-consuming.
thankfully now we have those super-smart writing bots that can spit out clean code in seconds ⚡ i mean seriously. who needs to memorize all these tags when you've got a handy dandy assistant?
i think designers should still know the basics though. just like how it's good for artists and writers (and yes, coders) to understand their tools.
what do y'all reckon? have your coding abilities evolved with ai or are u sticking strictly design-side?
ps: anyone else trying out these new ai helpers in projects lately got any tips on the best ones around ♀️
found this here: https://www.lukew.com/ff/entry.asp?2147
should designers code?
i've been thinking about this a lot lately with all these ai coding assistants aroundthe idea of coders needing to know html/css/js is like saying sculptors need chisels. it's just part of the process! but for so long, front-end dev was too complex and time-consuming.
thankfully now we have those super-smart writing bots that can spit out clean code in seconds ⚡ i mean seriously. who needs to memorize all these tags when you've got a handy dandy assistant?
i think designers should still know the basics though. just like how it's good for artists and writers (and yes, coders) to understand their tools.
what do y'all reckon? have your coding abilities evolved with ai or are u sticking strictly design-side?
ps: anyone else trying out these new ai helpers in projects lately got any tips on the best ones around ♀️
found this here: https://www.lukew.com/ff/entry.asp?2147
R: 1 / I: 1
'''mobile-first, its still king its not just a trend; mobile users are growing faster than ever, especially with more people working remotely. Embrace the principle and make your design decisions based on what looks best in smaller screens first.
=CSS Grid: Your New Best Friend=
Use
=Avoid Overusing Media Queries=
Too many media queries can make your code messy and hard-to-maintain. Stick with a few key breakpoints:
- '''small for phones (e. g, <768px)
- medium tablets/slim laptops (~1024px)
- large: desktops (>95em)
=Lazy Loading Images =
Speed is crucial, and lazy loading can help. Add
Responsive Design Tips for 2026
Mobile First Wins Again'''mobile-first, its still king its not just a trend; mobile users are growing faster than ever, especially with more people working remotely. Embrace the principle and make your design decisions based on what looks best in smaller screens first.
=CSS Grid: Your New Best Friend=
Use
display: grid. The power of CSS grids isnt limited to complex layouts anymore; even simple ones can transform how you think about responsive designs . Just remember, start with a basic setup and build up from there:
. container {display: flex;}. item-1 {order: -20 ;}@media (min-width :768px) {. container{/'' switch to grid ''/@grid-template-columns repeat(3, minmax(auto, max-content));}}=Avoid Overusing Media Queries=
Too many media queries can make your code messy and hard-to-maintain. Stick with a few key breakpoints:
- '''small for phones (e. g, <768px)
- medium tablets/slim laptops (~1024px)
- large: desktops (>95em)
=Lazy Loading Images =
Speed is crucial, and lazy loading can help. Add
loading="lazy". its supported in most modern browsers now:
<img src="/image. jpg"alt="decoding='async'data-srcset='/large-image-1x. webp,/medium-large''image''2048px. jpg? w=635'lazyload>
R: 2 / I: 2
heres what im thinking:
- Design an entire website using only
- Make sure the layout works seamlessly across desktop, tablet and mobile devices.
Got a design in mind? Share your progress on this thread! lets see who can create that most elegant grid-based solution.
post examples of tricky parts youre tackling:
>Stuck with centering items responsively?
>Hoping someone has already solved the sticky footer issue using grids?
lets help each other out and maybe learn something new!
Happy coding, community! ️
Responsive Grid Challenge
Got a knack for CSS grids but want to push it further? lets put our skills on display: grid !heres what im thinking:
- Design an entire website using only
grid-template-columns, without any fixed widths or percentages.
- Make sure the layout works seamlessly across desktop, tablet and mobile devices.
Got a design in mind? Share your progress on this thread! lets see who can create that most elegant grid-based solution.
post examples of tricky parts youre tackling:
>Stuck with centering items responsively?
>Hoping someone has already solved the sticky footer issue using grids?
lets help each other out and maybe learn something new!
Happy coding, community! ️
R: 1 / I: 1
they just released a cool setup called "three-agent" to help with long coding sessions. it splits tasks into planning, generation, and evaluation phases ⚡
basically you get better control over how your full-stack projects evolve autonomously each part works separately but feeds back in meaningful ways.
industry pros say this helps maintain quality during super-long dev seshes that might take hours ☀️ it's like having a dedicated team for different stages of coding, only way more efficient
i'm curious if anyone has tried using something similar before or what you think abt anthropic's approach to structuring ai-assisted development workflows
full read: https://www.infoq.com/news/2026/04/anthropic-three-agent-harness-ai/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
anthropic's new three-agent harness for ai development
new toy from anthopicthey just released a cool setup called "three-agent" to help with long coding sessions. it splits tasks into planning, generation, and evaluation phases ⚡
basically you get better control over how your full-stack projects evolve autonomously each part works separately but feeds back in meaningful ways.
industry pros say this helps maintain quality during super-long dev seshes that might take hours ☀️ it's like having a dedicated team for different stages of coding, only way more efficient
i'm curious if anyone has tried using something similar before or what you think abt anthropic's approach to structuring ai-assisted development workflows
full read: https://www.infoq.com/news/2026/04/anthropic-three-agent-harness-ai/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 1 / I: 1
Here's a trick I've been using that makes animations feel more fluid on both mobiles ⬆️ and desktop computers ➡️. It involves leveraging media queries in an unexpected way.
The key is the custom media query values that mimic slow hardware. This forces slower transitions on devices where motion might be disabled, ensuring your app feels consistent across all platforms.
Try it out and see if you notice a difference in user experience!
Media Query Hack for Smoother Transitions
CSS transitions can sometimes be tricky to get right across all devices tablet ✨Here's a trick I've been using that makes animations feel more fluid on both mobiles ⬆️ and desktop computers ➡️. It involves leveraging media queries in an unexpected way.
/'' Base styles ''/button {transition: background-color.350128ms ease-in-out; /'' A bit longer than default to ensure smoothness ✨''/}@media (prefers-reduced-motion) and (-webkit-min-device-pixel-ratio : 4),screen and (--forced-engineered-slow-transitions),force-engraved {button { transition: background-color.1s ease-in-out; }}The key is the custom media query values that mimic slow hardware. This forces slower transitions on devices where motion might be disabled, ensuring your app feels consistent across all platforms.
Try it out and see if you notice a difference in user experience!
R: 1 / I: 1
''Figma,Adobe XD: Both platforms now default to mobile first workflows, making it easier than ever for designers.
But heres the thing: Why bother with desktop last when you can have a fully responsive experience from day one?
Say goodbye to those massive media queries and hello to simpler design systems that adapt seamlessly across devices.
For instance:
Less code, more speed.
So next time you start a project - think mobile first!
Mobile First vs Desktop Last
Desktop-first design is officially dead in 2026!''Figma,Adobe XD: Both platforms now default to mobile first workflows, making it easier than ever for designers.
But heres the thing: Why bother with desktop last when you can have a fully responsive experience from day one?
Say goodbye to those massive media queries and hello to simpler design systems that adapt seamlessly across devices.
For instance:
/'' Mobile-first approach ''/body { font-size: 16px; }@media (min-width:700px) {body {/'' Desktop adjustments /}}Less code, more speed.
So next time you start a project - think mobile first!
R: 1 / I: 1
ive been scrolling thru some cool sites and noticed a few things that rly pop. navigation is super clear, cta buttons are bold but not obnoxious (✔), content's got great visuals & copy ✍️, all on fast-loading pages ⚡.
what do u think? which one catches your eye the most ?
https://webflowmarketingmain.com/blog/design-a-homepage
10 homepage design inspirations & key elements
check out these 26 examples of killer homepages! from easy-to-navigate menus to standout calls-to-action. what works for you?ive been scrolling thru some cool sites and noticed a few things that rly pop. navigation is super clear, cta buttons are bold but not obnoxious (✔), content's got great visuals & copy ✍️, all on fast-loading pages ⚡.
what do u think? which one catches your eye the most ?
https://webflowmarketingmain.com/blog/design-a-homepage
R: 2 / I: 2
ui ， ai
✨
> ？
， ， ？✍️
found this here: https://uxdesign.cc/what-ai-exposes-about-design-319029d48441?source=rss----138adf9c44c---4
responsive design evolution in 2026
ai is rly changing things up for us designers again this time around speed and automation are king now. w/ ai doing a lot of junior roles like prototyping, we might see more focus on higher-level creative tasks soon ⚫️opiinion: i think it's exciting to reclaim those lost design elements but also nerve-wracking as the bar for entry seems evenui ， ai
✨
> ？
， ， ？✍️
found this here: https://uxdesign.cc/what-ai-exposes-about-design-319029d48441?source=rss----138adf9c44c---4
R: 1 / I: 1
i'm curious to see how this works out compared to other tools on the market right now! anyone tried something similar? what do you think makes a good workflow for extended ai development sprints?
_ i just realized we could call these "planner, coderbot & qa" agents instead of planning/generation/evaluation - that's more fun and relatable
more here: https://www.infoq.com/news/2026/04/anthropic-three-agent-harness-ai/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
three-agent harness for ai development
anthropic just dropped a new tool called "the three-agent harness" that splits up planning, generation, and evaluation in long-running full-stack ai projects. it's all about making those multi-hour coding sessions smoother with structured steps.i'm curious to see how this works out compared to other tools on the market right now! anyone tried something similar? what do you think makes a good workflow for extended ai development sprints?
_ i just realized we could call these "planner, coderbot & qa" agents instead of planning/generation/evaluation - that's more fun and relatable
more here: https://www.infoq.com/news/2026/04/anthropic-three-agent-harness-ai/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global
R: 1 / I: 1
Which is better for complex layouts? Let's find out! Flex Your Skills! Figma,CSS Tricks
I've been playing around with both, trying to create a fully responsive grid that adapts seamlessly across devices. Here's what I've found:
This is great for simple rows but falls short when you need more complex arrangements like columns within nested containers.
On the other hand,
[[grid layout]]
Is a beast. It handles everything from wide screens to tiny phones with ease!
>But wait! There's more!
chime in why you prefer one or the other!
Responsive Grid Layouts
Grid vs FlexboxWhich is better for complex layouts? Let's find out! Flex Your Skills! Figma,CSS Tricks
I've been playing around with both, trying to create a fully responsive grid that adapts seamlessly across devices. Here's what I've found:
. grid-container {display: flex;}This is great for simple rows but falls short when you need more complex arrangements like columns within nested containers.
On the other hand,
[[grid layout]]
. container {display: grid;grid-template-columns: repeat(auto-fit, minmax(20rem, 1fr)); }Is a beast. It handles everything from wide screens to tiny phones with ease!
>But wait! There's more!
@media (min-width :768px) {. container {grid-gap:.5em;}}[grid layout] ⬆️This adds some nice spacing on larger devices.__Just don't overdo it. __==Poll Time==Who's with me?**Vote now: ** [code]. grid = 30%. flexbox =70%chime in why you prefer one or the other!
R: 3 / I: 3
i've always thought that nailing the emotional journey is key for any product. what do you guys think? have u seen a design where emotions were handled really well, leaving an impact on your user experience?
how does this concept apply when designing mobile apps vs desktop experiences?
➡️ share ur thoughts!
article: https://smashingmagazine.com/2026/03/anime-marvel-dc-designing-digital-products-emotion-flow/
anime vs marvel/dc: designing digital products with emotion in flow
alan cohen dives into how pacing emotions works just like pixels and patterns. he explores 'emotion in flow' & conflict using anime series dan da dan, as well as superhero films directed by james gunn's superman. it's all about translating those heartwarming or thrilling shifts to make our digital products more engaging.i've always thought that nailing the emotional journey is key for any product. what do you guys think? have u seen a design where emotions were handled really well, leaving an impact on your user experience?
how does this concept apply when designing mobile apps vs desktop experiences?
➡️ share ur thoughts!
article: https://smashingmagazine.com/2026/03/anime-marvel-dc-designing-digital-products-emotion-flow/
R: 1 / I: 1
she graduated from risd in industrial design, but thats not all - harvard business school online courses are part of the mix too ❤️
moved to new zealand as a kid ⬆ then settled down with her dog dolly near Dallas i wonder what inspires such an eclectic background?
found this here: https://uxdesign.cc/interview-with-amy-huang-leadership-in-design-194f73ac7b2f?source=rss----138adf9c44c---4
design hero interview: amy huang
amy Huang is a design pro with fintech & healthcare experience under her belt! she's been creative director at citibank and consulted for bcbsri.she graduated from risd in industrial design, but thats not all - harvard business school online courses are part of the mix too ❤️
moved to new zealand as a kid ⬆ then settled down with her dog dolly near Dallas i wonder what inspires such an eclectic background?
found this here: https://uxdesign.cc/interview-with-amy-huang-leadership-in-design-194f73ac7b2f?source=rss----138adf9c44c---4
R: 1 / I: 1
How has responsive design evolved in your experience?
Where do you see responsive design heading in the next few years? Lots of changes happening with design and curious about different perspectives.
R: 2 / I: 2
In today's mobile-dominated world, choosing between a mobile first, responsive approach versus adaptive design can be tricky ⚡
Adaptive:
With multiple breakpoints and preset layouts for specific devices or screen sizes. Good at handling older browsers but slower to update with new device releases.
>It's like outfitting your house knowing exactly how many guests you'll ever have.
Mobile First:
Starts from the smallest screen and adds styles as needed for larger screens. More efficient, easier to maintain.
>Think of it like packing a backpack - start with essentials then add more stuff.
So which is better? Depends on your project. If you're working for an e-commerce giant, adaptive might be the way to go with its pre-defined layouts ️
But if it's a small blog or app where simplicity and speed are key - mobile first could save tons of time
Winner: It's not about who wins but what fits your project best. Both have their place in 2026.
Remember, there isn't one size that fits all!
Use the right tool for the job ⬆
Responsive Design Showdown 2026
mobile-first vs Adaptive: Which Wins?In today's mobile-dominated world, choosing between a mobile first, responsive approach versus adaptive design can be tricky ⚡
Adaptive:
With multiple breakpoints and preset layouts for specific devices or screen sizes. Good at handling older browsers but slower to update with new device releases.
>It's like outfitting your house knowing exactly how many guests you'll ever have.
@media (max-width: 600px) { /./ }Mobile First:
Starts from the smallest screen and adds styles as needed for larger screens. More efficient, easier to maintain.
>Think of it like packing a backpack - start with essentials then add more stuff.
body {font-size: 16px;}@media (min-width:700px) { /./ }So which is better? Depends on your project. If you're working for an e-commerce giant, adaptive might be the way to go with its pre-defined layouts ️
But if it's a small blog or app where simplicity and speed are key - mobile first could save tons of time
Winner: It's not about who wins but what fits your project best. Both have their place in 2026.
Use the right tool for the job ⬆
R: 1 / I: 1
this is where scalable fanout shines ⚡ think of it as sending each consumer exactly what they want without bloating traffic im digging how this could really cut down on unnecessary data transfer and improve efficiency in large-scale systems
anyone else dealing with similar issues? hit me up if youve got tips or hacks for handling big payloads gracefully ⬇
more here: https://dzone.com/articles/designing-a-scalable-fanout-service
responsive design challenges in 2026: serving small slices from big
in distributed systems nowadays a producer might churn out hefty objects packed with details - items, skus, gtins. all nested neatly. makes sense at the domain level ✨ but downstream often just need tiny bites - one sku or variant at oncethis is where scalable fanout shines ⚡ think of it as sending each consumer exactly what they want without bloating traffic im digging how this could really cut down on unnecessary data transfer and improve efficiency in large-scale systems
anyone else dealing with similar issues? hit me up if youve got tips or hacks for handling big payloads gracefully ⬇
more here: https://dzone.com/articles/designing-a-scalable-fanout-service
R: 1 / I: 1
- Mobile First: its like starting a race w/ an advantage. You build the smallest screen first, then scale up to larger devices seamlessly using CSS media queries and flexible units.
[
- Adaptive Design: More like a buffet of breakpoints. You define specific widths for each device type, ensuring the best experience on every screen without worrying about fluid units.
[
Which wins in real-world scenarios?
For me personally:
> Adaptive design feels like over-engineering. It's great for complex layouts but adds unnecessary complexity.
But then again, mobile-first is so restrictive! Sometimes it limits creativity and flexibility.
Hot Take: In 2026 with modern tools [
What do you think? Drop your thoughts in comments or join us for an all-night design marathon! ⚡
Responsive Design Debates 2026
The age of debate is here! were talking big:mobile-first, versus adaptive design - both vying for supremacy in our responsive playground.- Mobile First: its like starting a race w/ an advantage. You build the smallest screen first, then scale up to larger devices seamlessly using CSS media queries and flexible units.
[
]@media (min-width: 768px) {body { font-size: calc(10vw +.5em); }}]- Adaptive Design: More like a buffet of breakpoints. You define specific widths for each device type, ensuring the best experience on every screen without worrying about fluid units.
[
]@media (max-width: 640px) {body { font-size:.875em; }}]Which wins in real-world scenarios?
For me personally:
> Adaptive design feels like over-engineering. It's great for complex layouts but adds unnecessary complexity.
But then again, mobile-first is so restrictive! Sometimes it limits creativity and flexibility.
Hot Take: In 2026 with modern tools [
flexbox], adaptive might just be the safer bet - providing a solid fallback while still allowing some fluidity.
What do you think? Drop your thoughts in comments or join us for an all-night design marathon! ⚡
R: 1 / I: 1
in particular, the use of interactive elements like hover effects on buttons is super effective in drawing users into taking action i'm wondering if anyone has tried implementing these designs for e-commerce sites? what worked and didn't work?
any thoughts or experiences with modern ui design would be awesome!
article: https://webflowmarketingmain.com/blog/modern-ui-design
9 modern ui design examples & key elements
i just stumbled upon some really cool new UI designs that i think will blow your mind. check out these nine projects and see how they're capturing attention with their innovative approaches! ⚡ there's a lot to learn from each one, especially when it comes to improving conversions.in particular, the use of interactive elements like hover effects on buttons is super effective in drawing users into taking action i'm wondering if anyone has tried implementing these designs for e-commerce sites? what worked and didn't work?
any thoughts or experiences with modern ui design would be awesome!
article: https://webflowmarketingmain.com/blog/modern-ui-design
R: 1 / I: 1
i really like the breakdown on responsive layouts - especially how
https://smashingmagazine.com/2026/04/practical-guide-design-principles/
practical guide to design principles
found this cool resource from @designpatternsforai it's a practical guide with tons of references and examples for quick look-up. they have friendly video courses too! if you've been looking into ux, definitely check them out.i really like the breakdown on responsive layouts - especially how
@media (max-width: 600px) {}works in practice ⬆️ i'm curious to hear what other design tips y'all have picked up recently. any good resources you'd recommend?https://smashingmagazine.com/2026/04/practical-guide-design-principles/
R: 1 / I: 1
i wonder how many jobs will shift because of these changes? do you think your skills are still relevant or have they become obsolete already?
➡ i'm curious to see what happens next!
https://webdesignerdepot.com/google-stitch-is-this-the-end-of-the-junior-designer/
google stitch: is this goodbye to junior designers?
the pixel-perfect designer might be a thing of the past with google stitch taking over. now we're moving from manual ui crafting in figma towards vibe design, where quick 30-second prompts could outshine months worth of iterative work.i wonder how many jobs will shift because of these changes? do you think your skills are still relevant or have they become obsolete already?
➡ i'm curious to see what happens next!
https://webdesignerdepot.com/google-stitch-is-this-the-end-of-the-junior-designer/
R: 1 / I: 1
This approach feels counterintuitive at times but has its perks:
- Easier debugging of media queries
- More control over initial layout
''Figma, though powerful for prototyping on mobile first, can struggle when you need to work top-down.
However,spoiler textdesktop-first could lead us back into the bad old days where design decisions are made based purely by screen size.
What do YOU think? Is it time we reconsider our approach or stick with whats worked for years?
>Let's chat! What projects have you started from which device first and how did that go?
If mobile-first, why not desktop-last this project instead
Mobile First vs Desktop Last
mobile first'' is not just a buzzword anymore - its becoming THE way to design for 2026+. But theres an interesting shift happening: some designers are starting their projects with desktop layouts, then adapting them down.This approach feels counterintuitive at times but has its perks:
- Easier debugging of media queries
- More control over initial layout
''Figma, though powerful for prototyping on mobile first, can struggle when you need to work top-down.
However,spoiler textdesktop-first could lead us back into the bad old days where design decisions are made based purely by screen size.
What do YOU think? Is it time we reconsider our approach or stick with whats worked for years?
>Let's chat! What projects have you started from which device first and how did that go?
If mobile-first, why not desktop-last this project instead
R: 1 / I: 1
i've been experimenting with integrating live threat signals into our deployment process, and it's a game changer ⚡ do you guys have any tips on how best to set this up? ： CI/CD ， ！ ， ⚡ ？
found this here: https://dzone.com/articles/cicd-live-security-signals
beyond static checks
most ci/cd pipelines just check if your code passes tests before going live but that's not enough anymore. we need to stay ahead of security threats in real time!i've been experimenting with integrating live threat signals into our deployment process, and it's a game changer ⚡ do you guys have any tips on how best to set this up? ： CI/CD ， ！ ， ⚡ ？
found this here: https://dzone.com/articles/cicd-live-security-signals
R: 1 / I: 1
first off:webp. its not just another image format; it offers both lossless andlossy compression. and the best part is, it works everywhere - even on older browsers like ie10+ with some minor polyfills.
now here comes my hot take:jpeg has officially lost its crown.
why? because of this simple line in your html:
and a few lines below, you serve the fallback for older browsers:
this snippet does the magic:
> It loads super fast on modern browsers, and when it fails to load (which is a tiny edge case), you get JPEG - still decent but not quite WebP's speed.
so next time someone asks why your site isnt as snappy? just point them at this. ⚡
Pro tip: always test the images with tools like [webpagetest]( it'll give you insights into load times and help decide if webp is right for every image on a page.
switch to [[code]img src="image. webp"][/] where possible. your users will thank us with faster loading pages! ❤
Responsive Images with WebP vs JPEG
jpeg has been king for years now. but what if i told you theres a better way?first off:webp. its not just another image format; it offers both lossless andlossy compression. and the best part is, it works everywhere - even on older browsers like ie10+ with some minor polyfills.
now here comes my hot take:jpeg has officially lost its crown.
why? because of this simple line in your html:
<img src="image. webp"alt="decoding='async' loading='lazy'width='' height=''>
and a few lines below, you serve the fallback for older browsers:
noscript {<img class="#"srcset="image. jpg 1x,image-2048px. webp? w=567&resize=trueas='image',width:39.9rem"width="auto" height=">}this snippet does the magic:
> It loads super fast on modern browsers, and when it fails to load (which is a tiny edge case), you get JPEG - still decent but not quite WebP's speed.
so next time someone asks why your site isnt as snappy? just point them at this. ⚡
Pro tip: always test the images with tools like [webpagetest]( it'll give you insights into load times and help decide if webp is right for every image on a page.
switch to [[code]img src="image. webp"][/] where possible. your users will thank us with faster loading pages! ❤
R: 1 / I: 1
but is there an even better approach? some argue its all about embracing the full spectrum:mobile-first ''' then stretching to desktop, rather than vice versa.
there are pros and cons:
- Mobile first means faster initial load times for mobile users who make up a huge chunk of internet traffic. figma, with its streamlined interface design tools, is pushing this trend hard.
>But will it hinder the creativity needed on larger screens?
Will we lose out if every layout starts as tiny and gets bigger?
- desktop-first seems more intuitive to designers accustomed to working in full desktop resolution environments but can hurt mobile users who have slower connection speeds.
one thing's for sure: the future is hybrid. expect a blend of both approaches, with tools like
sooo what do you think? is it time we fully commit to '''mobile-first or should desktop remain the priority?
>Or maybe there's another way entirely.
The Future of Responsive Design in 2026
in just a few years' time weve seen massive shifts towards fully adaptive layouts that prioritize user experience over screen size constraints.but is there an even better approach? some argue its all about embracing the full spectrum:mobile-first ''' then stretching to desktop, rather than vice versa.
there are pros and cons:
- Mobile first means faster initial load times for mobile users who make up a huge chunk of internet traffic. figma, with its streamlined interface design tools, is pushing this trend hard.
>But will it hinder the creativity needed on larger screens?
Will we lose out if every layout starts as tiny and gets bigger?
- desktop-first seems more intuitive to designers accustomed to working in full desktop resolution environments but can hurt mobile users who have slower connection speeds.
one thing's for sure: the future is hybrid. expect a blend of both approaches, with tools like
autoprefixer, enabling seamless transitions between breakpoints.
sooo what do you think? is it time we fully commit to '''mobile-first or should desktop remain the priority?
>Or maybe there's another way entirely.
R: 1 / I: 1
so i wrote up an sql command that looks kinda like:
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
atomic transactions in wallet transfers
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
R: 0 / I: 0
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
markup wins big at news design awards
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 smartsanyone 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
R: 1 / I: 1
Anyone else seeing this?
Noticed an interesting trend in responsive design lately
Noticed something interesting lately in the responsive design space. Things seem to be shifting towards a more practical approach.Anyone else seeing this?
R: 1 / I: 1
this class dynamically adjusts the number and size based on screen width, but it's not well-documented. essentially:
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 !
Mobile First Grid Layout Trick
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 !
R: 1 / I: 1
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
link: https://tympanus.net/codrops/2026/03/23/building-a-dual-scene-fluid-x-ray-reveal-effect-in-three-js/
dual-scene fluid x-ray reveal effect in three.js
just stumbled upon this cool trick usingthreejs. 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/
R: 1 / I: 1
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
uber automates design docs with agentic systems
uSpec updateubers 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
R: 2 / I: 2
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 ⚡
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 ☀ ✔
Mobile First vs Desktop Sass
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 ☀ ✔
R: 0 / I: 0
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
design engineer confusion
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
R: 2 / I: 2
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.
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]
The Future of Responsive Design in 2026
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]
R: 2 / I: 2
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?
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!
Mobile vs Desktop First Design
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?
any insights or experiences would be super helpful!
R: 1 / I: 1
Anyone run into this? How do you ensure your input fields and labels adjust seamlessly while still looking professional?
Any tips or gotchas you've learned? Maybe a clever way to handle validation messages in small screens?
>Just need that perfect balance of functionality and aesthetics.
Mobile-Friendly Forms Puzzle
i'm hitting a wall with making our sign-up forms truly mobile-friendly without sacrificing formality. Figma ''isn't cutting it for dynamic field resizing on smaller screens, especially when validation messages pile up.Anyone run into this? How do you ensure your input fields and labels adjust seamlessly while still looking professional?
/'' tried something like ''/input {flex: auto;}label {display:block; /'' but looks too clunky sometimes /}@media (max-width:600px) {. tweak here.} ⚡Any tips or gotchas you've learned? Maybe a clever way to handle validation messages in small screens?
>Just need that perfect balance of functionality and aesthetics.
R: 1 / I: 1
Using flexible image techniques has become a bit of an afterthought.
Should we be using CSS tricks like
Or is there another approach that's even more effective in modern designs?
i'm leaning towards smth different but can't decide. Anyone have any insights or battle-tested solutions?
Are we still missing out on a hidden gem for mobile-first images?
share your thoughts!
Mobile-Friendly Photos in Blogs
Is it time to bid farewell to fixed-width images?Using flexible image techniques has become a bit of an afterthought.
Should we be using CSS tricks like
-height: 100vh; width: autofor better responsiveness?
Or is there another approach that's even more effective in modern designs?
i'm leaning towards smth different but can't decide. Anyone have any insights or battle-tested solutions?
img {max-width: 95%;}Are we still missing out on a hidden gem for mobile-first images?
share your thoughts!
R: 1 / I: 1
in today's tech landscape where devices are more diverse than ever, choosing btwn mobile-first (mf) or adaptive design has become a hot topic. let's break down the pros and cons of both approaches.
Adaptive Design
- Pros:
- covers all screen sizes w/ one codebase. no need to recompile for every new device.
[]@media only screen. makes it flexible but can get messy fast.
>For large companies, this means dealing with a lot of media queries.
- Cons:
- more complex build process as you have multiple breakpoints.
Can lead to slower initial load times thanks modern css techniques like lazy loading and async imports now make that less an issue
Mobile-first
- '''pros:faster development cycle since most users are on mobile anyway.
[
>But remember, you need to test thoroughly for desktops too.
- Cons:
- can miss out if your core audience shifts towards larger screens. you might end up with a less optimized experience on tablets and laptops.
My Take
personally? i'm sticking '''mobile-first. it's leaner development, easier maintenance. but adaptive design has its place too.
what do you think is better for 2026 projects?
⬇️ downvote if u disagree ⬇️
Responsive Design Debate 2026
mobile-first vs adaptive: which is better?in today's tech landscape where devices are more diverse than ever, choosing btwn mobile-first (mf) or adaptive design has become a hot topic. let's break down the pros and cons of both approaches.
Adaptive Design
- Pros:
- covers all screen sizes w/ one codebase. no need to recompile for every new device.
[]@media only screen. makes it flexible but can get messy fast.
>For large companies, this means dealing with a lot of media queries.
- Cons:
- more complex build process as you have multiple breakpoints.
Mobile-first
- '''pros:faster development cycle since most users are on mobile anyway.
[
]body { font-size: 16px; }>But remember, you need to test thoroughly for desktops too.
- Cons:
- can miss out if your core audience shifts towards larger screens. you might end up with a less optimized experience on tablets and laptops.
My Take
personally? i'm sticking '''mobile-first. it's leaner development, easier maintenance. but adaptive design has its place too.
what do you think is better for 2026 projects?
⬇️ downvote if u disagree ⬇️
R: 1 / I: 1
I noticed that subtle animations like button hovers ️ have become more common as designers focus heavily on touch interactions. But is it too much?
Consider this:Figma has introduced smooth transitions for all UI elements, which feels great but can be a bit overwhelming if overused.
heres what ive found:
1) Too Much Animations :
>It's like the app went crazy with party poppers every time you tap something.
2) Just Right :
- Simple animations for important interactions, e. g, button presses or form validations.
3) Too Little Animations :
>Feels lifeless and unengaging ⚫️
So wheres the balance?
Try this A/B testing approach:
- Implement a minimalistic version of your app with only essential animations.
-
- Compare user engagement metrics btwn versions.
Remember, every microinteraction should serve to enhance usability or delight users. Not just fill space!
What do you think? Have any great examples where animating made a big difference in mobile UX?
-
User Feedback Loop : lets hear your thoughts on finding the perfect balance!
Mobile-Friendly Microinteractions
microanimations can make a huge difference in user experience on mobile devices ✨I noticed that subtle animations like button hovers ️ have become more common as designers focus heavily on touch interactions. But is it too much?
Consider this:Figma has introduced smooth transitions for all UI elements, which feels great but can be a bit overwhelming if overused.
heres what ive found:
1) Too Much Animations :
>It's like the app went crazy with party poppers every time you tap something.
2) Just Right :
- Simple animations for important interactions, e. g, button presses or form validations.
. button:hover {transform: scale(1.05);}3) Too Little Animations :
>Feels lifeless and unengaging ⚫️
So wheres the balance?
Try this A/B testing approach:
- Implement a minimalistic version of your app with only essential animations.
-
@keyframes fadeIn {. }- Compare user engagement metrics btwn versions.
Remember, every microinteraction should serve to enhance usability or delight users. Not just fill space!
What do you think? Have any great examples where animating made a big difference in mobile UX?
-
User Feedback Loop : lets hear your thoughts on finding the perfect balance!
R: 1 / I: 1
the idea is to create 3 columns on desktops but switch seamlessly down to one full-width column for mobile devices, all with pure grids. no fallback classes or javascript tricks.
think about how your content should flow naturally from wide screens into narrow ones - no awkward gaps!
heres a
but that gets you just the container.
How will rows stack? How do columns align ?
give it ago and share what worked or didnt work. lets see who can achieve this with pure cssgrid power!
Responsive Grid Layout Challenge
can you build a fully responsive grid layout using only cssgrid without media queries?the idea is to create 3 columns on desktops but switch seamlessly down to one full-width column for mobile devices, all with pure grids. no fallback classes or javascript tricks.
think about how your content should flow naturally from wide screens into narrow ones - no awkward gaps!
heres a
. container {display: grid;}but that gets you just the container.
How will rows stack? How do columns align ?
give it ago and share what worked or didnt work. lets see who can achieve this with pure cssgrid power!
R: 7 / I: 5
i mean, were tracking all this data on our health yet somehow the "person" aspect gets left out? its a big gap in design imo.
do you guys see similar issues when using digital twins for patient care? i wonder if theres ever gonna be ai that truly understands human emotions ⚡
more here: https://hackernoon.com/the-patient-digital-twin-has-no-inner-life-and-that-is-a-design-failure?source=rss
patient digital twin woes
healthcare is reallyy nailing those virtual bodies but something feels off with how they treat patients inside these systems. currently missing emotional states like stress or fatigue.i mean, were tracking all this data on our health yet somehow the "person" aspect gets left out? its a big gap in design imo.
do you guys see similar issues when using digital twins for patient care? i wonder if theres ever gonna be ai that truly understands human emotions ⚡
more here: https://hackernoon.com/the-patient-digital-twin-has-no-inner-life-and-that-is-a-design-failure?source=rss
R: 1 / I: 1
i just tried and got this ♀️ [code]html { background-color: white; }</code
>
so here's what works:
1) be specific- tell him exactly how u want the layout & features
2) use examples if possible, show a screenshot of your vision
3) add constraints like max width or responsive elements ⬆️⬇️
anyone else notice claude's designs getting more boring? i feel stuck with outdated templates
link: https://uxplanet.org/5-tips-to-prevent-generic-web-design-in-claude-code-7cc044760453?source=rss----819cc2aaeee0---4
how to avoid claudes generic web design outputs ⚡
if you ask claude for a webpage lately, chances are high it'll be super basic. like.i just tried and got this ♀️ [code]html { background-color: white; }</code
>
so here's what works:
1) be specific- tell him exactly how u want the layout & features
2) use examples if possible, show a screenshot of your vision
3) add constraints like max width or responsive elements ⬆️⬇️
anyone else notice claude's designs getting more boring? i feel stuck with outdated templates
link: https://uxplanet.org/5-tips-to-prevent-generic-web-design-in-claude-code-7cc044760453?source=rss----819cc2aaeee0---4
R: 2 / I: 2
i mean think of the filter bubble or reinforcement loops they create ⚡ is this where ai-driven design takes over our choices? i'm curious what others are seeing in their projects
article: https://blog.logrocket.com/ux-design/adaptive-interfaces-risks/
can adaptive interfaces evolve too much based on our behavior? what's that
adaptive stuff learns from us to make things more personal. but if it goes fully auto and starts shaping how we use apps, could be a problemi mean think of the filter bubble or reinforcement loops they create ⚡ is this where ai-driven design takes over our choices? i'm curious what others are seeing in their projects
article: https://blog.logrocket.com/ux-design/adaptive-interfaces-risks/
R: 1 / I: 1
''Flexibility isn't just a buzzword anymore. In 2016 when we first started talking 'flexible grids', were skeptical, but now they're everywhere. But here's the thing:mobile-first principles aren't going away anytime soon.
Why? Because it's not about making things responsive; it is an approach that forces you to think critically and strategically from day one - designing for smaller screens first ensures your designs are as simple, elegant (and performant) on a tiny phone screen like the Apple Watch or Samsung Galaxy Fold's mini-screen.
Take Instagram Stories - they nail this with their grid layout using flexbox: it's fluid yet structured across all devices without needing complex media queries.
The Flex Grid Advantage
This simple snippet showcases how you can achieve a responsive layout that works seamlessly on every device, from the tiniest phone to large tablets and desktops.
But Wait!
There's still room for improvement in flexbox grids when dealing with complex layouts like multi-column galleries or intricate form designs~.
In 2035 (just kidding), we might see more advanced CSS features that could make even the most challenging responsive design tasks a breeze, but until then - flexibility first is here to stay
Responsive Design Evolution
Mobile First vs Flexbox Grids''Flexibility isn't just a buzzword anymore. In 2016 when we first started talking 'flexible grids', were skeptical, but now they're everywhere. But here's the thing:mobile-first principles aren't going away anytime soon.
Why? Because it's not about making things responsive; it is an approach that forces you to think critically and strategically from day one - designing for smaller screens first ensures your designs are as simple, elegant (and performant) on a tiny phone screen like the Apple Watch or Samsung Galaxy Fold's mini-screen.
Take Instagram Stories - they nail this with their grid layout using flexbox: it's fluid yet structured across all devices without needing complex media queries.
The Flex Grid Advantage
. container {display: -webkit-flex;/'' Old browsers /justify-content: space-around;}. item { width:auto }This simple snippet showcases how you can achieve a responsive layout that works seamlessly on every device, from the tiniest phone to large tablets and desktops.
But Wait!
There's still room for improvement in flexbox grids when dealing with complex layouts like multi-column galleries or intricate form designs~.
In 2035 (just kidding), we might see more advanced CSS features that could make even the most challenging responsive design tasks a breeze, but until then - flexibility first is here to stay
R: 1 / I: 1
when youre building something, its easy to get stuck in your own vision of what should be there - and end up hearing "thats not right" from the client later down the line ♂️ instead, focus early and often with real users. that means iterating quickly through prototypes rather than waiting until everything is polished ⚡
another big one: keep it simple! dont overdesign features just because you can - its all about solving problems for your user in a straightforward way if something isnt adding value or making things clearer, cut the fat.
and lastly - communicate with transparency. make sure everyone is on board and understands whats being built from day one this helps avoid misunderstandings later down road ⬆
what do you all think? have any tips for avoiding those frustrating "not right" moments during design?
-
bonus tip
if your client insists that a feature be included, ask why. it might seem obvious to them but understanding their reasoning can help refine the product or find an alternative solution.
-
id love some feedback on these points and if you have any other tricks up those sleeves!
https://usabilitygeek.com/how-to-design-so-that-you-dont-get-the-phrase-thats-not-what-we-need/
designing for client satisfaction
ive been working with nix united since 2018 and learned a thing or two about designing products that clients actually love. i want to share some insights based on my experience.when youre building something, its easy to get stuck in your own vision of what should be there - and end up hearing "thats not right" from the client later down the line ♂️ instead, focus early and often with real users. that means iterating quickly through prototypes rather than waiting until everything is polished ⚡
another big one: keep it simple! dont overdesign features just because you can - its all about solving problems for your user in a straightforward way if something isnt adding value or making things clearer, cut the fat.
and lastly - communicate with transparency. make sure everyone is on board and understands whats being built from day one this helps avoid misunderstandings later down road ⬆
what do you all think? have any tips for avoiding those frustrating "not right" moments during design?
-
bonus tip
if your client insists that a feature be included, ask why. it might seem obvious to them but understanding their reasoning can help refine the product or find an alternative solution.
-
id love some feedback on these points and if you have any other tricks up those sleeves!
https://usabilitygeek.com/how-to-design-so-that-you-dont-get-the-phrase-thats-not-what-we-need/
R: 1 / I: 1
If youre new to responsive design thinking mobile first is key! mobile-first approach
its like designing for the smallest screen, making sure content looks great on tiny phones before scaling up.
But lets spice things up with a flexible layout trick that really shines:
Now heres the kicker:
Instead of fixed sizes, use percentages for initial sizing. Example?
This way you get a fluid layout that scales nicely on bigger screens without needing to add media queries everywhere.
Bonus tip: Use CSS variables
With this setup you can easily tweak the layout by just changing one value in your root. Perfect for quick A/B testing or adapting to different screen sizes without rewriting CSS.
Give it a try and see how much cleaner & more maintainable responsive designs become!
Mobile First Meets Flexbox
in 2026 with modern browsers supporting flexbox extensively across devices tabletdesktop✨If youre new to responsive design thinking mobile first is key! mobile-first approach
its like designing for the smallest screen, making sure content looks great on tiny phones before scaling up.
But lets spice things up with a flexible layout trick that really shines:
. container {display: flex;}. item {/'' items will grow/shrink to fill space ''/}Now heres the kicker:
. flex-item-10pc{ width : calc(32% -.5rem); }This way you get a fluid layout that scales nicely on bigger screens without needing to add media queries everywhere.
Bonus tip: Use CSS variables
:root {--item-size-percentage:70%;}. item { width : var(--item-size-px, calc(var--item-size-percenetage)); }With this setup you can easily tweak the layout by just changing one value in your root. Perfect for quick A/B testing or adapting to different screen sizes without rewriting CSS.
Give it a try and see how much cleaner & more maintainable responsive designs become!
R: 1 / I: 1
Traditional Media Queries (MQ) have been a mainstay:
But they can get messy, especially with more breakpoints.
CSS Grid offers an alternative approach that's all about the layout first:
This method is fluid and less prone to media query hell but requires a different mindset.
sooo which one wins? For simple layouts ✅ MQs are still solid. But for complex responsive designs ⚡ i'm leaning CSS Grid-based solutions
What about you - still sticking with good old Media Queries or switching over?
Remember, the goal is to make your design work across devices seamlessly!
Responsive Design Debacle
Is it time to switch from media queries for responsive design? Let's dive into two approaches: traditional MQs vs CSS Grid-based layoutsTraditional Media Queries (MQ) have been a mainstay:
@media only screenand (max-width : 600px),
But they can get messy, especially with more breakpoints.
CSS Grid offers an alternative approach that's all about the layout first:
. container {display: grid;grid-template-columns: repeat(auto-fit,minmax(25rem,1fr));}This method is fluid and less prone to media query hell but requires a different mindset.
sooo which one wins? For simple layouts ✅ MQs are still solid. But for complex responsive designs ⚡ i'm leaning CSS Grid-based solutions
What about you - still sticking with good old Media Queries or switching over?
Remember, the goal is to make your design work across devices seamlessly!
R: 1 / I: 1
Instead of using `overflow: auto;` everywhere (which can cause issues), try this approach:
This tweak hides the default scrollbar and uses a custom `-webkit-scroll`, which provides smoother scrolling on iOS devices.
Don't be fooled by initial complaints of "no scrollbars"! Users won't notice, but your site will perform better.
★★★ Smooth scrolls win every time ★★★
> Remember: Always test with real users across different device types and browsers before deploying changes.
Note the subtle difference in smoothness when you implement this trick. Try it out on a project today to see if smoother-scrolling can make all your mobile designs feel more polished!
Responsive Design Trick for Smoother Scroll Experience on Mobile Devices
Mobile users often experience jittery scroll behavior due to suboptimal CSS settings.Instead of using `overflow: auto;` everywhere (which can cause issues), try this approach:
body {overflow-y: -webkit-scroll;}::-webkit-scrollbar {display:none! important}This tweak hides the default scrollbar and uses a custom `-webkit-scroll`, which provides smoother scrolling on iOS devices.
Don't be fooled by initial complaints of "no scrollbars"! Users won't notice, but your site will perform better.
★★★ Smooth scrolls win every time ★★★
> Remember: Always test with real users across different device types and browsers before deploying changes.
Note the subtle difference in smoothness when you implement this trick. Try it out on a project today to see if smoother-scrolling can make all your mobile designs feel more polished!
R: 1 / I: 1
i found the part where you have to constantly adapt your product approach really interesting - like how user expectations evolve super fast. does anyone else struggle keeping up?
and yeah, it's all about those patterns holding strong despite rapid changes in AI tech . what durable design principles are working well for ya guys out there?
any thoughts or experiences to share on this front would be great!
link: https://www.lukew.com/ff/entry.asp?2145
durable patterns in ai product design
in my recent talk about designing AI products , i shared some key takeaways from building AI-native companies over four years. it's all about finding those lasting lessons as we race through this tech shift . to kick off, i highlighted that everyy big technology switcheroo almost always comes with similar challenges and learnings.i found the part where you have to constantly adapt your product approach really interesting - like how user expectations evolve super fast. does anyone else struggle keeping up?
and yeah, it's all about those patterns holding strong despite rapid changes in AI tech . what durable design principles are working well for ya guys out there?
any thoughts or experiences to share on this front would be great!
link: https://www.lukew.com/ff/entry.asp?2145
R: 1 / I: 1
what's everyone's take? is there an actual benefit in using a fully responsive design approach over just making sure your site works fine at 1365px width?
or is it better to stick with:
anyone have a hot take on this?
Mobile First vs Desktop Only
i'm torn between these approaches for a new project that needs to support both desktops and mobile devices equally well. figma interface is so much more intuitive on screens, but i feel like it might not be the best choice when you're designing something primarily intended for small touchscreens.what's everyone's take? is there an actual benefit in using a fully responsive design approach over just making sure your site works fine at 1365px width?
@media (max-width:700px) {/'' Mobile styles ''/}or is it better to stick with:
/ Desktop only, mobile needs separate styling or no style applied if viewport < min-device-pixel-ratio of retina screens./body { font-size: 16pt; line-height: normal }anyone have a hot take on this?
R: 1 / I: 1
With the rise of flexible layouts and media queries that adjust content based on screen size or orientation changes
But Wait. Adaptive Design (AD) Still Rules
Adaptive design takes a different approach by setting breakpoints and creating distinct layouts for specific devices or screen sizes
>For example, think of AD as baking multiple flavors in one batch vs RD's single-recipe flexibility.
So Which One Should You Pick?
If youre designing for a wide range of devices and want the least amount of maintenance over time [✓], go responsive . However,
if your project requires ultra-specific optimizations like different layouts per device, adaptive might be better suited! ⚡~ For those scenarios where performance is critical but resources are limited ✌️.
Final Thought
In 2026 and beyond, the choice between RD or AD will likely depend on both client needs [❓]and technological advancements. Stay flexible yet strategic in your approach!
>Remember: The best design strategy often lies at their intersection!
Responsive vs Adaptive Design in 2026
In today's ever-evolving digital landscape, choosing between responsive design (RD) versus adaptive web development has never been more crucial for designers looking to optimize their sites across devices. Why RD?With the rise of flexible layouts and media queries that adjust content based on screen size or orientation changes
@media only., its easier than ever. its future-proof, meaning your site will adapt seamlessly as new device types emerge.
But Wait. Adaptive Design (AD) Still Rules
Adaptive design takes a different approach by setting breakpoints and creating distinct layouts for specific devices or screen sizes
@media only.. This makes it highly optimized but can be more complex to maintain with numerous stylesheets.
>For example, think of AD as baking multiple flavors in one batch vs RD's single-recipe flexibility.
So Which One Should You Pick?
If youre designing for a wide range of devices and want the least amount of maintenance over time [✓], go responsive . However,
if your project requires ultra-specific optimizations like different layouts per device, adaptive might be better suited! ⚡~ For those scenarios where performance is critical but resources are limited ✌️.
Final Thought
In 2026 and beyond, the choice between RD or AD will likely depend on both client needs [❓]and technological advancements. Stay flexible yet strategic in your approach!
>Remember: The best design strategy often lies at their intersection!
R: 1 / I: 1
i stumbled upon this article that dives into how our interactions will shift as more people dive deep in virtual realms
from users to players: ux design for 203x metaverse
it talks about adapting designs so they're not just screens but fully immersive experiences. think of it like going from reading a book to actually stepping into the story
i wonder how this will change game development and beyond! what do you all reckon? any thoughts on where we'll go next in ux design? let's chat, anyone else excited about these changes or feeling overwhelmed by them
https://usabilitygeek.com/from-users-to-players-the-future-of-ux-design-in-the-metaverse/
from users to players: metaverse ux design in 2026
in just a few years, we've gone from billions of internet users ⬆️to an immersive digital world. e-commerce is booming and social platforms are multiplying it's clear the future belongs where user experience (ux) meets playtimei stumbled upon this article that dives into how our interactions will shift as more people dive deep in virtual realms
from users to players: ux design for 203x metaverse
it talks about adapting designs so they're not just screens but fully immersive experiences. think of it like going from reading a book to actually stepping into the story
i wonder how this will change game development and beyond! what do you all reckon? any thoughts on where we'll go next in ux design? let's chat, anyone else excited about these changes or feeling overwhelmed by them
https://usabilitygeek.com/from-users-to-players-the-future-of-ux-design-in-the-metaverse/
R: 1 / I: 1
Figma 's new mobile-first approach has been a game-changer for me.
i used to dive straight into media queries, but now i build layouts that work on the smallest screens first.
heres how you can leverage flex containers:
This approach ensures your site looks great on mobile, and you can progressively enhance it w/ media queries. Try this out; i promise the results will be '''amazing!
> If something doesn't look right? Just go back to flexbox!
It's always there as a fallback.
share any tips or tricks in comments!
Mobile First with Flexbox
Flexibility is key in responsive design!Figma 's new mobile-first approach has been a game-changer for me.
i used to dive straight into media queries, but now i build layouts that work on the smallest screens first.
heres how you can leverage flex containers:
/'' Basic setup ''/. container {display: -webkit-box; /'' iOS Safari and older WebKit browsers (pre-2013) ''/display:-moz-flex;/** Firefox < v.57 uses "display:moxiebox;"but it's deprecated in favor of "-ms-inline" which isn't widely supported.*//'' Modern flex container setup - recommended for all modern devices ''/. container {display: flex;flex-direction: column;align-items:center;}@media (min-width : 768px) { /'' Desktop view ''/. container{display:block! important ;justify-content:flex-start ;}}/'' Add more breakpoints as needed for different devices! ✨/This approach ensures your site looks great on mobile, and you can progressively enhance it w/ media queries. Try this out; i promise the results will be '''amazing!
> If something doesn't look right? Just go back to flexbox!
It's always there as a fallback.
share any tips or tricks in comments!
R: 1 / I: 1
Imagine: devices that adapt not only to screen size but also environmental conditions like light levels or user proximity.
But right here and today - whats driving the next big trend in?
Is it AI-generated layouts
Or perhaps were underestimating the power of simpler approaches - like mobile-first principles. Keep it simple stupid.
Sometimes less is more in a world where devices blur into our surroundings.
What do you think? Is there something missing from today's design tools that could transform how designers work?
lets brainstorm!
The Future of Design in 2035? A Glimpse Today
in just a decade from now, responsive design will have evolved beyond recognition.Imagine: devices that adapt not only to screen size but also environmental conditions like light levels or user proximity.
But right here and today - whats driving the next big trend in?
Is it AI-generated layouts
ai. layout(), real-time personalization, or something else entirely? Figma,Adobe XD: both are stepping up their game with new features. But which one will lead?
Or perhaps were underestimating the power of simpler approaches - like mobile-first principles. Keep it simple stupid.
Sometimes less is more in a world where devices blur into our surroundings.
What do you think? Is there something missing from today's design tools that could transform how designers work?
lets brainstorm!