iOS 15: Introducing MVVM into your SwiftUI project - Bucket List SwiftUI Tutorial 11/12

[@shim2dawg]

Thank you for stating MVVM is a terrible name. I have always been confused by it and it's nice to be validated.

[@carlsmith358]

This video really improved my understanding of how to use MVVM in SwiftUI, along with the benefits it has.

[@acjazz01]

You've created a wrong connection between ViewModel and ContentView by putting the VM inside of an extension of the ContentView, and actually MVVM says that the ViewModel must be agnostic, as it can be used in any view.

[@HaraldSchubert]

Perfect explanation of MVVM and application to SwiftUI!

[@maple3226]

I'm having a warning when I'm declaring the viewModel variable saying "Expression requiring global actor 'MainActor' cannot appear in default-value expression of property '_viewModel'; this is an error in Swift 6". Is there a different approach to remove this warning?

[@JeffreyConcerto]

Paul, why is it better to save the data via documents directory here instead of using CoreData?

[@Ipat639]

I am struggling with binding viewModel's private(set) var string and ContentView's TextField, any idea?

[@igorsevtsenko655]

Hi. Could you make please video about VIPER with SwiftUI. Very interesting to watch how can we use protocols for modules connections and SwiftUI property wrappers

[@mykytakhlamov]

Thank for this video and your work! I have one question: How to proper test this ViewModel via UnitTesting?

[@jamesm.6874]

You are an excellent teacher, thank you so much!

[@rileybarabash221]

Since we're migrating our logic from structs into classes, doesn't this have a negative affect on performance?

[@obelix8477]

MVVM is not an acronym. Acronyms are pronounced like words. Think radar, ASCII, modem. MVVM is an abbreviation. Probably a greek or latin base somewhere in there. Also, if your fans are confused with "belts and braces" they may know braces as suspenders. This is an analogy for the parts that hold your program together. They keep the "pants up" so to speak. But this means using two ways to ensure your pants don't fall down.

[@prashank]

Ty Mr. Doggo

[@shotaworld]

Great video! Could you make a video about the redux pattern? For example, the store, actions, reducers and dispatch. Thanks!

[@tinkering.online2007]

I think someone should file a bug for that disappearing of the file contents :-) But XCode gets angry at me too sometimes.

[@RajeshSharmaIndia]

View model is an independent component which should not have any information regarding views, by creating the view model class inside the view extension we are encapsulating the view model class which is resulting in tight Coupling. What problem are you solving by creating the view model class inside view extension?

[@twostraws]

I’m struggling to find the inclination to reply to this level of rudeness, however I will at least say this: you’re facing a problem known as Chesterton’s Fence, and might want to take a little more time to think before posting these sorts of comments.

[@RajeshSharmaIndia]

With a very polite manner I am saying that I learned so many thing from your video and article , but at some point if I have doubt in something or I found its not a good way to do the thing, so its no harm that creater accept i did wrong or if you didn't ,so you had to explain the reason why you choose that approach. Lots of people followed you and apply the approach in projects . i hope you didn't find the truth is rude.

[@Ipat639]

it is not tight coupling, it is a reminder that this view model normally should be used with this view. And it is a class declaration not a concrete object, you can instantiate it and use where you want to use.