A container view controller that manages a radio-style selection interface, where the selection determines which child view controller to display.
- iOS 2.0+
- Mac Catalyst 13.0+Beta
- tvOS 9.0+
The tab bar interface displays tabs at the bottom of the window for selecting between the different modes and for displaying the views for that mode. This class is generally used as-is, but may also be subclassed.
Each tab of a tab bar controller interface is associated with a custom view controller. When the user selects a specific tab, the tab bar controller displays the root view of the corresponding view controller, replacing any previous views. (User taps always display the root view of the tab, regardless of which tab was previously selected. This is true even if the tab was already selected.) Because selecting a tab replaces the contents of the interface, the type of interface managed in each tab need not be similar in any way. In fact, tab bar interfaces are commonly used either to present different types of information or to present the same information using a completely different style of interface. Figure 1 shows the tab bar interface presented by the Clock app, each tab of which presents a type of time based information.
You should never access the tab bar view of a tab bar controller directly. To configure the tabs of a tab bar controller, you assign the view controllers that provide the root view for each tab to the
view property. The order in which you specify the view controllers determines the order in which they appear in the tab bar. When setting this property, you should also assign a value to the
selected property to indicate which view controller is selected initially. (You can also select view controllers by array index using the
selected property.) When you embed the tab bar controller’s view (obtained using the inherited
view property) in your app window, the tab bar controller automatically selects that view controller and displays its contents, resizing them as needed to fit the tab bar interface.
Tab bar items are configured through their corresponding view controller. To associate a tab bar item with a view controller, create a new instance of the
UITab class, configure it appropriately for the view controller, and assign it to the view controller’s
tab property. If you don't provide a custom tab bar item for your view controller, the view controller creates a default item containing no image and the text from the view controller’s
As the user interacts with a tab bar interface, the tab bar controller object sends notifications about the interactions to its delegate. The delegate can be any object you specify but must conform to the
UITab protocol. You can use the delegate to prevent specific tab bar items from being selected and to perform additional tasks when tabs are selected. You can also use the delegate to monitor changes to the tab bar that are made by the More navigation controller, which is described in more detail in The More Navigation Controller.
The Views of a Tab Bar Controller
UITab class inherits from the
UIView class, tab bar controllers have their own view that is accessible through the
view property. The view for a tab bar controller is just a container for a tab bar view and the view containing your custom content. The tab bar view provides the selection controls for the user and consists of one or more tab bar items. Figure 2 shows how these views are assembled to present the overall tab bar interface. Although the items in the tab bar and toolbar views can change, the views that manage them do not. Only the custom content view changes to reflect the view controller for the currently selected tab.
You can use navigation controllers or custom view controllers as the root view controller for a tab. If the root view controller is a navigation controller, the tab bar controller makes further adjustments to the size of the displayed navigation content so that it does not overlap the tab bar. Any views you display in a tab bar interface should therefore have their
autoresizing property set to resize the view appropriately under any conditions.
The More Navigation Controller
The tab bar has limited space for displaying your custom items. If you add six or more custom view controllers to a tab bar controller, the tab bar controller displays only the first four items plus the standard More item on the tab bar. Tapping the More item brings up a standard interface for selecting the remaining items.
The interface for the standard More item includes an Edit button that allows the user to reconfigure the tab bar. By default, the user is allowed to rearrange all items on the tab bar. If you do not want the user to modify some items, though, you can remove the appropriate view controllers from the array in the
In iOS 6 and later, if you assign a value to this view controller’s
restoration property, it preserves a reference to the view controller in the selected tab. At restore time, it uses the reference to select the tab with the same view controller.
When preserving a tab bar controller, assign unique restoration identifiers to the child view controllers you want to preserve. Omitting a restoration identifier from a child view controller causes that tab to return to its default configuration. Although the tab bar controller saves its tabs in the same order that they are listed in the
view property, the save order is actually irrelevant. Your code is responsible for providing the new tab bar controller during the next launch cycle, so your code can adjust the order of the tabs as needed. The state preservation system restores the contents of each tab based on the assigned restoration identifier, not based on the position of the tab.
For more information about how state preservation and restoration works, see App Programming Guide for iOS.
Differences Between iOS and tvOS
Tab bar controllers serve the same purpose in tvOS as in iOS, but provide slightly different user interface features:
In tvOS, the tab bar interface appears at the top of the window. When focus leaves the tab bar, the tab bar remains fixed at the top of the screen by default. To create an interface where the tab bar doesn't remain fixed, but instead scrolls with the content, set the
tabproperty to the appropriate scroll view. In iOS, the tab bar always stays pinned at the bottom of the screen.
Bar Observed Scroll View
In tvOS, swiping down from the tab bar moves focus into the content view; specifically, to the first focusable view that is visually below the selected tab. Swiping down behaves like a normal focus-changing gesture—that is, focus moves in the direction the user swiped. If nothing is focusable immediately below the selected tab, the closest focusable view is focused instead. In iOS, the tab bar always remains in focus at the bottom of the screen.
In tvOS, pressing the Select button while a tab is focused moves focus into the content view. Because there is no direction associated with this change, focus moves to the most appropriate view specified in the content view's
preferredproperty. In iOS, there is no notion of focusing between views.
Tab bar controllers in tvOS do not support customization. A tab bar controller displays only the number of view controllers from its
viewarray that fit on the screen, and does not provide the More interface seen in iOS.