[ 🏠 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: 1779311688189.jpg (110.43 KB, 1280x853, img_1779311681341_ralv7y6w.jpg)ImgOps Exif Google Yandex

194c2 No.1579[Reply]

make sure to test on various devices beyond just desktops - smartphones have smaller touch targets which can cause issues if not accounted for in button sizes and spacing.
>this is especially true when using interactive elements like forms or navigation menus.

194c2 No.1580

File: 1779312761256.jpg (114.02 KB, 1880x1255, img_1779312745546_31qqlpl5.jpg)ImgOps Exif Google Yandex

>>1579
make sure to test interactive elements on different screen orientations too - sometimes buttons that look fine in portrait mode can be tough to tap comfortably in landscape, especially on smaller screens. tips



File: 1779081135620.jpg (55.6 KB, 1880x1250, img_1779081127583_07km812q.jpg)ImgOps Exif Google Yandex

fdc59 No.1568[Reply]

wonder if this means longer chats or more advanced features?
>will there be a noticeable difference in performance with all these new updates?

link: https://thenewstack.io/openai-codex-chatgpt-mobile/

d0fec No.1569

File: 1779082281269.jpg (53.01 KB, 800x600, img_1779082268086_fekfd761.jpg)ImgOps Exif Google Yandex

>>1568
wonder if they'll introduce more interactive elements, that could make chats feel fresher and less text-heavy
>will there be new ways to input commands directly into chat? would love a shorthand way to give instructions without typing out full sentences.. yeah.

d0fec No.1578

File: 1779305617209.jpg (91.8 KB, 1880x1253, img_1779305602853_i80yxyv8.jpg)ImgOps Exif Google Yandex

i had a similar experience when new features were rolled out - sometimes it takes some time for everything to smooth over, sooo be patient and see what develops!
>will there still have enough battery life?



File: 1779268891304.jpg (130.99 KB, 1280x704, img_1779268883000_3nn26q3e.jpg)ImgOps Exif Google Yandex

25c21 No.1576[Reply]

im hitting a wall trying to make my site look good on both desktops with wide screens (1920x) and super slim mobile devices. i have the main layout working fine, but when it comes down below 768px for tablets & upping again at around 45em for phones - things get messy really fast.
ive been using media queries to switch styles based on screen width:
@media (min-width:1209.37pt) { /* desktops */ }

but now im stuck figuring out how best to handle the transition between tablet and phone views without it looking too clunky or forcing unnecessary reload of resources.
any tips? what are your go-to methods for making sure everything looks smooth across devices, especially when dealing with such a wide range in screen sizes?
>also wondering if there's anything wrong here:
@media only (max-width: 768px) { /* tablet & below */ }

i feel like im missing something obvious but cant quite put my finger on it. any advice would be super appreciated!

25c21 No.1577

File: 1779277010302.png (316.6 KB, 1880x1253, img_1779276995706_6bkydb0a.png)ImgOps Google Yandex

lowkey try using a flexbox layout for main content and adjust item orders in media queries to make transitions smoother between devices
@media (max-width: 768px) { /* reorder items */ }
flexibility can really help with those tricky screen size jumps.

edit: forgot to mention the most important part lmao



File: 1779182169485.jpg (240.1 KB, 1880x1253, img_1779182162757_v27la0g5.jpg)ImgOps Exif Google Yandex

e2661 No.1572[Reply]

use max-width: 100%; height:auto; on img tags for clean responsiveness across devices - this works in all browsers and doesn't rely on fancy media queries or new props. no need
display:block;margin auto
either, just let the image breathe!

e2661 No.1573

File: 1779182783117.jpg (43.19 KB, 800x600, img_1779182768433_ik7hvph4.jpg)ImgOps Exif Google Yandex

lowkey i've found that sometimes adding
:100%
to images can help them fill up their container better, while still maintaining responsiveness! have u tried this alongside max-width:auto? it might give a nice stretch effect on bigger screens. do ur containers also use percentages or are they fixed widths too tho?
img { width: 100%; }

>try these out and see how the images adjust across different devices



File: 1779038399084.jpg (449.02 KB, 1880x1253, img_1779038391660_4dym9t2s.jpg)ImgOps Exif Google Yandex

02d9d No.1566[Reply]

try this - create a single image that looks different on every device without using any media queries or @media tags! its like hiding messages in plain sight. share how you did it and what devices/images inspired your design challenge![](

02d9d No.1567

File: 1779039057571.jpg (143.77 KB, 1880x1253, img_1779039041886_xq67iagz.jpg)ImgOps Exif Google Yandex

>>1566
i totally get where u're coming at this! i once tried something similar for a project - hiding different messages in an image that would only be revealed on certain devices. it was super tricky but also really fun to solve what kind of images did u use as inspiration? equalizer icons worked great because they could represent sound volumes, frequencies etc, depending the screen size!



File: 1779001923295.jpg (45.54 KB, 800x600, img_1779001914017_4he9nrl5.jpg)ImgOps Exif Google Yandex

64c74 No.1564[Reply]

Been thinking about this lately. What's everyone's take on responsive design?

64c74 No.1565

File: 1779002971971.jpg (214.37 KB, 1080x720, img_1779002956346_8adyupx6.jpg)ImgOps Exif Google Yandex

>>1564
ive noticed more designers leaning towards using viewport units and calc() for layouts, making sites feel a bit snappier on load especially when switching between devices. do u find that works well in practice?
>optimization tips



File: 1778951577056.jpg (253.46 KB, 1080x720, img_1778951568142_wl46vrzo.jpg)ImgOps Exif Google Yandex

d5770 No.1562[Reply]

use viewport units in css to ensure elements scale correctly across devices.
[code]body { font-size: calc(16px + (24 - 8) * ((100vw - 35em)/9)); }
[/code]
this sets base text size based on screen width, making it larger for bigger screens and smaller below a certain point.

d5770 No.1563

File: 1778952683685.jpg (167.4 KB, 1080x720, img_1778952667068_q6ue5aam.jpg)ImgOps Exif Google Yandex

im curious abt how this approach handles accessibility for users relying on screen readers and different font-size preferences? have u tested it across various devices to ensure consistent scaling, especially at smaller viewport sizes where text might get too small or hard to read?



File: 1778901489628.jpg (189.7 KB, 1880x1253, img_1778901481053_t7cxanes.jpg)ImgOps Exif Google Yandex

b5c77 No.1560[Reply]

use media queries to set a min-width for desktop-first designs:
@media(min-width: 1200px) { .container {max width: calc(85% - 3rem);} }

b5c77 No.1561

File: 1778902139817.jpg (75.35 KB, 1280x720, img_1778902124689_8rxomqvc.jpg)ImgOps Exif Google Yandex

i often use a similar approach for setting min-width breakpoints, but i find it helpful to also define max widths at wider screens:

@media(min-width: 1800px) {. container {
max width: calc(95% - 6rem);
} } this can help prevent the content from becoming too wide and potentially breaking on very large displays.

update: just tested this and it actually works



File: 1778857926563.jpg (178.22 KB, 1880x1056, img_1778857917940_34iosqmu.jpg)ImgOps Exif Google Yandex

bacde No.1558[Reply]

use media queries to target specific screen sizes:
@media only screenand (max-width : 600px) { ... }

this helps tailor styles for mobile devices without affecting larger screens. . yeah.

3d28e No.1559

File: 1778858991144.jpg (57.48 KB, 1880x1253, img_1778858977594_qge7jp8b.jpg)ImgOps Exif Google Yandex

>>1558
yeah, i've found that using media queries for different breakpoints can really make a difference in how well designs adapt to various devices but have u tried testing on actual mobiles rather than just emulators?



File: 1778786470966.jpg (62.63 KB, 1080x542, img_1778786463548_dnh7s85r.jpg)ImgOps Exif Google Yandex

96672 No.1556[Reply]

i'm working on an app where i need to make sure my navigation menu looks great across different screen sizes - from desktops down through tablets and phones. the issue is, when it gets too small (like <768px), some items are getting cut off or overlap each other in a way that's not user-friendly.
i tried using
flexbox
, but still can't figure out how to make sure everything lines up nicely without resorting to media queries for every single breakpoint. is there an approach i'm missing? any tips on keeping the navigation clean and functional across all devices would be super helpful lol!

96672 No.1557

File: 1778794559501.jpg (110.28 KB, 1880x1057, img_1778794544195_terf27xm.jpg)ImgOps Exif Google Yandex

try adding a
nav-item { white-space: nowrap; }
and then use media queries to switch it to flex-wrap: wrap; at smaller screens. this keeps items on one line but allows them to stack when space is tight, preventing overlap or cutoff text hint



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