Building a UI with MVC/MVVM

Several known design patterns can help us build stable and complex screens, but MVC and MVVM are the most common and famous patterns.

Like many development areas, the topic of MVC and MVVM can be subject to personal preferences and opinions and may not always align with practical considerations. We always need to be careful with that, especially when interviewing for a job. Let me explain what I mean.

Solving different problems with MVC and MVVM

I want to go over several sentences I suggest avoiding when having a professional discussion with an interviewer or even colleagues:

• “My app is built with MVVM architecture.”
• “MVC is antique and a horrible architecture. I never use it.”
• “This is not how MVVM works. Let me show you.”

Remember what I’ve said multiple times throughout the book – we should avoid dichotomous thinking as developers. MVC and MVVM solve different problems...