Let's talk about the page control now. A page control indicates number of available views, and also shows which one is currently visible. You should use a page control when it's more important to show users how many views are available than it is to help them choose a specific view. According to Apple, user page controlling situations in which each view is appear of every other view, that means slides walkthroughs, things like that. Not sure apps general sections might be possible, like in the weather app. Yes, this element is particularly popular for the walkthroughs It can be as basic as shown here.
Don't forget to include the button to skip the walkthrough. It can be also part of a very fancy walkthrough. As you see in this example, we have a lot Nice animations here to pitch control works in the gu standard way. Additionally, you can add some buttons to navigate between the available slides can be arrows, or text with an arrow. In this example here, we have just forward buttons at the bottom. If you don't include a skip button, make sure you have as few slides as possible.
With just three slides you can get away without allowing users to skip this intro. Page control displays an indicator dot for each available view in app. By default, it uses an opaque.to represent the currently visible view and translucent dots to represent all other variable views. It doesn't allow users to visit views not sequentially and it doesn't allow to tap the dots which control element doesn't shrink or squeezed out together when you add more of them include swiping navigation between the views. And the technical note for developers. A push control doesn't enable navigation between views by default, it must implement a view to view navigation and update the page control state appropriately.
To use a batch control to display views in a hierarchy, or other complex arrangement, it's used just for flat hierarchy views. Avoid displaying too many dots cannot use more than 10 mean no more than 10 slides for example, more than about 10 dots are hard for users to count at a glance, more than about 20 open views are time consuming to visit in sequence. If users can open more than about 20 years of using your app, consider displaying if used in a different arrangement that provides more information about the views and enables non sequential navigation used MX. If it's more use other UI partners. Lastly, according to Apple, you should center page controls at the bottom of the screen. A pitch control should always be centered and positioned between the bottom of the content and the bottom of the screen.
This keeps it visible without blocking content.