🔒 Uncontrolled dependencies can wreak havoc on a modern SwiftUI code base. Let's explore why, and how we can begin to control them using a brand new library.

🔒 We wrap up the "record meeting" screen by implementing two more side effects: speech recognition, and persistence. We'll experience the pitfalls of interacting directly with these dependencies, and why we should care about controlling them.

🔒 After a brief digression to explore the performance and ergonomics of identified collections, we dive into the messy world of side effects by implementing the "record meeting" screen. We'll start with the timer, which has surprisingly nuanced logic.

🔒 We add more screens and more navigation to our rewrite of Apple's Scrumdinger, including the standup detail view, a delete confirmation alert, and we set up parent-child communication between features.

🔒 We begin to layer on behavior in our rewrite of Apple's "Scrumdinger" demo application, starting with navigation. We will do some upfront work to model it in our application state, as concisely as possible, to avoid a whole class of bugs, unlock deep linking, and enable testability.

🔒 What goes into building a SwiftUI application with best, modern practices? We’ll take a look

at Apple’s “Scrumdinger” sample code, a decently complex app that tackles many real world

problems, get familiar with how it's built, and then rewrite it!

🔒 When all-new SwiftUI navigation tools were announced at WWDC, the one that got the most attention by far was `NavigationStack`, which powers navigation with an array. It is extremely powerful, but comes with trade-offs and new complexities.

🔒 Why did Apple scrap and reinvent SwiftUI’s navigation APIs in iOS 16? Let’s look at some problems the old APIs had, how one of the new APIs solves one of them, and how we can work around a bug in this new API.

🆓 A year ago we dove deep into the topic of navigation in SwiftUI. Then Apple deprecated many of those APIs

at this year's WWDC, replacing them with a brand new suite. To make sense of these changes, let's recap what

we built over those past episodes, and why.

🔒 With "immediate" and "unimplemented" conformances of the Clock protocol under our belt, let's build something more complicated: a "test" clock that can tell time when and how to flow. We'll explore why we'd ever need such a thing and what it unlocks.