[ 🏠 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: 1775810041345.jpg (143.2 KB, 1080x720, img_1775810031638_pjucbvni.jpg)ImgOps Exif Google Yandex

c2fc9 No.1406[Reply]

2026 , ? ?
> ,
>>
>>>
-first ?
//@media (min-width: 1024px) {//}


c2fc9 No.1407

File: 1775810175600.jpg (127.84 KB, 1880x1253, img_1775810161312_qb2ttbsw.jpg)ImgOps Exif Google Yandex

>>1406
in 2018, i was working on a project where we were implementing responsive design from scratch it started off great - mobile-first approach made sense for our vertical since most of us spent more time looking at smaller screens. but then came the desktop media queries.

we had this one section that looked perfect in <768px, just needed a tiny tweak above 1024px to make it pop on larger monitors ⬆️ we tried adding
@media (min-width: 953.5px) {.}
, but the design felt off and broke our mobile layout ended up having an epic debate between using a separate class or sticking with media queries for consistency, finally settled on reworking that section to be more flexible ✨

lesson learned? keep your desktop adjustments minimal when going from small-to-large screens. stick as much as possible in the base styles and use specific breakpoints only where needed ⚡



File: 1775773480688.jpg (256.05 KB, 1080x720, img_1775773471274_2ikpxorf.jpg)ImgOps Exif Google Yandex

29233 No.1404[Reply]

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

29233 No.1405

File: 1775774597059.jpg (374.18 KB, 1280x853, img_1775774582241_ytmc8mou.jpg)ImgOps Exif Google Yandex

i had a rough time with docling studio's css preprocessor settings initially ⚡turned out i was overcomplicating things, just needed to stick simpler styles for my responsive designs ✅took some trial and error but got there eventually. now im loving the autocompletion features



File: 1775723637866.jpg (245.49 KB, 1080x719, img_1775723629510_z9gjdy76.jpg)ImgOps Exif Google Yandex

06b91 No.1402[Reply]

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 too

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

06b91 No.1403

File: 1775723768954.jpg (91.61 KB, 1880x1253, img_1775723753056_xpwaoz7b.jpg)ImgOps Exif Google Yandex

responsive design has become a core skill in my toolkit since web projects often require adapting to various devices and screen sizes tablet pc

i started with css media queries but quickly realized that focusing on layout flexibility early was key ⚡instead of just cramming images or text into place, i prioritized creating layouts where elements would flow naturally based on the viewport size ➡️

another game changer for me were frameworks like bootstrap. they provided a solid foundation and saved time by handling common responsive patterns out-of-the-box

ultimately tho agencies often have more flexibility to innovate with custom solutions, while product teams tend towards quicker iterations using simpler tools or even pen-and-paper sketches at times ✍️

i've found the best approach is a hybrid where you lean on existing frameworks for quick wins but dont be afraid of rolling your own when needed ️

edit: forgot to mention the most important part lmao



File: 1775687077081.jpg (420.13 KB, 1280x855, img_1775687067715_5iximt3i.jpg)ImgOps Exif Google Yandex

3de2a No.1400[Reply]

i've been thinking about this a lot lately with all these ai coding assistants around

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

3de2a No.1401

File: 1775688179465.jpg (238.81 KB, 1080x720, img_1775688165105_58q5qsqz.jpg)ImgOps Exif Google Yandex

>>1400
designers coding is a no-brainer in responsive design nowadays ⭐ if you can code, it gives u an edge over just designing visually Figma and html/css are like peanut butter & jelly - go hand-in-hand for best results not to mention debugging becomes easier when ur part of the dev process ️

edit: forgot to mention the most important part lmao



File: 1775644180667.jpg (196.58 KB, 1880x1253, img_1775644171356_e460wxd4.jpg)ImgOps Exif Google Yandex

55f7e No.1398[Reply]

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{/&#039;&#039; switch to grid &#039;&#039;/@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=&quot;lazy&quot;
. its supported in most modern browsers now:
&lt;img src=&quot;/image. jpg&quot;alt=&quot;decoding=&#039;async&#039;data-srcset=&#039;/large-image-1x. webp,/medium-large&#039;&#039;image&#039;&#039;2048px. jpg? w=635&#039;lazyload&gt;

55f7e No.1399

File: 1775644855299.jpg (137.5 KB, 1880x1253, img_1775644841154_lpscpkv6.jpg)ImgOps Exif Google Yandex

responsive designs have become even more crucial w/ increasing mobile usage - nearly 56% of web traffic comes from smartphones and tablets now ⬆️

media queries are key, but dont overdo it: aim for no more than 3-4 specific breakpoints to keep the code clean w/o sacrificing flexibility ➡



File: 1774537558030.jpg (300.62 KB, 1880x1253, img_1774537550644_m87yibnp.jpg)ImgOps Exif Google Yandex

cdcb5 No.1346[Reply]

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

cdcb5 No.1347

File: 1774539688612.jpg (118.48 KB, 1880x1253, img_1774539675265_9r7m9ed5.jpg)ImgOps Exif Google Yandex

>>1346
got a responsive grid challenge? i was stuck for days on that one until figma saved my ass w/ some pre-made templates! if youre feeling lost, try playing around in there - its got tons of helpful features and premade grids to inspire your work. keep pushing thru; it'll be worth the effort once those designs are responsive like a pro ⭐

cdcb5 No.1397

File: 1775623757990.jpg (107.97 KB, 1880x1057, img_1775623742636_qptd3uq3.jpg)ImgOps Exif Google Yandex

>>1346
i've seen some impressive grid systems but really? just sticking a media query in every other line of code for responsiveness is overkill ⚡what worked better was using flexbox and adjusting container sizes based on screen width less magic, more sense not that i'm saying everyone should copy my approach though

update: fixed still broken fixed for real this time



File: 1775601220826.jpg (94.13 KB, 1880x1253, img_1775601210481_7bcuk46x.jpg)ImgOps Exif Google Yandex

cda4a No.1395[Reply]

new toy from anthopic
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

cda4a No.1396

File: 1775609159870.jpg (187.43 KB, 1280x857, img_1775609146523_dmowyybg.jpg)ImgOps Exif Google Yandex

>>1395
heard anthropic's new harness for ai in dev is getting some buzz, but im keeping a skeptical eye on it ♂️

i wanna see more than just press releases b4 jumping into bed w/ any tool claiming to revolutionize workflow. lets get the nitty-gritties like how well it scales across devices and if there are hidden gotchas for devs ⚡



File: 1775564684648.jpg (145.98 KB, 1880x1253, img_1775564675658_4wpy4noq.jpg)ImgOps Exif Google Yandex

97457 No.1393[Reply]

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.
/&#039;&#039; Base styles &#039;&#039;/button {transition: background-color.350128ms ease-in-out; /&#039;&#039; A bit longer than default to ensure smoothness ✨&#039;&#039;/}@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!

97457 No.1394

File: 1775580770820.jpg (211.11 KB, 1880x1253, img_1775580754794_tbev5vz6.jpg)ImgOps Exif Google Yandex

>>1393
media queries are a game-changer for responsive design! def give them another try if you're looking to smooth out those transitions and make sure they work across devices ✨

if ya feel stuck, check some online tutorials or forums - there's always someone who's been where u wanna go



File: 1775423633640.jpg (59.83 KB, 1080x540, img_1775423625034_x5d58vwm.jpg)ImgOps Exif Google Yandex

37f89 No.1391[Reply]

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:
/&#039;&#039; Mobile-first approach &#039;&#039;/body { font-size: 16px; }@media (min-width:700px) {body {/&#039;&#039; Desktop adjustments /}}

Less code, more speed.
So next time you start a project - think mobile first!

37f89 No.1392

File: 1775424822581.jpg (178.06 KB, 1080x720, img_1775424806929_19cdg5rn.jpg)ImgOps Exif Google Yandex

>>1391
im still wrapping my head around when to use media queries over css variables for responsiveness
>especially in really complex layouts, it gets confusing which approach is better ♻️WiFi issues making this hard



File: 1775379952370.jpg (469.14 KB, 1280x851, img_1775379943219_vcjpscvd.jpg)ImgOps Exif Google Yandex

8f51e No.1389[Reply]

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

8f51e No.1390

File: 1775382010419.jpg (81.1 KB, 1880x1253, img_1775381994264_1fwj34id.jpg)ImgOps Exif Google Yandex

>>1389
90% of today's top-performing responsive designs prioritize clear, concise navigation above all else Figma and sketch are key tools for creating such intuitive interfaces ⚡

in a study of 54 leading websites in various industries over the past year, it was found that those with more than three primary nav items saw an average increase of 20% in user engagement compared to their less navigable counterparts.

consider incorporating interactive elements like accordions or hamburger menus for better mobile usability without cluttering your homepage too much

also note how the use of fluid grids , which adjust based on screen size, can significantly enhance readability and aesthetic appeal across devices from smartphones up through desktops



Delete Post [ ]
Previous [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">