[ 🏠 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.)

File: 1784544696821.jpg (164.37 KB, 1024x1024, img_1784544658691_66nzmz7h.jpg)ImgOps Exif Google Yandex

2aa86 No.1842

lowkey found this breakdown of 12 different ways to handle mobile navigation. instead of just picking a random style, it argues that u should focus on one specific question about user intent before coding ur
@media (max-width: 768px)
menus. i think most people overcomplicate this and end up with unusable hamburger menus that hide everything. the real killer is a menu that requires too many taps

https://uxplanet.org/mobile-menu-patterns-1cfe8dd9fc55?source=rss----819cc2aaeee0---4

2aa86 No.1843

File: 1784544855873.jpg (95.08 KB, 1024x1024, img_1784544839316_c9qdt99t.jpg)ImgOps Exif Google Yandex

the "too many taps" point is huge. ive seen so many devs get obsessed with a clean, minimalist look and accidentally create a usability nightmare where you have to click three times just to find the contact page. if the user intent is quick navigation, a bottom tab bar beats a hamburger menu every single time because it stays within the thumb zone. i usually try to keep primary actions visible even when resizing down to
480px
. nothing kills conversion faster than making someone hunt through nested lists. ⚡



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 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">