Modern Android Architectures - MVVM MVP MVC - in Java (Udemy.com)

It is a good introduction to those architectures patterns. I liked how the teacher used 1 app and "rewrite" it to showcase how it can be implemented in each architecture. The reason I'm not giving 5 stars it is because I think only one example is too little. He could used more examples to show the difference between the architectures. I dont think it is necessary to rewrite another app from scratch, but at least showcase other examples.

Very good course and goes straight to the point!!! Looking forward to seeing this content from the author applied to Kotlin and Flutter in his future work. Who knows, perhaps, new courses on the same topic applied in these programming languages.

Super nice course ! Although the are already new versions of the libraries which are not compatible with the course, so would be great to add some small updates

The course really fulfilled my expectations to understand the different architectures that accompanied the evolution in the development of Android apps. Stefan always explains clearly and goes to the point. Thank you

The material is good, but there is outdate parts which caused lots of confusing errors. Specifically RxJava3. Using the correct dependencies. Retrofit's Adapter for rxj3 for example. As well as things like AndroidSchedulers, Disposable Observer, and Single. This led to lots of Googling instead of focusing on the architecture.

MVC: there are various way in which we can decouple the UI logic from the application. it was not explained properly. MVP: very short inrtroduction. MVVM: just show how where to put the code. Did not share any infromation about it underlying logic. The course is very basic and is suitable for beginners.

The course was awesome, i was looking for something like that, which includes all architectures. As an advise; maybe there can be little complex separate projects for all architectures in future. Greate job!

Really like that you start of with the diagram to explain the architecture concept first, then proceed to code all 3 architectures using the same code base. So can really see what's the different between all architectures.

Thank you so much, I really love this course, it's really easy for understanding, quickly apply and I learn fast refactor from MVC to MVP or MVP to MVVM... But I think this course must have one lesson about comparing each positive and negative on each architecture, let we can more clearly understand this.

This will get you to understand the basics of MVC, MVP, and MVVM. The only one I knew going in was the MVVM, now I am confident I know all three. However, MVVM lacks alot of supporting detail about why you would want to use it. My point is that a new student would never know what an observable actually does without mention of the lifecycle. It was made with the idea that when managing the variables using the lifecycle methods, race conditions are likely to happen unless programming it in a certain way, and also decoupling. Instead the live data was used like any variable and the only explanation was that it is an "observable."