New answers tagged

0

Here are three examples based on what you want. I believe these are more user-friendly. However, whenever you are developing new ways, test it and if your target users like it. Then you have solved the problem. I have read that Hamburger menu increases conversion rate as for secondary menu, you can either combine them into the hamburger menu as below : ...


0

You could try something like this. in terms of selection it's similar to mac osx navigation style. in the 1st column is the actual form and in the 2nd column is the option or input for the form selected. this means your input area are all shared by the 2nd column space. and selecting each field you want to enter changes the 2nd column


3

Perhaps a searchable dropdown could fit your needs: On opening, the dropdown will show you all possible choices, which you can filter by typing in the desired term.


4

The common (almost too common) way to provide choices of many options is often via the dropdown, but a flat list of options can be made easier to digest by grouping the items and, at the very least, ordering the items alphabetically. Say 10 ordered groups each with 10 ordered items in might be manageable. A further refinement is to make the dropdown ...


2

Short answer Don't user hover. Long answer While I don't think it will make too much difference in 2016 as web users are much more familiar with these menus and quickly work it out on a site by site basis, there does appear to be a movement away from using hover menus full stop. How much of this is due to the growth of mobile devices is open to debate. ...


1

A dashboard is a very different UI than an application, so there is an argument that the navigation can be different. For example, the features are different, the purpose and goals are different, so what works for one might not work for the other. Consistency comes with advantages, so as a general rule of thumb the consistency argument should trump ...


0

Changing the top bar navigation by page is a problem. The user needs to feel safe and always be able to find their way home if is necessary without clicking too much. If you start changing navigation patterns per page at some point the user is going to loose track. Example: all google products, Facebook, Jira, stack exchange. They are all keeping the same ...


3

Whether it's the hamburger menu or the menu bar, navigation should be consistent throughout your system. This features throughout most accessibility guidelines, is good for SEO, and is just generally good practice.


2

You cannot use mouse-hover on touch screens like tablets and large smartphones, and mouse-hover presents accessibility challenges. Hover also frustrates people if it is triggered by accident, or involves unknown interactions, i.e. hover for 1 second, and can be difficult to use with precision if the hover region is small, etc. So it is much better to use an ...


0

That's a pretty bad IxD. Hovers/tooltips should by shown and hidden with the same method used to enter/exit the area. So when the mouse leaves, it should go back to its prior state. I try to recommend against using hovers in mega menus. Hovering introduces extra things to consider, like timing of the hover to trigger the content to appear. Hover also opens ...


0

as per my experience you don't need to repeat the navigation bar links in footer if there is no additional information or category you want to display then. Then also if you have to keep it there then just drop the contact information with address, phone,email i.e. kinda contact form in footer. For small website footer is not the important but what your ...


1

This really depends on the initial product listing page. Are the filters on the listing page useful enough to aggregate relevant products? Has the page filtered the results enough so that users will want to skim through their results? Are products to the left and right relevant to the viewed product? Is this a search results page? I would definitely be ...


2

