Alright, let's now talk about the split view controller. And let's just call it simply a split view. A split view manages the presentation of two side by side panes of content, with persistent content in the primary pane, and related information in the secondary pane. Each pane can contain any variety of elements, including navigation bars, toolbars, top bars, tables, collections, images, maps, and custom views. Split views are often used with filterable content. At least the filter categories appears on the primary pane, and the filtered results for the selected category are shown in the secondary pane.

Primary panes on the left and secondary panes on the right. Display the persistent information in the primary pane on the left and related details For subordinated information in the secondary pane on the right, in a way, primary pane usually acts as a menu, and the right one displays the content associated with a particular selected menu item. Well, and this is the core essence of the split view displays both panes side by side in the horizontal irregular environment. That is what we perceive as a split view actually. The primary pane can overlay the secondary pane and can be hidden off screen when not in use. This is particularly useful when the device is in portrait orientation.

So it allows more room for viewing content in the secondary pane. Guess what here in compact iPhone environment, this is actually a split view, with a primary pane being hidden and accessible by tapping the messages button. In the navigation bar, or swiping to the left, so the primary pane transitions to a hidden mode in compact environments. And what looks like this in the horizontal the regular environment becomes this, the compact environment. Split you can contain basically anything, all the regular things, all the other types of use and controls. Choose a split view layout that works well with your content.

By default, a split view devotes a third of the screen to the primary pain and two thirds to the secondary pain. The screen can also be split into equal hearts. Choose an appropriate split based on your content. Make sure that things don't look unbalanced. Avoid creating a secondary pain that's narrower than the primary pain restrict them. occasion to one side of a split view.

Having navigation in both panes would make it very difficult for users to discern the relationship between the two panes. You can display the nav bars in both panes, but only one of them should have the navigational elements like going back, and it's usually the left pane. persistently highlight the active selection in the primary pane. Although the secondary panes content can change, it should always correspond to a clearly identifiable selection in the primary pane. This helps people understand the relationship between the panes, the that means you highlight somehow the selected item on the left pane to show that it's the current one. And the associated content shown in the right pane needs to always be relevant to that selected item.

This view and experience helps people understand the relationship between the item in the primary pane and the contents of the section. Under pain, as I said, I think like three times already provide multiple ways to access a hidden primary pain. On layouts where the primary pain may be off screen, be sure to provide a button typically in the navigation bar to reveal the pain. Unless your app uses the swipe gesture to perform other functions, let people also swipe from the side of the screen to access the primary pain. As you see in this example, I can use both the button in the navigation bar and the swipe gesture to reveal the primary pain. Also, in some cases, the split view can display the primary pain layered on top of the secondary pain