CSS3 animated dropdown menu
red-team-design.com
CSS3 animated dropdown menu
1–10 of 10 posts
Re: CSS3 animated dropdown menu
#2When you develop the next cool widget, consider that a large part of the web is now mobile. So that means no hovering, no mouse.
Deal with that.
Re: CSS3 animated dropdown menu
#3This is nice. Unfortunately it does not work on devices with touch interfaces. When you develop the next cool widget, consider that a large part of the web is now mobile. So that means no hovering, no mouse. Deal with that.
Re: CSS3 animated dropdown menu
#4However, I've always disliked the drop down menu. I avoid it at all costs (unless a client really demands it). It seems chaotic to me, and it doesn't give any affordance to being a mechanism that shows more options on hovering.
That said, there are some nice implementations that I've enjoyed using because they can reduce clicks if it is responsive enough. This one could easily fall in to this camp.
Re: CSS3 animated dropdown menu
#5This is nice. Unfortunately it does not work on devices with touch interfaces. When you develop the next cool widget, consider that a large part of the web is now mobile. So that means no hovering, no mouse. Deal with that.
What do people think is the better approach? Should we provide a responsive, interactive menu that works really well for computer users while providing a simpler, touch friendly menu for mobile users? Or should we provide a single interface that works for both and provides a consistent interface across all devices, but it dumbs down the gloss or functionality on the pc side?
Re: CSS3 animated dropdown menu
#6Re: CSS3 animated dropdown menu
#7Re: CSS3 animated dropdown menu
#8This is nice. Unfortunately it does not work on devices with touch interfaces. When you develop the next cool widget, consider that a large part of the web is now mobile. So that means no hovering, no mouse. Deal with that.
1. Show a grid of icons that let you navigate to various parts of the app on a flat hierarchy. Facebook used to do this and now many other apps copied their approach. This nav menu is typically the root view in a navigation hierarchy.
2. Show a tableview where each row shows a different part of the app, you tap to go there. This is also the root view in a nav hierarchy but you can group table rows under headings to essentially get 2-levels showing at once.
Should a dropdown menu creator also make the decision of how to reorganize the dropdowns to work on mobile? No. The decision of how one will display a similar navigational structure on their mobile app is very personal, very rooted to how they currently structure the interface on their mobile app or website.
Re: CSS3 animated dropdown menu
#9This is nice. Unfortunately it does not work on devices with touch interfaces. When you develop the next cool widget, consider that a large part of the web is now mobile. So that means no hovering, no mouse. Deal with that.
What do people think is the better approach? Should we provide a responsive, interactive menu that works really well for computer users while providing a simpler, touch friendly menu for mobile users? Or should we provide a single interface that works for both and provides a consistent interface across all devices, but it dumbs down the gloss or functionality on the pc side?
Re: CSS3 animated dropdown menu
#10Mac OS notably lets you move diagonally as long as you are moving more right than down I think. There may be a delay involved too.
I couldn't find an exact reference for this, but this is on the topic: http://www.asktog.com/readerMail/2000-07ReaderMail.html#Anch...