Thanks for this

https://www.google.nl/search?q=tik+tok.home+page&client=ms-android-samsung&prmd=vin&source=lnms&tbm=isch&sa=X&ved=2ahUKEwiM7vnOhdbeAhVE6qQKHZE4B_YQ_AUoAnoECA0QAg&biw=360&bih=560#imgrc=b5UMBRiE1EOuVM like this image

Thanks for your fast reply. Ok good then, I never really use MVVM, but I like having a way out for dependency issues. It will fast become a nightmare if the application growth. By the way, excellent course again. I just miss one and I expect to quickly overcome this problem! : ) Big fan of your work!

I think adding UIKit to the Model is not a design tradeoff: it is a mistake, because it breaks the MVVM pattern.

Christophe, How did you create the cardViewModels array in the HomeController using this?

I am guessing he did something like this: let cardViewModels = [ CardViewModel.cardViewModel(fromUser: User(name: "Jane", age: 20, proffession: "Computer Science Student", imageName: "l1")), CardViewModel.cardViewModel(fromUser: User(name: "Xiomi", age: 23, proffession: "Data Scientist", imageName: "l2")) ]

@Tokyojogo

Hello Brian, First I would like to thank you for these well drafted codes. Secondly, I would like to ask you whether the below would match the concept of MVVM. Under CardViewModel, I included: static func userToCardViewModel(user: User) -> CardViewModel { let attributtesName: [NSAttributedString.Key: Any] = [ .font: UIFont.systemFont(ofSize: 34, weight: .heavy) ] let attributesAge: [NSAttributedString.Key: Any] = [ .font: UIFont.systemFont(ofSize: 24, weight: .regular) ] let attributesProfession: [NSAttributedString.Key: Any] = [ .font: UIFont.systemFont(ofSize: 20, weight: .regular) ] let attributedText = NSMutableAttributedString(string: "") attributedText .append(NSAttributedString(string: user.name, attributes: attributtesName)) attributedText.append(NSAttributedString(string: " \(user.age)", attributes: attributesAge)) attributedText.append(NSAttributedString(string: "\n \(user.profession)", attributes: attributesProfession)) return CardViewModel(imageName: user.imageName, attributedString: attributedText, textAlignment: .left) } Under Home controller, I included: fileprivate func setupDummyCards() { users.forEach { (user) in let cardViewModel = CardViewModel.userToCardViewModel(user: user) let cardView = CardView(frame: .zero) cardView.cardViewModel = cardViewModel cardsDeckView.addSubview(cardView) cardView.fillSuperview() } } Thanks

the video is showing but its like 3 times the width of the screen so the only way I can watch is if I click on full screen. I'm using firefox. Its weird because all the other pages are ok. just this one.

Also, why not setting all those properties from viewModel inside CardView? If you have a card with a lot of properties the code could get really messy.

You are absolutely right, the original Microsoft approach (from which this architectural pattern is derived) differs greatly from this approach. But I guess why Brian isn't following this is because it would add extra complexity to the course, because you need some kind of reactive bindings (i.e. two-way bindings), which makes it hard for beginners to understand because the whole app already has its own level of complexity and people came for Tinder and not MVVM. If you want to know more about MVVM, I guess Ray Wenderlich has some good articles, and there are many on medium. I've read Advanced App Architectures for iOS (RW), which provides a pretty good tutorial for really complex applications, you should check it out. Basically, the original MVVM pattern is structured as follows: The ViewModel owns the model and other services and the controller retains the View and the ViewModel, every time the Model changes this triggers an action in the ViewModel. This informs the controller that the view needs to be changed.

Thanks, for an answer, I was little confused.I look at course Advanced App Architectures for iOS (RW) and thinking abut get it, may be will do