The Myth of the MV pattern: Why SwiftUI developers just reinvented MVC
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
The MV pattern, promoted in SwiftUI communities as a modern alternative to MVVM, is argued to be nothing more than a rebranding of the classic MVC pattern. Apple's own WWDC19 data flow diagram mirrors the original MVC diagram from 40 years ago. The so-called 'aggregate models' in MV are functionally equivalent to MVC controllers, just renamed. MVVM's view models serve distinct roles that MV cannot cover — such as enabling unit testing of view logic, supporting object identity for delegation patterns, and enforcing proper separation of concerns — making strict adherence to MV an anti-pattern in SwiftUI development.
Table of contents
Enjoying this article?Table of contentsThe SwiftUI data flow diagram presented by Apple is the diagram for the MVC patternAggregate models in the MV pattern are just MVC’s controllers with a fresh coat of paintEnjoying this article?View models have never been against Apple’s frameworks, and they have existed for a long timeMVVM’s view models fulfill roles that cannot be filled by any of the layers in the MV patternConclusionsEnjoying this article?1.3K Impressions