<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://uizine.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Application UI Design</title><subtitle type="html" /><id>http://uizine.com/blogs/applicationuidesign/atom.aspx</id><link rel="alternate" type="text/html" href="http://uizine.com/blogs/applicationuidesign/default.aspx" /><link rel="self" type="application/atom+xml" href="http://uizine.com/blogs/applicationuidesign/atom.aspx" /><generator uri="http://communityserver.org" version="2.1.61120.2">Community Server</generator><updated>2007-03-27T12:29:00Z</updated><entry><title>Deciding On a Navigation Metaphor for Your Business Application</title><link rel="alternate" type="text/html" href="http://uizine.com/blogs/applicationuidesign/archive/2007/03/27/start-button-navigation.aspx" /><id>http://uizine.com/blogs/applicationuidesign/archive/2007/03/27/start-button-navigation.aspx</id><published>2007-03-27T19:29:00Z</published><updated>2007-03-27T19:29:00Z</updated><content type="html">&lt;IMG title=Compass style="MARGIN-LEFT:10px;WIDTH:100px;HEIGHT:136px;" height=136 alt=Compass src="http://uizine.com/art/compass.gif" width=100 align=right&gt;Coming up with a main navigation design for a complex business application is not easy. It's even harder when the app is highly configurable and the UI has to accommodate the needs of different user types. 
&lt;P&gt;&lt;STRONG&gt;One navigation for all&lt;/STRONG&gt;&lt;BR&gt;My company's&amp;nbsp;application suite breaks down into several different products. However, to the end-user they are seamlessly integrated into one environment or web application. The main navigation serves as a gateway to the different features a user has access to. Regular employees can only access features such as setting their goals and doing their performance appraisal. For other users such as recruiters, the application is used&amp;nbsp;for daily tasks including the creation of&amp;nbsp;requisitions and to advance candidates. To sum it up, the design of the navigation has to take into consideration that some people are using the application on a daily basis&amp;nbsp;and&amp;nbsp;other users as little as once a year. &lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The horizontal menu approach&lt;/STRONG&gt;&lt;BR&gt;For a while we were using a pretty standard horizontal navigation bar. This type of navigation&amp;nbsp;performs well in usability tests as everything is&amp;nbsp;in front of the user.&amp;nbsp;It is&amp;nbsp;accessible with one click.&amp;nbsp;The menu&amp;nbsp;also serves as an orientation tool since menu items are highlighted and indicate the page the user&amp;nbsp;is on. The menu had two main levels (two horizontal bars) as well as drop-downs on several menu items&amp;nbsp;for quick&amp;nbsp;access to recently viewed items. &lt;/P&gt;
&lt;DIV style="CLEAR:both;TEXT-ALIGN:center;"&gt;&lt;IMG alt="Horizontal Menu Bar Screenshot" src="http://uizine.com/art/horizontalMenuBar.gif"&gt; &lt;/DIV&gt;
&lt;P&gt;This is&amp;nbsp;comparable to a lot of navigations used on major Web sites such as Amazon.com or Fidelity.com.&lt;BR&gt;This approach&amp;nbsp;had three major disadvantages: First,&amp;nbsp;the menu bars&amp;nbsp;take up extremely valuable vertical screen real estate. We would like to move data grids and long forms as far up as possible so that critical data doesn't get pushed below the bottom of the viewable browser area. With the sub-menu bar exposed we lost about 50 pixels worth of vertical space. Secondly, it makes the screen look busier with all available navigation choices constantly displayed. This might be good for a power-user who knows the application well&amp;nbsp;and wants quick access to everything. On the other hand, for a user who is in the system twice a year for a very specific task,&amp;nbsp;seeing all available choices is too consuming and&amp;nbsp;intimidating. The last disadvantage of this approach is the limited availability of horizontal space for long menu labels (the labels are customizable plus translatable). Adding dynamic horizontal scroll buttons&amp;nbsp;on the right end of the menu bar is not too appealing.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;No main navigation at all?&lt;/STRONG&gt;&lt;BR&gt;Another option was to remove the navigation entirely and force users to access all pages and features through contextual&amp;nbsp;links in their homepage and their task list. The homepage in this case is a dashboard with feature specific widgets. The task list is one of the widgets available on that dashboard. There also is&amp;nbsp;a&amp;nbsp;globally available task list button on the top of the screen. This approach seemed suitable for users such as regular employees who log into the system a few times a year to perform a single task. You can see that it wouldn't work well for users who use the application more often, most of the time to perform several tasks. They would have to go back to the dashboard to navigate somewhere else. Finding the links might be hard as they are sprinkled across the different widgets on the dashboard.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The best solution&lt;/STRONG&gt;&lt;BR&gt;The best solution was to clean things up using a one button menu.&amp;nbsp;This is&amp;nbsp;not a new idea. It's pretty much how the MS Windows&amp;nbsp;&lt;EM&gt;start&lt;/EM&gt; button works. The button sits in the top right corner of the app, consuming very few pixels. It glows orange when hovering over it. Clicking on it drops down the main navigation panel. The panel is a DIV with see-through PNGs on its sides for the&amp;nbsp;shadow effect. We regained a good chunk of vertical real estate and the application looks much more inviting for more novice users while providing the right level of accessibility the everyday user needs. Use of larger 32x32 icons makes menu options easily identifiable.&lt;/P&gt;
&lt;DIV style="CLEAR:both;TEXT-ALIGN:center;"&gt;&lt;IMG title="Drop Down Menu Screenshot" style="WIDTH:431px;HEIGHT:276px;" height=276 alt="Drop Down Menu Screenshot" hspace=10 src="http://uizine.com/art/dropdownMenu.gif" width=431&gt;&lt;/DIV&gt;&lt;BR&gt;Similarly, Microsoft cleaned up the UI of Word by getting rid of the horizontal menu bar.&amp;nbsp;A one button menu now has all the choices ready if needed. This makes for a much less overwhelming interface. &lt;BR&gt;&lt;BR&gt;
&lt;DIV style="CLEAR:both;TEXT-ALIGN:center;"&gt;&lt;IMG title="Word 2007 Menu Screenshot" alt="Word 2007 Menu Screenshot" hspace=10 src="http://uizine.com/art/officeMenu.gif"&gt;&lt;/DIV&gt;
&lt;P&gt;Early usability tests have shown that the new&amp;nbsp;menu works well for our diverse set of&amp;nbsp;user needs. It's another helpful step in making business applications more inviting and fun to use. &lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Additional options for power users&lt;/STRONG&gt;&lt;BR&gt;This is not where the potential of this type of navigation approach ends. This design lends itself to using helpful little shortcuts. For example, double-clicking on the round menu button takes the user back to the homepage -- the dashboard in our case. Ultimately the menu could be expanded by using key shortcuts, and individual menu items could be selected by using the up and down arrows on the keyboard. This is&amp;nbsp;just like the Windows &lt;EM&gt;start&lt;/EM&gt; menu behaves. Then we avoid the mouse click altogether. The user opens the app, clicks the alt key to expand the menu, and presses the down arrow key&amp;nbsp;twice to get to the feature he or she needs. Once on the page the cursor already sits in the first form element -- not one&amp;nbsp;mouse click...&lt;/P&gt;&lt;img src="http://uizine.com/aggbug.aspx?PostID=276" width="1" height="1"&gt;</content><author><name>Tobias</name><uri>http://uizine.com/members/Tobias.aspx</uri></author><category term="Drop Down Menu" scheme="http://uizine.com/blogs/applicationuidesign/archive/tags/Drop+Down+Menu/default.aspx" /><category term="Navigation" scheme="http://uizine.com/blogs/applicationuidesign/archive/tags/Navigation/default.aspx" /><category term="Information Architecture" scheme="http://uizine.com/blogs/applicationuidesign/archive/tags/Information+Architecture/default.aspx" /></entry></feed>