×
Namespaces

Variants
Actions
(Difference between revisions)

Tabs Usability

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix metadata etc)
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
 
Line 22: Line 22:
 
}}
 
}}
  
[[Category:Mobile Design]][[Category:Usability]]
+
[[Category:Usability]]
  
 
==Description==
 
==Description==

Latest revision as of 03:42, 9 May 2012

Article Metadata
Article
Created: naresh99 (19 Jun 2009)
Last edited: hamishwillee (09 May 2012)

[edit] Description

Tabs provides navigation between different views/controls. Each tabs show name of open controls in rectangular box with its top borders rounded. User can navigate between different tabs using arrow keys. Usually active tabs highlighted to distinguish it from other inactive tabs.

[edit] Example

Keep followings general rules in your mind while designing your application with tabs.

  • The first tab should contain most essential functionality of the application. Underlying tabs can be used to hide advanced functionality.


Good tab example
Tab1Good.JPG

Bad tab example
Tab1Bad.JPG


  • Highlight currently selected/active tab and its title. Set title of others tabs dimmed/faded. Also make sure that the title of unselected tabs are clearly visible and readable.


Good tab example
Tab2Good.JPG

Bad tab example
Tab2Bad.JPG


  • Allow users to switch tabs using left and right arrow keys.


Good tab example
Nav available.jpg

Bad tab example
Nav unavailable.jpg


  • Connect the active tab to content area.


Good tab example
Tab4Good.JPG

Bad tab example
Tab4Bad.JPG



  • If tab is an icon (rather than text) then use tooltips to give description of tab


Good tab example with tooltips
Tab5Good.JPG

Bad tab example without tooltips
Tab5Bad.JPG



  • One row of tabs preferable than multiple rows.
  • The row of tabs preferable on top of the panel.
  • Change the font color of title on the active tab.

Changing the font color will give your active tab even more differentiation, and will allow people to quickly scan the navigation for the other view available to them.

  • Tab Labels should be short usually one or two words.
  • Try to limit the number of tabs if possible, so that the users need not scroll.
  • For a full screen application or if there is a user's requirement, customized tabs could also be provided.

[edit] Related Links

This page was last modified on 9 May 2012, at 03:42.
119 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×