The first sample is a demo of the Tab View in SwiftUI, titled ‘About Me’ 🤭
Before we dive into that, lets discuss the format of how it is presented & why it is important.

This is a list of all our Sample App projects. You notice each file extension is ‘swiftpm’. They did this so we can run the sample on macOS & iPad using Swift Playgrounds. I would prefer if all the samples had this option, where appropriate. Anyway, you can use more than Xcode to create demos.

TabView {
    MewView()
        .tabItem {
            Label("Info for MewView", systemImage: "cat")
        }
    SomeView()
        .tabItem {
            Label("Info for SomeView", systemImage: "book")
        }
}

Now- I don’t know if you were wondering this, but I thought- can this become like Inception? 😴
That movie comes to mind as we had folks going to have dreams inside of dreams- Can we stack TabViews too? The honest answer is: We should not. Apple developers & designers should be familiar with Human Interface Guidelines.

‘YourData.swift’ in section 2, they introduce the idea of separating concerns: our info is stored here & the other user interface files reach into here to display content. That’s usually the way things are done, whether we have data stored on disk, or we are reaching to the cloud to pull it down; the user interface will behave as a template for ordering this information we get. From sections 3 – 6, they just break down the content of each tab, reinforcing concepts of things like VStack, Text, Image & ScrollView