So far, we’ve built a handful of apps, all using a single page. A single page has worked well for the sample apps we’ve been building and works equally well for several commercial apps in the real world. But often, you need more than one page, for example, to distinguish different areas of an app or logically group functionality. Additional pages become especially necessary with nontrivial apps when they grow too much to cram everything into a single screen. In this chapter, we’ll look at navigation paradigms and the different ways that .NET MAUI supports providing multiple pages in your apps and navigating between them.
ContentPage is the most important page type. Other page types are just containers that provide different navigation paradigms that offer a way to present a ContentPage.
ContentPage has a single public property of type View called Content, which is what the page will render on screen. In XAML, the Content property is assigned by placing the XAML element between the opening and closing <ContentPage...> ...</ContentPage> tags, as in listing 7.1. In C#, you can assign it just like any other property, as in listing 7.2.