Page view controller. A page view controller provides a way to implement land unification between pages of content, such as document to Notepad or calendar, and it uses one of the two styles for that the regular scrolling style, or the page code style as you see here. A scrolling transition has no specific appearance. Pages fluidly scroll from one to the next. A pitch curve transition causes pages to curl over as you swipe across the string, turn like pages in the physical book. In most cases, just go ahead and use the scrolling style.
Scrolling style has no default appearance. It just depends on the content stuff into and simply vertical scrollable. And what happens to the content when you scroll is actually definitely an animation. Mind advice. Use base cross style only if it really serves some purpose. If it's a big boom with many pages, it makes sense to use a scroll style.
That way our user has understanding which page is on and can navigate better throughout the book. Remembering visit specific pages if you want to note that here we have a progress indication, bottom, and some additional buttons to help search and navigate throughout the book. Also, you might use the page curl style with a purpose is to provide some specific experience. Like in this example, the creator's wanted to provide an experience of reading a real book. Also, make sure all visual design is taken care of in these cases, and make it obvious that the users can flip waitress because they're mostly used to scrolling, not clipping. The visual style for this example makes it quite obvious that should be able to flip pages here, at least for generations, who had experience with real books.
Additionally, or alternatively, it will help demonstrate the bridge can curl For Shawn little animation of page being slightly poorer than the US laws the view, you can also show it in the initial walkthrough of your app. Or you could actually just demonstrate it in your apps listing screen shows. Page curl view can be split in half in the spine in between can be added. The kind of animation for the content position in page 12 use Office, the current page appears to turn like a page in a book or not. So use a page view to present content that users access in a linear fashion, such as the text of a story, or content that naturally breaks chunks, such as a calendar, if appropriate, create a custom way to let users access content in a nonlinear way. A pitcher to control itself lets us only move from one page to the next or to previous but it doesn't give users a way to jump among non joining pages.
If you Want to use a basic view controller to present content that users might access in a nonlinear fashion, like in the dictionary, or in the Books table of contents, you must implement a custom way to let users move to different areas of the content. So in this dictionary example, you would tap on letters on the right, and then select the section in the second level that appears, and then you will be taken to a corresponding page. And here's some more examples of custom navigation, Contacts app and a calendar app. Stop navigation