Static screens only get you so far. Real apps respond to taps, hold changing data, and move between screens. This module covers how SwiftUI handles all three: state, navigation, and the architecture that keeps it all organized.
You'll start with @State and @Binding, the property wrappers that tell SwiftUI when a view needs to redraw, and learn how SwiftUI decides what to update. Then you'll move between screens with NavigationStack and NavigationLink, and finish with MVVM, a pattern for separating your data and logic from your views.
Some lessons are clips cut from longer courses, and one of them predates the newer @Observable macro, so treat it as the underlying idea rather than the latest syntax. When you're ready, continue on to UIKit Essentials.
Make a view respond to changes with @State, and share that state with child views using @Binding.
How SwiftUI describes, updates, and redraws your views, and why it matters for the way you write them.
Move between screens with value-based navigation, and see how the navigation path works.
Separate your data and logic from your views with a view model, and see how data flows between them.