[ 🏠 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: 1776000313631.jpg (79.38 KB, 1880x1253, img_1776000305816_hhcode98.jpg)ImgOps Exif Google Yandex

28020 No.1415[Reply]

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


File: 1775939367195.jpg (604.6 KB, 1280x833, img_1775939358109_z2wp0j2s.jpg)ImgOps Exif Google Yandex

afc73 No.1412[Reply]

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

afc73 No.1413

File: 1775940101609.jpg (59.53 KB, 800x600, img_1775940086802_9m5qfj2l.jpg)ImgOps Exif Google Yandex

i'm still trying to wrap my head around how schema evolution works in delta lake for real-world pipelines, like what happens during a merge operation? does it handle column addition and deletion seamlessly without breaking existing queries? ✍️



File: 1775896442416.jpg (237.63 KB, 1280x853, img_1775896429224_yr7d6kx8.jpg)ImgOps Exif Google Yandex

ac29c No.1410[Reply]

Both frameworks have their strengths, but when it comes to a seamless user experience across all devices in 2026. thats where Tailwind CSS
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
<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.

ac29c No.1411

File: 1775896565525.jpg (61.24 KB, 1080x827, img_1775896550542_o14r6f27.jpg)ImgOps Exif Google Yandex

yep, mobile-first is key!:) if you're just getting started with responsive design and feeling a bit lost i was there too, don't worry it gets easier as u go along

if ya stumble on tricky media queries or layout issues figma has some great tutorials that break things down step by step. give 'em a try! they really helped me out when i first started. keep pushing, and you'll see the magic happen in no time ❤



File: 1775859870593.jpg (215.87 KB, 1080x810, img_1775859861082_sjhfcefd.jpg)ImgOps Exif Google Yandex

a82ea No.1408[Reply]

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

45067 No.1409

File: 1775860938066.jpg (205.46 KB, 1080x721, img_1775860922537_r52tv8dj.jpg)ImgOps Exif Google Yandex

>>1408
responsive typography is all 'bout making sure type scales well across devices tablet

i found using rem units for font sizes really helps ⚡for headings, use something like h1 {font-size: 2rem} and let it scale down on smaller screens. this keeps your text readable no matter the device you're viewing from ipad iphone



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



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