Okay, let's talk about a popover. A popover is a transient view that can be revealed when people tap a control or tap in an on screen area. Transition basically means transitory. Temporary. popover is a type of a model view. According to the guidelines, you're supposed to use popovers on the horizontal irregularly environments, horizontally compact environments, you're supposed to use other types of models instead, model view and self bid fullscreen and not action sheets, activity views.
There are however situations when you can use popovers in compact environments as well, and we will get into that later. Generally, use a popover to display additional information or actions related to the focus or selected object. In particular, it's useful when a specific action requires extra user inputs before proceeding. It can be as simple as one extra choice, as we see in this example. Or it can include multiple extra inputs. It can even include multi level navigation.
As you can see here. Here we have the segmented control. And then we have the categories inside, and each of them might have even more levels inside. That can be a lot of combinations in cases. No wonder, because the popover is a tool that is used on iPads instead of all those regular model views, action sheets and activity views. So it can contain a wide variety of objects and views within it table, which is simply at least image map text, web queue, and custom views, as well as navigation bars, toolbars and tab bars.
And of course, it can contain also other controls that act upon objects in the current app view. Let's take a look at a few more example. Here's a popover with an activity view. Here's the one with the table. Yep, guidelines referred to as a table instead of release. Well, you know, it's a table is just one column.
Here's another one with a list of contacts. Check it out. It has basically a navbar, a search bar, a table view, and the segmented control. Now, let's go over some details and recommendations from Apple. First, as you have already noticed, a popover displays an arrow that indicates the point from which it emerged. It has a translucent background and blurs content underneath just as many other UI elements do since iOS seven.
By default, they will use navigation bars and two bars in the popover is a transparent background, meaning they don't have any visible background at all. That is to let the popovers blurring show through. So for the default UI style in order for a popover to be consistent with other UI elements, you're not supposed to add any extra backgrounds to the elements that the popover things you might do though, for some specific functional or aesthetic reason, in your particular case. In the horizontal the regulatory environment, meaning mostly on iPads, an action sheet always appears inside a popover and so does the activity view. A closed button, such as cancel or done is worth including if it provides clarity, such as exiting with or without saving changes. In general, a popover should close automatically when its presence is no longer necessary.
In most cases, a popover should close when someone taps outside of its bounds or selects an item in the popover If multiple selections can be made, the popover should remain open until someone explicitly dismisses it with a cancel or Done button with taps outside of its bounds. In general, save users work when they tap outside the popovers borders. Not every proposal requires an explicit dismissal, so people might dismiss them mistakenly discard the work people do in the popover. Only if they specifically tap a Cancel button. A proposed arrow should point as directly as possible to the element that revealed it. Because popovers can be dragged around on the screen.
A popover shouldn't cover essential content people may need to see while using the popover. A popover also shouldn't cover the element that was tapped to show the popover ensure that only one popover is visible on screen at a time. You shouldn't display more than one popover custom view designed to look behaves like a popover at the same time. In particular, you should avoid displaying a cascade or hierarchy of popovers simultaneously, in which one popover emerges from another, you can need to show a new popover close the open one first. Don't display any other views on top of a popover. Except for an alert, nothing should be displayed on top of a popover.
Actually, Apple itself does it though. For example, in this case of showing the shortcuts bar popovers on top of the apps popovers. Those can be considered system popovers though, so listen to applicants and don't create popovers over popovers in your app. When possible, let users close one popover and open a new one with one tap. This behavior is especially desirable when several different bar buttons each open a popover because it's prevents people from having to make extra taps. Avoid making the popover too big a popover shouldn't appear to take over the entire screen.
Instead, it should be just big enough to display its content and still point to the place it came from. The height of a popover is not constrained, so you can use it to display a long list of items. In general, though, you should try to avoid scrolling a popover that enables a task. Note that the system might adjust both the height and the width of a popover to ensure that it fits well on the screen. When a popover grows in size due to the number of contained elements, and reaches the bottom edge of the viewport, it is possible to scroll within the popover. Use standard UI controls and views within a popover.
General popovers look best and they're easier for users to understand when they contain standard controls and views. Make sure a custom popover still looks like a popover. Although it's easy to customize many of the visual aspects of a popover. Avoid creating a design that people might not recognize it as a popover. If you change the appearance of a popover too much, users can't rely on their prior experience will help them understand how to use it in your app. Provide a smooth transition when changing the size of a popover.
You might want to change the popover size if you use it to display both a minimal and an expanded view of the same information when you adjust the size of visible popover animated change, because it avoids giving the impression that a new popover has replaced the old one. Now, let's go beyond the guidelines again. And take a look at the examples when it makes sense to use a popover in compact environments as well. First, a somewhat popular way to use it is as a navbar drop down as you see in these examples. Another case when it's okay to use a popover in compact environments is when the popover is pretty small. And an extra driving factor can be having quite a custom looking before, so it wouldn't really fit well in a standard action sheet or activity view.
In these cases, go ahead and use it if you want to, like in these examples here. Also note that you can actually show the popover on any side of the associated object, in case you need that. And by the way, here we see a popover with just the text. You can use it for giving some hints here and there. For example,