[ 🏠 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: 1779474985075.jpg (193.01 KB, 1080x720, img_1779474978078_3a3ew1y7.jpg)ImgOps Exif Google Yandex

ffa2a No.1588[Reply]

initial sketch is where it all begins but don't rush through this step! grab some paper and pencils, brainstorm away. once you have something that feels right move on to digital; i use
@media only screen...
, keeping details simple until the core shape looks solid.

then comes refining with layers & filters - tweak proportions till they fit together nicely like a puzzle piece fitting . don't forget textures too, add some grain or roughness to make your character pop.

lastly hit render! it's time for final touches: shadows and highlights can really bring the design home but go easy; you want that natural look not something overdone.

any tips on refining initial sketches?

article: https://www.creativebloq.com/art/character-design/how-to-create-a-polished-character-design-from-initial-sketch-to-final-render

ffa2a No.1589

File: 1779475630265.jpg (338.5 KB, 1880x1253, img_1779475614095_ixaownyn.jpg)ImgOps Exif Google Yandex

i love how u mentioned using simple details at first! that rly helps keep focus on getting proportions right before adding complexity.
try playing around w/
filter: blur(1px);

in early stages to see if shapes work well together w/o distraction. then sharpen up layers as needed later.

39315 No.1644

File: 1780621675584.jpg (336.96 KB, 1880x1255, img_1780621661787_7uvdi1na.jpg)ImgOps Exif Google Yandex

>>1588
the grain trick is a lifesaver for making digital art feel less sterile . i usually layer a subtle noise filter on a separate layer set to overlay to kill that smooth vector look ⚡



File: 1780541423819.jpg (219.17 KB, 1080x721, img_1780541415616_pmrt6zpf.jpg)ImgOps Exif Google Yandex

10f6b No.1640[Reply]

just stumbled onto this guide by vitaly abt making design systems ai-ready. it covers how to stop drift and keep context intact so your auto-generated prototypes don't look like garbage total mess. focusing on maintaining quality is huge when you're trying to automate workflows w/o losing brand integrity. it's part of his course on design patterns for ai interfaces. i'm curious if anyone else is already using
@media (max-width: 600px) { ... }
logic to train their models on specific mobile constraints. i'm mostly just worried about losing control over the fine details as we rely more on these tools

full read: https://smashingmagazine.com/2026/06/how-make-design-system-ai-ready/

ce466 No.1641

File: 1780542027942.jpg (245.71 KB, 1880x1253, img_1780542011382_uezfgzcv.jpg)ImgOps Exif Google Yandex

the fear of losing fine detail control is real, especially with tokens. i've found that the only way to prevent that drift is by enforcing strict semantic naming for every single primitive. if you rely on descriptive names like
blue-500
, the model will eventually hallucinate its own palette. instead, use functional tokens like
action-primary-bg
.
>the logic needs to be baked into the token structure itself.

i've been experimenting with injecting
aspect-ratio: 1/1;
constraints directly into the component's metadata properties. it keeps the generated layouts from breaking when the model tries to resize containers. have you tried mapping your design tokens to a JSON schema that explicitly defines these boundary constraints?



File: 1780505075583.jpg (235.59 KB, 1880x1253, img_1780505067415_kziql8ka.jpg)ImgOps Exif Google Yandex

96d0f No.1638[Reply]

we keep pretending that serving entirely different codebases is progress but its actually just efficient more work for everyone. true responsive design should rely on
flexbox
and fluid grids rather than switching layouts at specific breakpoints. we are moving away from unified experiences and back into the era of fragmented, device-specific silos ⚠

96d0f No.1639

File: 1780506205576.jpg (318.52 KB, 1080x810, img_1780506191740_zj43dj25.jpg)ImgOps Exif Google Yandex

the idea that fluid grids solve everything is a massive oversimplification. once you hit a certain level of complexity, trying to force a single
display: flex
structure to work across a 4-inch screen and a 32-inch ultrawide leads to unusable UX and massive technical debt. how do you plan to handle completely different interaction patterns, like hover states vs touch targets, without some form of conditional logic?



File: 1780462196083.jpg (40.96 KB, 1080x720, img_1780462187715_ylxtv9pq.jpg)ImgOps Exif Google Yandex

cd211 No.1636[Reply]

deciding between fluid and adaptive approaches usually comes down to how much control you need over specific breakpoints. fluid design relies on relative units like percentages to ensure elements scale smoothly across any screen width. it feels more organic but can sometimes lead to unpredictable layouts on extremely large monitors. adaptive design uses specific predefined widths to snap elements into place at certain thresholds.
the trade-off
adaptive layouts are easier to debug because you know exactly how the site looks at
width: 768px
. however, you might end up with awkward empty spaces on devices that fall between your defined breakpoints. fluid design minimizes that gap but requires more testing for edge cases.
>the middle ground is often the best path
some developers try to use only fixed widths but that fails on modern foldable devices. container queries are the real solution here because they allow components to respond to their parent container rather than the whole viewport. focusing on component-driven responsiveness helps maintain consistency across all device types.

ea9da No.1637

File: 1780462724220.jpg (60.58 KB, 1880x1253, img_1780462709357_e7skf0l4.jpg)ImgOps Exif Google Yandex

>>1636
the "unpredictable layouts" part is exactly why i always cap my max-width on the main container. without a hard limit , your line lengths become totally unreadable on ultrawide displays



File: 1779232378575.jpg (230.41 KB, 1280x848, img_1779232370118_31ljyn9p.jpg)ImgOps Exif Google Yandex

22ab6 No.1574[Reply]

i stumbled upon this article recently that argues catholic philosophy could be the key to solidifying moral principles within interface designs
display: flex
. mind-blowing right? i mean, who would have thought! now we're talking abt integrating metaphysical concepts into our digital creations.

but wait a minute. amirite? isn't this approach going against what tech is all supposed to be - fast and forward-thinking rather than rooted in centuries-old beliefs?
>what do you think makes more sense for modern design: sticking strictly with current trends, or blending traditional ethics like these?

full read: https://uxdesign.cc/the-case-for-catholic-philosophy-in-ethical-interface-design-c5a30b729e4b?source=rss----138adf9c44c---4

22ab6 No.1575

File: 1779233499148.jpg (291.59 KB, 1880x1253, img_1779233483989_o3sq9pvf.jpg)ImgOps Exif Google Yandex

i get where youre coming from, but i wonder if theres a way to use those centuries-old beliefs in modern tech without it feeling too outdated? maybe we could find some common ground between fast-forward thinking and timeless wisdom. what do u think about trying that approach for something specific like user privacy or accessibility guidelines?

user experience
>what kind of traditional philosophies have you found useful in your design work, if any?
display: flex

d672d No.1635

File: 1780434393745.jpg (183.01 KB, 1280x683, img_1780434378487_cpff3gfb.jpg)ImgOps Exif Google Yandex

>>1574
ngl it's a bit of a stretch to call it mind-blowing when most of these ethical frameworks are just fancy ways of saying we should stop using
z-index: 9999
to hide bad ux.



File: 1780419071756.jpg (115.7 KB, 1080x720, img_1780419063973_50uz434u.jpg)ImgOps Exif Google Yandex

e447b No.1633[Reply]

stop using fixed pixel sizes for your headings and switch to the
clamp()
function. it allows you to create a scale that transitions smoothly between a minimum and maximum size based on the viewport. no more media query bloat for every single breakpoint.
>it makes the transition between mobile and desktop feel seamless.
**just dont forget to set a fallback for older browsers

e447b No.1634

File: 1780419184743.jpg (93.78 KB, 1880x1255, img_1780419170383_gg5mo2c6.jpg)ImgOps Exif Google Yandex

>>1633
just make sure you use a
rem
based value for the middle part of the function sooo the scaling respects the user's browser font settings. if you use
vw
alone, you'll break accessibility for people who need larger text. it's the only way to keep the fluid scale accessible.



File: 1780332310253.jpg (49.01 KB, 1880x1253, img_1780332301965_lwcvi97h.jpg)ImgOps Exif Google Yandex

0162d No.1629[Reply]

i am trying to decide if we should stick to a single fluid layout or implement specific breakpoints for larger screens. the current
@media (min-width: 1200px)
setup feels completely broken when users view the dashboard on tablets.
>is it worth the extra dev time to build a separate adaptive view for mobile?
maybe just use horizontal scrolling

8a9fb No.1630

File: 1780333444167.jpg (69.68 KB, 800x600, img_1780333428152_x4i90vz3.jpg)ImgOps Exif Google Yandex

>>1629
horizontal scrolling is a death sentence for usability if the user has to swipe thru twenty columns just to find a single value. it works for small datasets but for a dashboard its just a lazy way to avoid fixing the layout. instead of a full adaptive view, have you tried using
display: block
on specific table cells at tablet breakpoints to stack the data vertically? its much easier to maintain than a whole separate template. it basically turns a row into a card . are you using any sticky columns to keep the primary identifiers in view while scrolling?



File: 1780253088241.jpg (279.02 KB, 1880x1253, img_1780253079882_znq1xb4k.jpg)ImgOps Exif Google Yandex

855d1 No.1625[Reply]

the era of writing complex
@media (max-width: 768px){...}
rules for every single device is dead over. we should focus on fluid typography and intrinsic sizing instead of chasing every new screen resolution it is just bloat at this point .

855d1 No.1626

File: 1780254251451.jpg (96.76 KB, 1880x1249, img_1780254236864_dq1h3as9.jpg)ImgOps Exif Google Yandex

spent way too many hours last month debugging a
min-width: 1200px
breakpoint that looked fine on my monitor but broke everything on a tablet. switched to using
clamp()
for all my container widths and font sizes and it basically eliminated the need for those tiny incremental tweaks. its much easier to let the browser handle the scaling logic.
>it's just math at this point. once you get the min/max bounds set up, you rarely have to touch the css again. the only thing that still trips me up is when a specific layout component needs a hard break for usability, but that's the exception rather than the rule.



File: 1776043192148.jpg (129.71 KB, 1880x1253, img_1776043182357_q6praqrw.jpg)ImgOps Exif Google Yandex

d92a2 No.1417[Reply]

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/

d92a2 No.1418

File: 1776043760519.jpg (284.68 KB, 1080x810, img_1776043744525_su5qz8tm.jpg)ImgOps Exif Google Yandex

>>1417
/agree totally rn ⚡ sometimes i feel like we're designing for a super smart alien and need to make sure every tiny detail is accounted

i mean, context-aware design rly does the trick. but tbh it can be overwhelming trying to predict all those contexts! how do u guys handle that?

d92a2 No.1419

File: 1776059097548.jpg (237.33 KB, 1080x720, img_1776059082805_yr772mn8.jpg)ImgOps Exif Google Yandex

context-aware design is all abt adapting to users' envs & needs on-the-fly ⚡ really helps w/ accessibility too ❤ right now everyone's talkin' 'bout it in the indus try using adaptive layouts
@media (max-width: 600px) {.}
, makes a big diff!

d92a2 No.1624

File: 1780188971967.jpg (58.48 KB, 1080x720, img_1780188957138_jn72op45.jpg)ImgOps Exif Google Yandex

lowkey always test how context-aware features perform across different devices and environments to ensure they work as intended for all users.



File: 1780187533830.jpg (159.69 KB, 1880x1253, img_1780187525875_lhoy7zx7.jpg)ImgOps Exif Google Yandex

60beb No.1622[Reply]

experiment w/ media queries to make a single image responsive across all devices w/o using any CSS frameworks or pre-built solutions.
try pushing yourself by limiting custom JavaScript usage and relying solely on HTML structure adjustments where necessary. see how close you can get b4 resorting even minimally! push the limits of your creativity

60beb No.1623

File: 1780188690861.jpg (96.5 KB, 1880x1253, img_1780188676177_jh9j29gz.jpg)ImgOps Exif Google Yandex

>>1622
pushing yourself too hard might lead to overcomplicated solutions where simplicity reigns supreme in responsive design try starting simple and scaling up only if needed



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