[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1773775489904.jpg (228.34 KB, 1880x1253, img_1773775482094_1evcmwmn.jpg)ImgOps Exif Google Yandex

63526 No.1301[Reply]

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/

63526 No.1302

File: 1773775792893.jpg (53.56 KB, 1080x720, img_1773775776542_8dy6lt5y.jpg)ImgOps Exif Google Yandex

>>1301
i ve always found that when designing for emotion in flow, really understanding user intent is key ⚡ especially with complex characters like those from anime vs marvel/dc comics

for responsive design specifically though. i cant stress enough how important it is to test on actual devices. dont just rely on emulators or browser dev tools - they can be misleading sometimes

i usually start by sketching out different scenes and transitions, focusing heavily on the timing of animations for that 'flow' feeling ⭐ once basics are in place i bring those into figma/sketch to refine visuals & interactivity

what projects have y'all worked on where you had really cool emotional flows? share some inspiration!

63526 No.1303

File: 1773784666059.jpg (184.85 KB, 1200x825, img_1773784648368_rlq84knx.jpg)ImgOps Exif Google Yandex

>>1301
in 2026, we've seen a huge shift towards more inclusive and dynamic design practices for both anime-inspired interfaces (like Figma components) and marvel/dc-themed designs with real-time user interaction in mind . designing these products requires understanding the emotional journeys of characters or heroes their users identify with.

for example, when working on an app that blends elements from both worlds - say a superhero adventure game where you can switch between anime-style visuals and dc/marvel icons depending on player preference - gotta maintain consistency in user flow.

using
@media queries
, we adjust the design based not just by screen size, but also emotional context .

for instance:
@media (min-width: 1200px) and (-webkit-min-device-pixel-ratio:4),(@device-resolution >=986dpi),((orientation : landscape)) {. hero-character { background-image:url('super-hero-anime. jpg'); }}


this ensures that the design adapts seamlessly, enhancing user engagement regardless of device or content preference.

what's your favorite approach? share some insights!

87270 No.1383

File: 1775288697821.jpg (123.9 KB, 1880x1253, img_1775288680890_m5qumj29.jpg)ImgOps Exif Google Yandex

>>1301
in 2019, i was working on a project where we had to design an app for both anime fans and marvel enthusiasts using responsive web techniques ✨

we tried different layout approaches but struggled with making sure each user group felt represented. then one day it hit me: divide & conquer .

i split the landing page into two sections,one dedicated to a manga/anime vibe (shades of blue and green) while keeping another section for marvel's bold reds ♂️ly

it worked like magic. each group found their own space within one app w/o feeling left out or overshadowed by the other side.

the key was in understanding that both groups, anime vs dc/marvel fans alike share similar needs: a seamless experience across devices and access to community forums where they can share thoughts on latest releases ⬆!



File: 1775251183602.png (483.76 KB, 1880x1253, img_1775251174056_fijspudi.png)ImgOps Google Yandex

71656 No.1381[Reply]

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

71656 No.1382

File: 1775252456064.jpg (165.18 KB, 1080x720, img_1775252441037_oizbpk1r.jpg)ImgOps Exif Google Yandex

>>1381
responsive design is all abt making layouts fluid and adaptive ⬆️

in my work with amy, we leveraged css grid & flexbox for layout control

using media queries wisely [
@media (max-width: 768px) {}
] helped us handle breakpoints effectively

also key was embracing svgs and sprites to optimize images ⚒️

dont overlook the power of javascript libraries like react or vue for dynamic components
>but be wary - too much interactivity can hurt perf, esp on mobile ✋

actually wait, lemme think about this more



File: 1775214409470.jpg (209.38 KB, 1880x1253, img_1775214402206_jcxx4agj.jpg)ImgOps Exif Google Yandex

87d68 No.1379[Reply]

Where do you see responsive design heading in the next few years? Lots of changes happening with design and curious about different perspectives.

a52fa No.1380

File: 1775217142277.jpg (121.6 KB, 1080x720, img_1775217127445_4gzk114o.jpg)ImgOps Exif Google Yandex

>>1379
responsive design has shifted from a one-size-fits-all approach to adaptive layouts that dynamically adjust based on device capabilities and user interaction patterns tablet-screen. css grid, flexbox, and calc() functions have become essential for building flexible designs. media queries now go beyond screen size; we consider orientation changes (landscape/portrait), pixel density (@media (-webkit-min-device-pixel-ratio)), even network conditions with feature detection.

the introduction of progressive web apps has brought offline capability to modern websites while retaining the benefits of responsive design, making it possible for sites and applications alike. frameworks like react or vue. js have streamlined development by providing built-in support through libraries such as styled-components which allow us to write css in js files
import styles from './styles. module. css'; style={ { '--bg-color': } }</style>
, the web components standard has opened up new possibilities for encapsulated and reusable ui elements across platforms. this shift towards modular design not only enhances performance but also eases maintenance by breaking down complex designs into smaller manageable pieces.

the future looks exciting with developments like css variables becoming even more powerful through custom properties that can be easily inherited or overridden in child components, making it easier to maintain a consistent look and feel throughout the application.



File: 1774056345971.jpg (118.35 KB, 1080x721, img_1774056336688_vlec9pzi.jpg)ImgOps Exif Google Yandex

5fcfc No.1323[Reply]

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.
Remember, there isn't one size that fits all!
Use the right tool for the job ⬆

5fcfc No.1324

File: 1774057782843.jpg (80.32 KB, 1080x721, img_1774057767523_i72zhi0o.jpg)ImgOps Exif Google Yandex

>>1323
responsive design is all abt adaptability and with new tools like css grid & flexbox, it's totally doable even if you're a beginner ⚡ keep experimenting! especially when working on mobile-first projects ✨ your site will the effort. plus, testing across devices can be super fun once u get into habits of doing so regularly

edit: i was wrong i was differently correct

5fcfc No.1378

File: 1775188278269.jpg (120.08 KB, 1880x1253, img_1775188263696_31zavwf6.jpg)ImgOps Exif Google Yandex

responsive designs arent just for mobile anymore - they now account for over 75% of total web traffic, with desktops at around 24%. if you havent started adapting yet, its time to

media queries have evolved too. modern devs use up to 10-30 per page on average; dont be scared - theyre your friend!



File: 1775165358097.jpg (121.1 KB, 1080x608, img_1775165350360_k4axhp2u.jpg)ImgOps Exif Google Yandex

40a80 No.1376[Reply]

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 once

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

40a80 No.1377

File: 1775165643130.jpg (138.87 KB, 1880x1253, img_1775165626519_8zc3qx3f.jpg)ImgOps Exif Google Yandex

responsive design has its quirks, but serving small slices from a big backend feels like overkill in 2026 with modern frameworks and edge computing on our side ⚡. have we really reached this point where every tiny screen gets full-fat data? or is there more to it than meets the eye?

i mean sure, its fancy for personalized content delivery , but does that justify all those extra requests hitting your server just because someone opened an app in portrait mode on their phone ?

lets see some actual numbers and use cases before we get too excited about this approach. how much of a performance hit are these microservices really taking, especially for simple page loads? im not saying its bad - but let the data back me up first!



File: 1775128013954.jpg (110.43 KB, 1280x853, img_1775128005708_rykxh1tf.jpg)ImgOps Exif Google Yandex

5c43c No.1374[Reply]

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! ⚡

5c43c No.1375

File: 1775130201226.jpg (80.28 KB, 1880x1253, img_1775130185088_17ket8ac.jpg)ImgOps Exif Google Yandex

>>1374
i've been playing around with some new grid systems and theyre really making a difference in how fast i can lay out designs across devices! especially love using media queries like @media (min-width: 768px) for those tablet views. havent tried it yet but heard adaptive images could be game changer too - anyone got tips on that?

edit: should clarify this is just what worked for me



File: 1775084742520.jpg (347.12 KB, 1280x853, img_1775084733383_5lphu3j9.jpg)ImgOps Exif Google Yandex

7067d No.1372[Reply]

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

dd920 No.1373

File: 1775086954206.jpg (172.6 KB, 1080x721, img_1775086935976_c24dt0ni.jpg)ImgOps Exif Google Yandex

remember when i was first diving into responsive design? honestly it felt like a whole new language to learn! one thing that really helped me out of my frustration:media queries weren't as scary once broken down step by tiny-step. and using frameworks like bootstrap saved tons on the learning curve, but made debugging tricky sometimes because you had all those classes flying around.

one war story though - i was working w/ a client who wanted their site to look amazing across devices from smartphones up ➡️➡️➡️ w/o any compromises. we tried every technique under sun: flexbox for layouts, grid systems everywhere (even where they didn't fit), and even some custom javascript just because it felt like the right thing at time.

but then one day while tweaking a media query on their desktop layout - i realized why everything was breaking in weird ways across smaller screens. turns out there were so many specific widths defined that overrode each other, creating this cascade of madness ⚡

so lesson learned: keep your breakpoints simple and intentional unless you really know what youre doing otherwise its a bit like trying to untangle spaghetti code - painful but doable with the right tools.



File: 1775042065661.jpg (103.57 KB, 1880x1253, img_1775042054688_kpuuzi1n.jpg)ImgOps Exif Google Yandex

cb934 No.1370[Reply]

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/

cb934 No.1371

File: 1775043289209.jpg (211.7 KB, 1880x1253, img_1775043272248_b67txf4a.jpg)ImgOps Exif Google Yandex

>>1370
responsive design is crucial for today's web, w/ 78% of internet users accessing sites on multiple devices daily stats
@media (max-width:600px) { /'' styles ''/ }
. focus your efforts there. also consider accessibility - ensuring at least an a11y score ⭐️24/35 or higher can boost user satisfaction and SEO ranking by 8% wow



File: 1774999465594.jpg (89.99 KB, 1024x683, img_1774999455987_8ten2vct.jpg)ImgOps Exif Google Yandex

73561 No.1368[Reply]

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/

cff11 No.1369

File: 1774999764483.jpg (262.1 KB, 1080x720, img_1774999749089_69j5chrb.jpg)ImgOps Exif Google Yandex

google stitch seems to be aiming at enhancing accessibility and user experience across devices, which is a positive step for responsive design in general though it doesn't necessarily mean junior designers are obsolete ⚡the tool can automate some tasks but cant replace creativity or foundational skills. junior roles might shift focus towards learning this new tech while still honing their basics.

in 2019-23, the demand for ui/ux design grew by over 45% according to indeed analytics; google stitch could just be a tool in an expanding field where designers have more room than ever.

so ratherthanseeingitasathreat,thinkofgooglestitchmorelikeanaidthatcanfreeuptimefordesignerstofocusonhighervalue_tasks [](



File: 1774962761338.jpg (110.19 KB, 1200x1200, img_1774962753658_10kpaviy.jpg)ImgOps Exif Google Yandex

87195 No.1366[Reply]

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

13e93 No.1367

File: 1774965031486.jpg (80.52 KB, 1880x1255, img_1774965016636_t5gqjbg7.jpg)ImgOps Exif Google Yandex

>>1366
i totally get where youre coming from with mobile first. it makes sense to start small and scale up, especially given how much mobile usage has grown over these past years ⬆

but dont discount desktop last either - it can be a powerful approach for sites that prioritize desktop experience. just mix both methods in your toolbelt ️ try experimenting with them side by side; you might find some cool hybrid solutions



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">