MVVM vs MVP: what's the difference? 🤔

preview_player
Показать описание
#iOS #swift #softwaredeveloper #iosdeveloper

Thank you for watching this video 🙌

(affiliate link)

Рекомендации по теме
Комментарии
Автор

Did you find this explanation useful? Are you already using MVP in your apps? Let me know in the comments 🚀

v_pradeilles
Автор

Wish this video existed about 7-8 months ago. I had to do a take-home project specifically in MVP. Surprisingly I couldn't find any resource that pointed out this specific difference between MVVM and MVP. So my solution looked pretty much like MVVM. Needless to say, I didn't get the job 😅 But at least now I know! Thank you.

isurujn
Автор

MVP is just the delegate pattern but looks good.

donathmm
Автор

Brilliant explanation.

I would like to see your approach with Combine + URLSession Networking, MVVM architecture.

Note: ViewModel should not contain any business logic and not make directly Api call.

coolnext
Автор

Thanks for one more nice video ! It would be great if you access view object from presenter as abstract protocol object in MVP then testability of presenter would become easy. This is one of the difference between in mvp and mvvm I believe. vm don't have knowledge of view at all . It makes more testable . In Declarative coding mvvm is best choice I believe .

yogeshdeshmukh
Автор

Closure or Delegate can be used in either of MVVM or MVP, right? I feel the video didn't highlight the difference between them, please correct me if I stated this wrong.

nashtravelandlifestyle
Автор

Hi @Vincent that is an excellent explanation. Can you please explain how to decide Architecture for an app among the MVC, MVP, MVVM and VIPER

Rahul-jfkf
Автор

I'd be interested in how these patterns look in the SwiftUI world, if these even have a place with the more reactive/declarative underpinnings of SwiftUI. Are there patterns we should consider for SwiftUI as sometimes writing directly against the model in SwiftUI seems like a step backwards even thought the reactiveness takes away a lot of the boilerplate code to update UI in response to state etc.

bugmeister
Автор

The problem with all of these patterns is you lose the power of the responder chain. IMO it's best to stick with MVC and learn about child view controllers.

indiekiduk
Автор

Nice explanation! 
What do you prefer to use in a large and modularised app? 
What do u think about VIPER?

Thank you from Italy! :)

_faang
Автор

Nice explanation, but I still prefer MVVM.

byaruhaf
Автор

Williams Helen Anderson Angela Walker Jessica

JackQuincy-di
Автор

Thanks for the detailed information, can you please elaborate why viewModel.updateUI is in viewDidLoad and viewModel.fetchData is in viewWillAppear()?

zivzalzstein