This article is about adding a separated Services-layer to an app. A Services-layer is, in my opinion, the single best app architectural addition you can make, after the basic Model-View separation already implicit in SwiftUI.
Slicing an app into modules is the best organizational step you can make. It's a step you should take before you choose to make any other deliberate architectural choice.
I'll look at the pattern that application architectural pattern that emerges naturally when writing SwiftUI apps in a minimalist way. I'll also look at the different roles that exist in the basic SwiftUI application architecture.
This article will be the final third of my investigation, looking at sequencing and threading in Combine; what guarantees does Combine offer for thread safety and delivery order. I'll finish up with a quick look at Combine's performance.
This article will be the first third of my investigation into Combine, covering an effort to re-implement the three key protocols of Combine: `Publisher`, `Subscriber` and `Subscription`
This article will look at how SwiftUI's approach to declarative views compares to CwlViews, why the two approaches differ and what Apple changed to make this possible. I'll end with some thoughts about how this will affect macOS and iOS development.
