New answers tagged navigation
0
Conceptually, the link back to the main website lives at a different level from the main navigation of the current careers page. It's function is entirely different. So make it different and make it stand out.
You could put a bar at the top of the page that links to them could be a solution. Google uses this for instance, because all their services are ...
0
You may want to consider the Extra Site Navigation pattern.
http://books.google.com/books?id=LC0cG-vFJbcC&pg=PA99&lpg=PA99&dq=extra+site+navigation&source=bl&ots=CWj5WudP79&sig=YGvTVzoIvcwe2gT7AfnJP2T0a8w&hl=en&sa=X&ei=4ESdUdfNBoXPigLc6YHIAw&ved=0CEAQ6AEwAw#v=onepage&q=extra%20site%20navigation&f=false
1
Apple's own Reminders app has a good example of the functionality you are asking about.
Reminders has a left column of checkboxes next to the items and a disclosure chevron on the right side of the reminder column. Touching a checkbox selects the checkbox and touching the reminder slides the user to the details page.
Link to image: ...
7
The modifiers for the tab key are already taken for important window management tasks:
Ctrl+Tab cycles through tabs in the browser as it is the common shortcut for cycling through open documents in the same application. Shift+Ctrl+Tab goes backwards. Alt+Tab switches between running applications.
It would be unexpected, and highly annoying, for a single ...
1
Have you looked at the Google Plus Circles UI? That's an awesome way to move a large number of people into smaller groups.
It solves a number of your requirements:
people can be in multiple groups
it's easy to show people that are not yet in a group by filtering the overview of available people
it makes great use of your screen real-estate for ...
1
You seem to be trying to solve a problem without any indication that it is a problem. You should do some ux-testing to see if it actually is a problem for your users, before you spend time complicating your interface to solve it.
In many situations, people use tabbed browsing to open up a new site in a new tab, and so don't ever need to navigate back. ...
0
This is a bit old school but perhaps will help stir the creative juices.
A list builder is a classic example of this functionality. In that case, the tree grid ends up being the "view" of the teams (and in this case, you could pivot that view by teams or by people/players).
The benefits of the list builder, assuming attributes may have a one:many ...
0
Why change the navigation?
For one thing, your top nav appears to be a permanent navigational tool, but then it completely changes upon click. That's very disorienting for the user.
Supplement with a breadcrumb
Assuming you fix that issue (if you agree that it's an issue), you can supplement the top nav in subsequent pages with a breadcrumb:
Personal ...
1
Looking at your pages, a simple solution would be to have a top section just devoted to a link back to the main page which allows the user to quickly navigate back to the lawyer jump page. My company's creative wing's site has this as shown below
The only time this link will not be available at the top is when he is the Lawyer jump page since there is no ...
1
Make it intuitive and proceed observantly.
In 2009 a Nielsen Norman Group finding Big, 2-dimensional drop-down panels group navigation options to eliminate scrolling and use typography, icons, and tooltips to explain users' choices.
This sounds great... but (and this is all very old by internet standards).
In 2010 they revised their statement after ...
2
2 different usage patterns mentioned in the Win 8 UX navigation pattern guidelines:
Initial pattern says Back button should take you back to previously visited page and not hierarchy.
Header and Back button:
The header labels the current page and is useful for wayfinding. The Back button makes it fast to get back to where you were.
Further down ...
2
Horizontal menus and vertical menus are needed to aid information architecture - otherwise there is a danger to end up with the menu like the one on old Amazon website (could not find image unfortunately).
Typically, horizontal menu would be used at higher level, perhaps even horizontal subnav, but you definitely would not want to have a third layer of ...
6
Horizontal menu's don't readily support more than one level. Nesting or indentation are difficult to achieve, leading to many hard to use solutions widely documented in many articles and here on UX.SE. I'm no big fan of the Windows 8 website for instance, at the third level deep it just becomes weird.
Web documents are usually laid out for scrolling ...
1
I think it would be fair to say that the user interface has to be designed for the content first. It is much harder to take into account of things such as the user environment, hardware devices and habits because these are much more variable. On the other hand, with content it is much more feasible to take into account of the types of elements, the number of ...
1
Since the user will be reading in downwards direction for each article, it would make more sense for each next article to be below the current one. This way a user can just keep on scrolling to go through the article, instead of switching downwards, sideways, downwards, sideways. One app that does this well is Reeder on the iPhone, but there are many others. ...
2
If you are using sliding animations between screens, you should stick to the convention that pushing a new view from the right = forward, and from the left = backwards. Otherwise your sliding animation not only looses its purpose, but it actually then causes confusion by implying something that isn't true.
The second part of your question is more ...
6
Menus are a navigation element and so what make the most sense is whatever makes navigation easier for your users.
Your first example is a good menu, as although you have only one item under 'Otters', it wouldn't make sense renaming 'Otters' to 'Sarah' as it would then look like 'Sarah' were a type of animal. Additionally, if you get a second otter to keep ...
1
I would wonder if theres any established best practice for this situation. This would depend on different factors.
Scalability:
If your navigation menu is category based and there is significant possibility that the number of menus under it may increase, its definitely good to keep it as category. Example, If 'Accommodation' may contain 'Guest House', ...
1
A approach I would take is to provide the alternate filtering option on the page of the main level only.For example,taking your last example of filtering by hotels the design would be something like that
download bmml source – Wireframes created with Balsamiq Mockups
The advantage of this method is that you can provide the superset of results ...
2
Menus don't have to be logic they have to be meaning and useful.
If there is one "child" then you do not need a "parent" like a unique radio button does not make sense.
Having sub-navigation on-click is common but very replaceable
Most web sites do not have sub-navigation menus. A book of one chapter does not need a summary: you just read it, a house with ...
1
If you need a back button to navigate around an iOS app, then you clearly need a navbar with a back button.
If however, you have a simple app that doesn't need any navigation, you can leave the back button out, or where it can be navigated entirely by using a tab bar, then a back becomes unnecessary.
Apple do this with many of their default iOS apps. ...
4
If it's just a screen with text on it, then there are two options that work on both a large and a small screen equally well:
Navigate by swiping. Swipe left or right should related to back and forward respectively. This is a common pattern that has proven to work.
Place thin transparent navigation bars on the left and right with a clickable area much ...
0
This is a common scenario with web-based and distributed applications. When you have multiple types of users with different needs, a common solution is to provide ways to customize their view of the data. If you have a defined or finite number of views, then this can simply be a toggle or selection. So if someone chooses a Project view then they get the ...
0
The most important thing here is to make sure and use « instead of <
;D
0
I would propose having two ways to take a "step back" in your website.
Since it's pretty much a short wizard, I would expect each step (except the first obviously) to give me the option to continue ("submit") or step back and revise an earlier choice ("cancel"). When looking for "can I go back", it's logical to look at the bottom of the screen next to the ...
1
Repurposing Visual Metaphors can be confusing
People typically follow habits. If something doesn't work as intended, then it can confuse them or pull them off-track.
Web browsers (with the exception of IE in Windows 8 on a desktop) usually offer an intuitive method of backward navigation. Most of that navigation is pretty consistent between browsers by ...
6
If you're talking about mobile apps, the top left is the standard position for both iOS and Android (technically it's the up button on Android, but that's close enough).
If you're talking about a website, there is no standard placement for a back button, as there is a keyboard back button, and so most sites don't bother with a back button.
That said, I ...
1
First, I am wondering if a progress bar is the best solution here. Progress bars show a continuous progress not a step to step progress.
Furthermore if I see a bar I imagine that I can jump to wherever I want whenever I want. I say "I" because I cannot be sure every user is going to feel the same, but to underline my conviction: video progress bars and ...
0
What you are referring to Progress Bar appears to be a Navigation Bar with Progress Indicator. In that sense, it is alright.
@rk's idea of user "undoing his progress" holds weight but the way I interpret, it is a navigation bar and progress bar showing where in the process you are. That means if you go a page back, you go a step away from your final goal ...
27
It can work well, but I wouldn't recommend the method that you are proposing.
You can use breadcrumbs as a form of progress bar, which not only solves your navigation issue, but shows what still has to happen better than a pure progress bar. It is also common practice on some of the most used websites, so your users are likely to already be used to it.
...
3
If you are using the progress bar to move forward and backward, you are essentially implying that the user is 'undoing' his progress or is able to jump forward (?) in progress.
Separate your concerns and use the progress bar to show progress and use a navigation to navigate. Do not jumble the things. If the user needs to think twice whether his action will ...
0
The point of a card sort is to figure out what mental modal your users have of the information you're presenting, before they see the site. The main thing it lets you do is to avoid the frustration of not finding the foo section under the bar section, when that's obviously where it should be.
If all your users put foo in 'don't know' then that tells you ...
3
I've just done a little quick and dirty analysis on the OptimalSort database for you.
Eyeballing some of the instructions messages suggests that most studies are not prompting the use of a "don't know" group. So I've counted the number of participants who did anyway using the following criteria:
... where label REGEXP '(don\'t|dont|misc|confus|not ...
5
It's a question of costs and risks. Which is worse: users getting an incentive without really trying, or false data being taken during research and becoming misread as "official user feedback"? I'd suggest the latter. Forcing categorisation means participants create weak categories just for the sake of including miscellaneous items. That means weak silos ...
1
Would it be a bad idea to allow them to define groups instead of using the Don't know group? This way, you get them to help with the categorization of cards and then you can use newly created groups to help other users who don't know what how to group their cards.
'Don't know' is fine but I would imagine that someone will have to step in behind someone ...
5
It is absolutely okay to chose that pattern. The only thing you should worry about is making the link different enough from the others that user will know that something else will happen once he/she clicks on it.
The easiest and least subtle way to do this would be to style the tab completely different from other tabs — for example like a link:
Or you ...
10
While you could probably get away with it, it is a bad idea.
If you're going to use a well know pattern like this, it raises an expectation about its behavior. This is why patterns are so powerful and useful: users will recognize them and immediately be able to build a mental model of the way your website works.
If you break this pattern, you break all ...
7
This answer is more or less a paraphrase of what I remember about what Jef Raskins says in The Humane Interface about KLM:
Say K is the time it take to hit a keystroke, P the time to put the cursor in some place of the screen, H the time to go from the keyboard to the mouse and vice versa, M the time for the user so she can prepare to the next action, R the ...
4
The amount of clicks required is something you can measure about an interface. It's a number and if managers like one thing it's numbers. It is however impossible to learn anything about the quality of an interface from a usability/ux point of view by counting clicks.
I have seen it happen: people trying to improve an interface by reducing clicks through ...
0
Since to go back the user must drag the cursor to the back button why not place a red tooltip there (I guess this is what you are suggesting in the question itself). Something like this
download bmml source – Wireframes created with Balsamiq Mockups
1
There are a lot of excellent answers here (makes me wonder if michael intends to vote for an answer at all). I would emphasize one critical point:
This question all but impossible to answer in general terms.
The transition from mouse to touch is a delicate and multifaceted challenge. No one can give you general guidelines that will answer your unique ...
0
You can look at references of touch gestures/actions from searching on the forum and see if you want to trigger a menu based on a specific gesture, and Luke Wroblewski's Touch Gesture Reference is pretty comprehensive. I think on apps there might be a standard, but for websites the context menu should be redesigned so that it is not required, especially if ...
0
I would consider having a task action bar at the top of your list view that scrolls out of the way when the user scrolls down, but is easy to "pop over" the list again using a button in the top bar. This would make those tasks discoverable, while saving screen real estate during the scroll task.
download bmml source – Wireframes created with ...
3
Considering you are really asking about hover menus.
They can be a really good mean in creating a rich content website. It is also a trap in which you do not want to fall.
They are hard to use because they are often badly designed. @Marvin is pointing at some issues you can deal with while using them in your graphic interface.
Amazon has been kind enough ...
0
With the prevalence of tablets and mobile devices I feel that we should move away from hover-centric designs. Touchscreens don't have a "hover" state.
My approach is simple:
Don't try so hard to fit every conceivable link into your header. Instead, design a simple navigation structure with a few broad topics or categories.
Each link leads to a landing ...
-3
My experience is that hover menus and megamenus are hard to use. This comes from personal experience and watching other users. This is especially significant if the user has limited dexterity or poor motor skills.
I also agree that they don't seem to work well with touch interfaces.
9
Two level menus are better for usability than traditional drop-down menus, because the user doesn't have to navigate carefully in multiple directions.
As AskTog explains, with traditional, multi-level drop-down menus:
The bottleneck is the passage between the first-level menu and the second-level menu. Users first slide the mouse pointer down to the ...
0
If you have just a few buttons and only one button with a submenu, then it's not bad user interface. However, if many of them have submenus you might want to consider a side page menu. Otherwise it will be hard to read and not very clear what you are trying to communicate.
0
The example you have given here is a hover menu. Hover menus can help in defining a large navigation and allow users to clearly see the child and sub child nodes of a main navigation and they also save on vertical space.However they are not excellent for usability as this article shows
One of the worse things about hover menus is that they force users ...
2
Typically in this situation applications will present a dialog that looks something like this:
download bmml source – Wireframes created with Balsamiq Mockups
This is in line with your intuition that a warning that "going back" is unsupported behavior is the best UX to provide in this situation.
Note that it may be possible to support the back ...
Top 50 recent answers are included
