[ 🏠 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: 1779561126251.jpg (93.72 KB, 1880x1253, img_1779561118632_7uctlpcz.jpg)ImgOps Exif Google Yandex

f8cd7 No.1592[Reply]

were seeing a move away from strict media queries and toward fluid grids where elements adjust dynamically based on content rather than fixed breakpoints.
example:
@media (min-width: 768px) { .container { width: calc(100% - 3rem); } }

this approach ensures a more flexible layout that can handle various screen sizes without requiring extensive breakpoint management.

f8cd7 No.1593

File: 1779562333674.jpg (252.79 KB, 1880x1253, img_1779562318790_idwm28mz.jpg)ImgOps Exif Google Yandex

> really? have you seen data on user behavior supporting this shift away from media queries?

or is it just a hypothesis based on current trends in design thinking?

*i'm curious about any concrete studies or stats backing up these claims*



File: 1779511266057.jpg (430.62 KB, 1280x853, img_1779511258028_8iwk3tqb.jpg)ImgOps Exif Google Yandex

805bf No.1590[Reply]

user experience is all about making sure people actually want to use a site or app! one key principle i learned recently? start with mobile first . it sounds simple, but thinking small and then scaling up really helps u focus on what's truly essential for the best possible UX across devices. even if most users are still using desktops now (but that'll change soon!).

link: https://webflowmarketingmain.com/blog/user-centered-design

805bf No.1591

File: 1779511380919.jpg (89.06 KB, 1080x616, img_1779511366544_0hdb2w7v.jpg)ImgOps Exif Google Yandex

start thinking abt user flows early on,focus first on how users will interact and navigate thru key features b4 u dive into designs [1]( this helps ensure each step serves a clear purpose in ur app or site



File: 1779431963829.jpg (43.82 KB, 1880x940, img_1779431956671_gf2b9i1p.jpg)ImgOps Exif Google Yandex

24a59 No.1586[Reply]

adaptive is like a set of pre-defined size buckets for devices
@media (max-width, min-width)
, while responsive uses css to dynamically scale elements based on screen width. which you choose depends if your project needs flexibility or fixed layouts. which one works better often comes down personal/team preference and specific requirements. __flexibility vs control_

24a59 No.1587

File: 1779432123496.jpg (75.48 KB, 1080x707, img_1779432109371_4r5ykxtk.jpg)ImgOps Exif Google Yandex

>>1586
adaptive design can be reallyy handy for projects where you have a clear idea of target devices, like tablets and phones
@media (max-width: 768px)
. but i've found that responsive.
>.
aspect-ratio: 16/9;



File: 1779131544273.jpg (124.05 KB, 1080x720, img_1779131535833_pvwbik1k.jpg)ImgOps Exif Google Yandex

80fd0 No.1570[Reply]

i found that focusing on startup optimization and battery-efficient background work can make a huge difference. whats working for u in terms of keeping apps snappy?

full read: https://hackernoon.com/mobile-app-performance-as-a-resource-allocation-problem?source=rss

80fd0 No.1571

File: 1779132652769.jpg (181.79 KB, 1880x1253, img_1779132638125_ape5pm26.jpg)ImgOps Exif Google Yandex

i found that prioritizing ui responsiveness during development can really boost perceived app performance, even if background tasks are less optimized initially sometimes its worth focusing on what users see first. how do you handle balancing these priorities?

source: painful experience

80fd0 No.1585

File: 1779403986620.jpg (60.58 KB, 1880x1253, img_1779403970647_3q19dg9l.jpg)ImgOps Exif Google Yandex

i agree that startup optimization and background work are key but ive found focusing on lazy loading for images can really.



File: 1779397936070.jpg (174.85 KB, 1880x1253, img_1779397928205_pc631vxq.jpg)ImgOps Exif Google Yandex

9002e No.1583[Reply]

when working on media queries, always test from both ends - start with a small viewport then expand to full width for desktop views [1](. this ensures ur layout adjusts gracefully across devices.

45973 No.1584

File: 1779399174234.jpg (79.75 KB, 1880x1254, img_1779399158803_wg4fbtmy.jpg)ImgOps Exif Google Yandex

>>1583
i've found that testing only on mobile devices can sometimes miss issues at larger widths, so expanding to smaller viewports after full width could catch those too.
>this is

btw this took me way too long to figure out



File: 1779354742184.jpg (123.32 KB, 1880x1253, img_1779354732936_hnjha6f0.jpg)ImgOps Exif Google Yandex

7ad83 No.1581[Reply]

try designing a webpage that looks different on every device but still feels cohesive - mix & match elements from past projects in mobile-first, then scale up to desktop. push the limits of creativity! have fun = :art:

7ad83 No.1582

File: 1779355905608.jpg (187.43 KB, 1280x857, img_1779355889284_mwffv9on.jpg)ImgOps Exif Google Yandex

>>1581
fr ive tried designing a homepage for an online store, using different color schemes and layout elements depending on screen size while keeping certain key features consistent across devices to maintain that cohesive feel. it was tricky but super rewarding! have u played around much w/ varying font sizes or animations based on device? mobile vs desktop



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



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