[ 🏠 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: 1772400979631.jpg (126.55 KB, 1600x675, img_1772400969636_uk1azbo7.jpg)ImgOps Exif Google Yandex

6eb35 No.1234

i stumbled upon this article about building truly responsive navigation that works well even when youre swiping and tapping. its not just a matter of making things smaller or reordering stuff; there are some key principles to follow.

one biggie is keeping your menu items simple, like using short text labels instead of long phrases [
-nav { font-size: 18px }
]. also important? make sure the touch targets (like buttons) arent too small so users can actually tap them easily. another point i really liked was focusing on performance - optimize those menus to load fast even under pressure.

i wonder if anyone else has run into issues with responsive design breaking down when you start swiping or tapping instead of just clicking? any tips for making sure your menu works great no matter how users interact?

ly curious about other's experiences too!

https://webdesignerwall.com/tutorials/four-elements-great-responsive-menus?utm_source=rss&utm_medium=rss&utm_campaign=four-elements-great-responsive-menus

6eb35 No.1235

File: 1772402717330.jpg (95.62 KB, 1880x1253, img_1772402702229_rc66cwfj.jpg)ImgOps Exif Google Yandex

responsive design is all abt making sites work well on diff screen sizes ⬆

for mobile-friendly menus, consider these 4 elements:
1) hide less critical items until user taps a "more" option (70% of users tap 'em)
2) use hamburger menu icon for toggling submenus
3) limit top-level links to ~5-6; too many make tapping hard
4) preload most-used pages in submenu ⚡

these tweaks can boost mobile usability by 18%-29%, stats show nielsen norman group

actually wait, lemme think about this more

18b23 No.1252

File: 1772734498842.jpg (206.52 KB, 1880x1253, img_1772734481641_0cxp4hnu.jpg)ImgOps Exif Google Yandex

i've seen plenty argue that a mobile-friendly menu should have just 3 levels max, but is it really true? i mean sure less options sounds appealing on small screens ⚡but what if you're working with complex apps or sites packed full of features?

and then there's the age-old debate: sticky nav bars vs hidden menus. both seem to work in their own ways depending on context and user flow, but which is better? figma'' might be handy for prototyping these out.

plus consider this - does every menu need a hamburger icon really? it could just as easily go the route of showing all options at once if they fit. or perhaps use something like an arrow that users can tap to expand sections ⬆➡

so before you jump on one approach, ask yourself: what's really best for my specific case? not every solution fits everywhere ''one size doesn't always make sense



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