[Suggestion] Move <Shell> XAML out of App.XAML into its own class.

[ToolmakerSteve]

Yesterday I tried to help an SO MAUI question where a person tried to pull <TabBar x:Name="PhoneTabs">... into their own MAUI App class, then work with those elements in App.xaml.cs.

Not surprisingly, they weren't succeeding: They were attempting something that would only work within a Shell PAGE, not the APP.

Seeing this, I suggest that the example might be a more useful starting point if the "page" XAML was a separate class, with its own code behind.

---

(I would link to the question, but it has been removed. Based on a comment OP made just before removing it, they became upset and thought that I was (criticizing? insulting? not sure) what they attempted. Whereas what I intended to convey is that a) MAUI isn't ready yet to work with, unless one is already an experienced Xamarin Forms developer (who would have understood my comment suggesting they make this code refactoring before continuing), and b) that WeatherTwentyOne example had caused this confusion by making it seem (at first glance, to someone not well-versed in XAML and XF) that these elements were part of the App class, whereas they are actually part of Shell, which is a Page.)