How to implement the MVVM architecture in Swift!

#iOS #swift #softwaredeveloper #iosdeveloper
Thank you for watching this video 🙌
Get the code 👉 bit.ly/3siaUnT
I use Ecamm Live to record my videos, check it out 👉 bit.ly/3n9CClf
(affiliate link)
➜ Leave a tip: www.buymeacoff...
➜ Website: www.swiftwithv...
➜ Twitter: / v_pradeilles
➜ GitHub: github.com/vin...
➜ LinkedIn: / vincentpradeilles

[@v_pradeilles]

Did you find this explanation useful? Are you planning on using MVVM in your apps? Let me know in the comments 🚀

[@hosseindastan6221]

it would be good to see also combine version.

[@v_pradeilles]

Request noted 📝

[@idanboadana3611]

Great video! I actually would love to see this implemented with Combine, and more Combine videos would be amazing :)

[@TheLeonardofs89]

This is very informative! It actually helped me in an interview!!! As a request, I would love to see some S.O.L.I.D. principles in Swift codings, if possible! Thank you so much and keep on with your great work!

[@pkc456]

Good video, some questions for you:
1. Why ViewModel inherit form NSObject?
2. Don't we need to use the main thread to display data?

[@v_pradeilles]

Good questions!
1. Force of habit. I don’t think you actually have to.
2. Very good point, I kept that part out, because it was a bit out of topic, but you definitely want to make sure that the UI is updated only on the main thread.

[@Iwasee]

Thanks a lot ! I really enjoyed your example, small amount of code is so much more better for understanding !

[@40tutur]

Thanks for the video !
Very simple, popular and useful pattern ! But i prefer to use MVI pattern, unidirectional data flow, single source of truth for the UI state ! For me it's a very interesting good evolution of MVVM pattern :)
That's just my opinion of course ;)

[@rohitdhawan02]

Yes Vincent, though already using MVVM.

[@robinandthedog]

Very well explained, merci beaucoup!

[@jebamoses3209]

Good Explanation👍🏻

[@garyash7607]

Good video. Myself, I'd consider formatting to a view responsibility

[@sdmf195]

Thank you so much :)

[@rev_kous9275]

Pourras-tu stp faire une vidéo avec la variante du MVVM, qu'est MVVM-C (Coordinator) ? Je trouve que c'est très important de savoir implémenter l'architecture MVVM avec les Coordinators.

[@v_pradeilles]

Je note l'idée !

[@cozybazaar]

Please do one about VIPER too 😍🙏🏻

[@developerios6096]

Hi vincent, easy to understand and interesting. A good old imperative approach, but i was wondering if we could implement a closure(in fetchData) to let us know when fetchData got the actual data. Tipically, we want our UI to be refreshed as soon as the new data is available. Would this solution be "too much reactive" ?

[@junaidkamoka4059]

Thanks

[@Kel_jellyfish]

I want to use my data for table view but outside the closure the array return nil. It's my first step with the MVVM pattern.

[@v_pradeilles]

For this use case, MVVM with closures can be indeed a bit clunky. You basically have two approaches:
1. the ViewModel stores the latest value of the array of data in a property (ideally with a public getter and a private setter).
2. you go for the MVP pattern, which makes it a bit easier to work with table views.

[@idembele]

Je ne comprends toujours pas. Je pense que je vais la regarder encore.. et encore.. et et encore ta vidéo... Merci Vincent

[@idembele]

je pense que c'est la closure de updateUI m'embrouille :D. Le newData (dans viewController.updateUI) c'est une sorte de property Observer? Est ce une sorte de didSet?

[@JLCodes]

What is the purpose of extending your ViewModel to NSObject?

[@v_pradeilles]

You don't really need it to conform to NSObject, I did it more by force of habit than anything else.

[@laurentk2033]

Hello Vincent, I'm new in iOS, for the moment I've been learning both UIKit and SwiftUI but wich should I learn more in depth? And if the answer is both wich one at first?
Greets from Belgium :)

[@v_pradeilles]

Let me redirect you to Paul Hudson's website, because he's written a great article on this very topic 👉 www.hackingwithswift.com/quick-start/swiftui/answering-the-big-question-should-you-learn-swiftui-uikit-or-both

[@yogeshdeshmukh1642]

great

[@Dragonrojo2555]

Why the ViewModel is an Nsobject?

[@v_pradeilles]

Force of habit, I don’t think it’s actually necessary

[@vm3172]

ALO BILL GATES TAO VENDENDO DIPLOMA EM SETE LAGOAS FORMEI SEM SABER INGLES E NEM SEI PROGRAMAR HAUAUHUHAUHAUH

[@zivzalzstein3776]

why 'viewModel.updateUI` is in the viewDidLoad and not viewWillAppear?

[@v_pradeilles]

Here the reason is that the closure will be the same for the entire lifetime of the view controller.
You could also set the closure in viewWillAppear and set it to nil in viewWillDisappear, if you don’t want the controller to be updated when it’s out of the screen.