You can watch this episode by subscribing to Cocoacasts Plus.
Mastering MVVM with SwiftUI
The Problem
| 1 | Views, Models, and View Models 03:37 |
|---|---|
| 2 | The Problem 04:49 |
| 3 | A Solution 07:05 |
| 4 | Fixing Code Smells 07:51 |
| 5 | Hiding the Model Layer 06:12 |
| 6 | Meet Thunderstorm 05:50 |
| 7 | Setting Up the Project 06:33 |
| 8 | Populating the Locations View 10:17 |
| 9 | Displaying Weather Data 08:17 |
| 10 | Populating the Location View 08:22 |
| 11 | Displaying Weather Data in the Location View 08:37 |
| 12 | Displaying Weather Data in the Forecast View 11:09 |
| 13 | Adding Locations 10:08 |
With this and the next episode, I want to make sure you choose for the Model-View-ViewModel pattern for the right reasons. I want to avoid that you adopt MVVM in a project because you were told it is a sound architecture or because you think you need view models if you use SwiftUI. In this episode, I want to highlight a few problems a typical SwiftUI application can suffer from. Those problems can be resolved by the Model-View-ViewModel pattern with relative ease.
Instant and Unlimited Access
to 500+ Cocoacasts Tutorials
Monthly
$19 / month
Pay Once a Month
30 Day Money Back Guarantee
Yearly
$8.25 / month (billed annually)
Pay Once a Year and Save $129
30 Day Money Back
Guarantee
