It works like this:
On a certain topic, the content is divided into 3 tabs. Each tab represents an aspect or section of the topic.
The first tab is here selected. It shows information about the topic. When the second tab is tapped…
… that tab gets highlighted and the content corresponding to that aspect is shown. When the final tab is tapped…
… it is selected and the corresponding content is displayed.
Tabs are used when you want an amount of information on a topic to be distributed over different sections. Those sections are displayed in a horizontal row of 2 to 5 tabs. The section labels are displayed in the tab.
Tabs are similar to segmented controls in wanting to help the user find particular data without changing the current view, but segmented controls work as filters, and tabs divide the data into different sections. When you want the user to switch between data that doesn't fit one set, you should use a tab bar.
- Straight forward way of distributing data over different sections
- Originally coming from web interfaces, so users are probably familiar with the principle
- It can take up a lot of screen real estate, when the app also contains a title bar, or action bar, and a heading
- When more than 3 tabs are used, there's not a lot of space for a label