Комментарии:
So the controller didn't disappear when going from MVC to MVVM ... it's duties are just passed off to the the view and viewmodel? The controller orchestrates the interaction between view and model -- what is doing this orchestration in MVVM?
Ответитьthanks, man this helped me a lot
Ответитьperfect explanation, especially you mentioned the problem of MVC from the beginning of its evolution :)
ОтветитьOne of the best and cleanest explanation thanks
Ответитьthanks a lot. it's very nice video. can you please explain the other design pattern clean swift and VIPER?
ОтветитьWow, your explanation of those three patterns is amazing! Thank you so much! 👏🏼
ОтветитьHi,
I have seen MVP tutorials where some offload things like showing an alert over to the presenter. And in some tutorials, they advice against that practice and recommend keeping the presenter UI-agnostic and have it only handle business logic.
I know there is no silver bullet, 100% correct way to these things. But personally, what do you think is the better approach? Should the presenter have UI code in it or not?
Hi! I'm asking to all... What is the name app to make those workflow mockups? Looks amazing I would use it.
ОтветитьGreat , awesome presentation
ОтветитьOkay, then why none of them figures out where to put networking code ? They are basically 3 similar patterns that have exactly the same flaws ...
ОтветитьI thank you for your clear and simple explanation. Grrrrreat job! Not a second wasted on fluff just the good stuff!
ОтветитьHey Caio, thank you for all the tips. I was stuck in MVC (apple) and no matter how I was separating things, one layer was always doing too much as you've said. Now I'll have another paths to go :) Thanks mate. (PS: Você é brasileiro? Deu pra sentir pelo sotaque... Um abraço cara! :D)
ОтветитьThanks for the video, As you explain MVC, MVP MVVM and VIPER are UI Design Pattern then what is Arachtechtural Pattern in iOS?
ОтветитьYou have a new subscriber dude
ОтветитьGreat stuff, mate. Clear , concise and comprehensive! Kudos
ОтветитьThis is really great. Do you have an example of this, with all the layers you have (networking, routing, parsing, rendering..)?
ОтветитьGood explanation, thank you
Ответитьhi. Great video. thank you. please can you tell me what software you used to create your diagrams?
ОтветитьSo at the end MMVM is not solving anything that wasn't "working" on MVC just moved around, and as always the best scape is "you decide where you put it"
ОтветитьThank you very much. I would be interested how SwiftUI influences the selection of a UI pattern. In my option Apple released with SwiftUI a MVVM solution. So, in the next two years iOS 13 definitely is the default version on every iPhone. Therefore MVVM will be the new MVC. Would do you think?
ОтветитьBest tutorial on this topic I have found by far
Ответитьvery nice and concise explanation, thank you for the video!
Ответитьbusiness logic is good to have with a model in the case of MVVM? isn't should be with viewModel? Eg. Showing a specific date format based business requirement totally should be calculated by ViewModel not by the model. correct me if I am wrong.
ОтветитьThe best explanation ever. Direct, talking not only about the views, but included the other parts of the application as well (networking, parsing routing...), which most of other videos don't even mention about it, and very good and clear graphics. Well done mate. Thank you.
ОтветитьI'm wondering why after one year I'm finding your tutorials and website?! great content and descriptions.
Ответитьthe best explanation ever
ОтветитьVery nice video!!!!!!!!!!!!
At last, I finally understood these design patterns and the difference between MVC and MVVM clearly!!!!!!
Thank you so much!!!!!!!!
Thanks, I think this is one of the clearest tutorials on the web which explains these patterns and how are applied to the iOS platform. Really liked to see how the original MVC is different from the Apple implementation and how all those patterns are very similar between them :)
Ответитьsir,
please do collectionview inside tableview using mvc
Thank you, so many crappy tutorials out there that are poorly written or recorded. Yours was the best!
ОтветитьCould you add some example simple but representative public github example projects for these various architectures so we can connect the diagrams to what it looks like in code?
Ответитьwhat is the best in ios MVVM or MVP?
ОтветитьHello, thanks for this new video. One comment that I think should be added is to explain why people keep implementing MVVM though it looks like MVC+boilerplate - because VM doesn’t depend on UIKit and it is easier to test.
Ответить