Many view controllers have to load data asynchronously. We explore different options to factor out this code using protocols, container view controllers, and generics.

We refactor our code by moving the app's flow from the storyboard into a separate class. Our goal is to manage the view controller flow from a central place so that view controllers don't have implicit knowledge of their context.

We explore how Swift's generics can be used to create a simple, reusable table view controller. As a welcome side effect, this process helps us keep our view controller code clean.

Stack Views are great for prototyping. To make them even easier to set up in code, we create an abstraction using enums to specify UI elements in a declarative style.

We show how you can build a generic, type-safe table view controller that can display different types of items using multiple cell classes.

We refactor some view controller logic while working on our upcoming tvOS app. Instead of letting multiple view controllers manage the navigation bar's state individually, we pull this code out and unify the logic in one place.

We look at multiple ways to create variables that have a class type but also conform to a protocol.

Brandon from Kickstarter joins us and shows how the company uses view models to write highly testable code. We integrate Apple Pay payments and look at Kickstarter's open-source codebase.

Brandon from Kickstarter joins us to discuss deep linking into an iOS app. We show how to unify all potential entry points into the app using a common route enum, and then we take a look at this pattern in Kickstarter's open source codebase.

Brandon from Kickstarter is back to show us how the company uses playgrounds to prototype and style individual view controllers.

This week Lisa joins us to demonstrate the test-driven approach to reactive programming taken at Kickstarter.

We refactor a declarative wrapper around stack views we wrote in episode #7. Instead of wrapping UI controls to provide an interface with callbacks, we write a dedicated target-action class.

We show how the reducer pattern can be used to make typical view controller code more testable.

We build a component similar to NSFetchedResultsController, but without the reliance on Core Data. This component can be reused whenever we need to drive table view animations.

We refactor our reducer-based project from episode #62 to use The Elm Architecture. Instead of interacting with UIKit directly, we build a virtual view hierarchy and let our Elm framework do the rest.

We extend our Elm-style app with a more dynamic view hierarchy by adding a navigation controller and a table view.