1

We're creating some applications that need a multi-level menu navigation. This navigation menu should be presented in these environments:

  1. Web (large browsers)
  2. Web (responsive for devices)
  3. Android app
  4. iOS app
  5. Possibly Windows Phone

We're stuck at deciding how to represent this navigation model across devices and platforms. Is there any best practice?

Update: One solution is:

Create a waterfall-like drop-down menus for web portals
Create a breadcrumb-like navigation for devices
Create a nested-accordion Android navigation drawer
For iOS, we're truly stuck.

  • 1
    This is a very broad question and the answers may tend to be Primarily opinion based. Those two reasons are enough to close this question. Why don't you show us some of your ideas so that we can help you with possible suggestions and edits, rather than asking the users to think from scratch. That way, we will have more clarity on this post and you'll benefit more from it too. – Varun Nair May 2 '16 at 8:35
  • @VarunKN, I updated the question. This question is not broad at all. We Googled and we couldn't find a universal best practice to present navigation across devices. This is so universal, that I doubt thousands of applications have not encountered it. – Saeed Neamati May 2 '16 at 8:42
  • Whatever your strategy is it needs to fit around the content and IA for your audience in the context of different device usage use cases. On the off chance that your content and IA is very organic, and that your users have the same requirements across all devices, you would have a very big job in design and testing as part of your product lifecycle. – Michael Lai May 3 '16 at 0:54
3

You can always try the MultiLevel Push Menu which works fine for all the devices you mention and has very clear and easy to follow hierarchies.

enter image description here

Additionally, you could also use Responsive Multilevel Menu which is more or less the same, only that not taking the whole vertical space

enter image description here

  • Super amazing. It's super amazing. I just can't say it enough, it's super amazing. Yet it has one drawback. Going from one leaf, to another leaf means traversing into the root (or common ancestor), and then going back to the other leaf. Is this really a drawback? – Saeed Neamati May 3 '16 at 3:26
  • I don't think so, to me it gives reference to the user, but as in anything UX, you'll need to test it and see – Devin May 3 '16 at 15:03
0

Here is the example of IOS menu design : Hope it will help you.

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.