Thanks! It is not 100% based on Apple's sample projects but also my personal experience in creating SwiftUI and React apps. I find React, SwiftUI and Flutter extremely similar and I always wondered why React never uses MVVM pattern. Apart from that I am porting all my projects from SwiftUI MVVM to SwiftUI with less VM and finding that it saves a lot of time and effort and also helps me not fight the framework.

One example I gave was EnvironmentObject. When using MVVM it becomes hard to access EnvironmentObject inside a custom VM. You need to pass it down to the nested VM and it becomes really messy.

VMs also don't have access to FetchRequest, FocusState, GestureState etc.

As mentioned in the article, in some cases VM makes sense but in majority of the cases it is unnecessary. Few weeks ago MongoDB also held a session about MVVM in SwiftUI and reached the same conclusion that in most cases it is unnecessary since all the features of VM (binding) are already available in the View. The View in SwiftUI is essentially a View Model.