You could test your users, or review other sites, especially your competitors and see what they do. Make a spreadsheet and examine your results. If everyone: on-line merchants,banks, and other sites all do the same thing - then that would be a good choice as it would be the industry standard. The two choices I see most often (correct me if I'm wrong) are: ...


0

Depends. If what you are logged into is blocked from those not signed in, then you should take them to a login page or form overlay. If people can still view the content, such as this page, then you should just log them out with some indication that this has taken place.


0

It should inform the user they were logged out successfully and provide a way to easily log back in. This could be a link back to the login form or the login form can be present. The login prices should be within two clicks.


0

As per my understanding,you having confusion with the toolbar. I think when we are displaying the profile info at that time there should be only one back icon in the screen because if you toolbar contains different menu from the profile then there is no need to display toolbar in profile screen. Below is the figure in which I tried to explain you this ...


3

If you're looking for user friendly, then browser's back button should suffice, it's a known and expected behavior, and for one level navigation, it's what most users will look for. Now, if you want to keep context, you could use a modal window, but that will also depend on the content you have for those services and also the kind of behavior you're looking ...


0

Are the users going to check out several services? If so going back and forth can be cumbersome. Maybe you could use a modal window with a close window. You could even allow the users to navigate between services with arrows or thumbnails. If they aren't gonna check several I wouldn't bother with a back button, I would rely on the menu and the ...


1

You can use "breadcrumbs" which is very common and useful. It takes less space(unless you style it heavily) and users can easily navigate to various pages.


1

To expand on the answer given by @PixelSnader there are also occupational health and safety (OH&S) implications regarding head movement. There is a lot of research indicating that while sitting at a computer the screen should be set up so that you can read the screen with very little movement of your head, neck and shoulders. If a website was designed ...


2

If you let if run full width, the text will be very annoying to read. The ideal line length is somewhere between 50 and 100 characters. You could increase the font, sure, but then you'd have to move your head more. So we try to keep text lines shorter. And left aligned with a huge amount of whitespace on the right is just ugly.


3

Mouse-click is always better than mouse-hover, because mouse-click allows you to support all keyboard users, those who may or may not need accessibility support. It also helps you transition to touch-based devices like Tablets and Smartphones where you don't use a mouse, i.e. tap triggers the mouse-click. So benefits all round when you use mouse-click and ...


0

This is called a Bad Idea Because it only makes navigation harder and has hardly any benefit. You could argue that in some cases (tall content sections) you sometimes have 1 or 2 more lines of text on screen. But that doesn't weigh up against the navigation problems it will create. All the other answers mention a (scrolling) navigation bar, and for good ...


1

What you're describing sounds like the "Tab" + menu UI used on the Semantic UI framework, specifically on this page. The behavior of the tabs and the right menu seems pretty similar to what you're describing. http://semantic-ui.com/modules/tab.html#/definition


1

I don't know a specific name for the style, but it seems to be a fixed div with in-page navigation. You put a fixed div at the top of the page with a menu and then each div is named such as <a name="Section 1" /> Then, at the top of your page, in the menu bar (your fixed ), you'd put the link to that section: <a href=”#Section ...


1

If you're looking for something that is literally repeated throughout the content of the page then I don't know that there is a specific name for it but I would call it something like "Repeated inline navigation", maybe? If you're looking for something that has the navigation locked to a certain position (usually the top of the window) and updates based on ...


1

I would try something like "Top bar", "Navigation top bar", "Scrolling nav" or something like that. I don't know if it is official name, but it describes it good. These pages are using something like it: http://andy-hook.co.uk/ https://2015.avocode.com/


1

Just so that you can have a clearer idea about the reasons for the comments, think about two different types of websites, one is mostly informational (i.e. lots of text, images, etc.) while the other is transactional (i.e. lots of workflows, buttons and call-to-actions). Lets look at the informational site first. If your content is mostly short snippets of ...


0

I'm not going to say whether a context-dependent side menu is the right choice or not. I feel like that's more a design-dependent question. What I will focus on is the UX standards and practices that might help you make up your mind. Do you have a complete buildout for all the screens your app will show? I feel like doing this will lead to a natural sort of ...


0

I've never heard of such a thing. Ask yourself, how complex is the navigation on the site? How much sideways navigation will there be? how much content does the site have? If you need to have lots of text and images the user has to read go for smaller navigation, nowadays you can even hide it behind a menu icon. If you need the user to have constant ...


0

I would suggest that you consider the way Apple does it: a More button. Below is a screenshot from AppStore, and upon clicking on it, the content will expand downwards. Apple uses this strategy in iTunes as well. It isn't very easy to implement though, but I think it worth trying :)


2

If you want to make it available to "dig deeper infinitely through the application", it's really gonna be difficult to use. But if there are only 2 or 3 levels of hierarchies, you can do some indentations. (courtesy of IMDb app) The screenshot here only has two levels, but if you want to go deeper, you could have a sub-level with more indentation. (Just ...


4

Generally, for mobiles, breadcrumbs are not recommended; the back button is what the users are familiar with. Also, it is said that; if your app needs a breadcrumb then your app is not easy to use. Even though, if you really want to introduce one - try what Windows does for the deep hierarchies:


0

Perhaps one (slightly left-field) way to look at this would be to investigate accessibility research for people with motor impairments - people who find it difficult/impossible to use mouse/keyboard/touch inputs. Some useful resources: How people with disabilities use the web To use the Web, people with physical disabilities often use specialized ...


1

I'm sure there are other concerns, but the first one that comes to my mind is that the app should be designed to minimize the input of number and letters, as it is usually very cumbersome on this type of device... When it is absolutely necessary to let users input letters/numbers, I would use smart defaults (popular choices for instance), autocompletion or ...


1

I can't see any problem. You have a wheel that can be turn front/back. And push button. You can easily prototype such interface by simulating scrolling by tab/shift+tab and push like enter button. The main thing is to put all elements in proper order (like tab index) and clearly highlight which button is selected currently.


3

Well as you are having a gaming portal, I suggest:- Arrange them by popularity Try to give an option to the user to compare between 2 games like we can see in the websites which compares different mobile phones. 3.The most important-> While displaying a particular game product- you can put Pro's, Con's and compatibility as the definite items to be ...


3

Both (hamburger and nav bar) have advantages and disadvantages that make them suitable in particular contexts. It very much comes down to how much value your users get from functionality that you consider for your main navigation, and more objectively, how often they use that functionality. Spotify is a great example where a nav bar makes a lot of sense: ...


2

Left sidebar occupies prominent space on the screen so the value / utility it provides should be high. The question then is what's the distribution of number of different products a single user has (or more simply how many products a user has on average). And the second question would be how much your users switch between different products? One extreme is ...


4

Hamburger menus, like it or not, are widely recognized Inertia: everyone else is doing it, so we did it and now it's done (until the next major redesign/funding come along) Burgers take up very little space and lend themselves to being tucked into a corner of the screen In many instances, they are effective I want to address that last item in particular. ...


1

I have got over this issue by using a 3 stage left nav & used the hamburger to toggle states, user preference is a key factor as you don't want to hide something from a user who has no experience with that type of nav check out the Google analytics nav for a good example of a simple layered left nav. I prefer the left nav approach personally although ...


1

You can have dynamic menu systems based on some threshold, e.g. one nav menu type below the threshold, a different nav menu type above the threshold. This will obviously involve more development effort, but as I always say "To make something really easy to use, you might have to do a lot of work behind the scenes". Note I am not suggesting a drop-down menu ...


0

This seems to me a bit overcomplicated. Maybe I am missing some point, but I rather would use a multiple navigation sidebar. I find this solution super easy to navigate with a very clear feedback about user position. download bmml source – Wireframes created with Balsamiq Mockups


3

I encountered an issue similar to this with a shopping app where the cards for items were a perfect fraction of the page space meaning that the last item on the page in its default state ended just clear of the fold (page break). During user testing most users reported that there was a lack of items available because they didn't realise they could scroll ...


0

From your image, the only cue that there might be more content below the fold is a missing paragraph explaining C - but that takes careful attention (notice there are A, B, and C in the image) and some inference (if there are explanations for A and B, there should be one for C as well). Otherwise, the design indicates in several ways that this page is ...


0

I don't like to generalize for topics like that. I would definitely say that it depends on the information that the vertical menu presents. In e-commerce websites, most of the times, a horizontal menu is used for bigger e-shops. Personally, I think that the left navigation is waste of space. The main requirement is to leave the user undistracted to focus ...


2

My answer only applies to Android, as I am lacking any long term usage experience with iOS. Add step forward and backward buttons on the bottom (if this is a wizard like screen), Add the familiar "steps" dots on the bottom too. Provide swipe gestures to go forwards and backwards too. Please do not attempt to create a general solution for Android and iOS! ...


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. Additionally, you could also use Responsive Multilevel Menu which is more or less the same, only that not taking the whole vertical space


8

I would encourage you to consider whether a cancel button is truly necessary in this situation. What is the likelihood that the user will wish to cancel their entire submission? Is it more likely that the user would wish to change pieces of the submission more easily accessible using the back navigation rather than the entire submission? Will other ...


0

A third option is to use a button with an arrow to the left and up (⬑) on the left position in the first step of version 1. This conveys the information that clicking that button goes back to a previous state and that that state also one step back/up in the information hierarchy.



Top 50 recent answers are included