It took so long for me to get the time to successfully focus on the task, I decided to split this topic into 2 parts, and get phase 1 out so I can articulate my gain from what was read.

Where we left off was the final lesson of the second tutorial, and I mentioned I wanted to dive into docs.
Starting off at Binding, I had read it before but so what if this is the eighth time. This time I paid a little more focus to the area where they say it is Mentioned In: – sure search? They repeat search three of the four times. I didn’t attach significance to this before. Started reading the first link and imagining- a search bar. How is it responsible? Making some activity happen, such as a search or maybe a filter, which will probably change some other view. That makes sense.

Further down, docs state we require storage in the form of a String to perform the search. This is where we have our first Binding in the form of ($). Properties are still @EnvironmentObject & @State but this data we are sending to DepartmentList & ProductList will end up changing those views. I hope I am understanding this correctly.

struct ContentView: View {
    @EnvironmentObject private var model: Model
    @State private var departmentId: Department.ID?
    @State private var productId: Product.ID?


    var body: some View {
        NavigationSplitView {
            DepartmentList(departmentId: $departmentId)
        } content: {
            ProductList(departmentId: departmentId, productId: $productId)
                .searchable(text: $model.searchText)
        } detail: {
            ProductDetails(productId: productId)
        }
    }
}

The next link used nearly the same substance as the first, I would have expected the examples to be different 😅
Third link discusses activating the search link. I’m a little searched out, I want to dive into Binding.
Fourth link is my favorite as it has this graphic:

OK- so Our view, on top, has a @State or @Environment property, our subview which has the Binding takes the $ sign. Inside this view, this property would be @Binding and the data has the potential to change the whole view. Does this make sense? Anyone agree or disagree with my theory of Binding? Feel free to email me at info<at>mvilabrera.com and let’s chat! It took me awhile to grasp this so if I am getting it wrong, please let me know. 🙂‍↕️

Now I feel like I got heaps out of reading all those docs, yet the tutorial feels flat. I’m at an impasse, it is self-imposed. We have SwiftUI Sample Apps, which is nice, they are teaching stuff we didn’t work on such as networking, gestures & machine learning. What I do not like is, lessons are pre-formed like it is here. 🫤 Then there is Scrumdinger, which is an app that helps organize meetings, with a timer & a bell. Apple hasn’t really linked to this so… idk- but I like this because we are creating a new app & creating new files as we go. Develop In Swift is also there, they cover Swift Testing, Swift Data & visionOS. I can’t decide which to start with and explore.