Building Apps with Android Architecture Components

Course Overview
Hi everyone, my name is Omri Erez, and I'd like to welcome you to my Pluralsight course, build well-structured apps with Android Architecture Components. I've been a professional software engineer for over 10 years now focusing on the Android platform. Developing Android applications is a complex task and sometimes we forget about the structure and architecture of our code. In order to deliver an extendable, maintainable, and testable code base we have to think about the architecture of our application from the very first stage of our development. In this course, we are going to learn together how to write Android apps with a robust structure and we will utilize the various art components, which will result in architecture with well-defined layers. Specifically we will learn about the following subjects, the SOLID principles and commonly-used architectural patterns on Android, the ARCH, ViewModel, and lifecycle-aware components, the LiveData framework, the Room persistence solution, and how to test your architecture using various test types. By the end of this course you will know how to utilize the various ARCH components and how to produce Android apps with a robust architecture, which will be both extendable and testable. This course is specially designed for beginners. Before starting this course you should have basic knowledge of Android development and Android Studio. I hope you will join me on this exciting journey to learn about Android Architecture Components with build well-structured apps with Android architecture components course, here at Pluralsight.

Understanding Common Android Architectural Patterns
Welcome back everyone. After reviewing the basic concepts of object-oriented design and understanding why architecture is important, in this module we are going to talk about common Android architectural patterns. These patterns are being used every day across many Android applications and it's important for us to understand them. Before we start with the patterns I want to emphasize this term, the God Class, or a God Object. It's an object that contains a high number of components, the components logic is coupled, usually it's a very lengthy class, and we should avoid them at all costs. As we stated before, God Classes are very bad for our architecture, or you can even call them architectureless. In our demo our activity is a God Class because it contains all the logic of our application. All the components of our application are implemented within our activity, this is a very bad idea. Let's go ahead and talk about the architectural patterns we are going to review. The first one will be MVC, AKA model-view-controller. The second one would be the MVP pattern, AKA model-view-presenter. And last, but not least, we are going to talk about the MVVM, model-view-ViewModel.