Master Multi-Module Architecture for Android Development

Gone through 3 videos and they are all good. Well done!

This course is almost perfect from 0 to 100% my rate is 90% why? if you add flavors to the project will be the master class project.

I found a video on YouTube explaining how to create a module manually and thought it was great, so I decided to purchase the full course. I am currently on the ninth video, and overall, the course is good—you get the necessary information. However, there are some caveats. I often find myself pausing the videos to look up what the instructor is doing and why. The explanations focus more on the "how" rather than the "why," which makes it harder to follow along without additional research. Additionally, the videos could be broken down into smaller, more structured sections. For example, the instructor jumps from setting up a module to creating a custom plugin and then updates the .toml and Gradle files—without clearly explaining the purpose of each step. This back-and-forth approach can be confusing. A more effective structure might involve separate sections for different components. For instance, if setting up a network module requires creating a custom plugin first (because it is referenced in the .toml and Gradle files), it would be clearer to introduce and explain the custom plugin before moving on to Gradle configurations. Instead, the course moves between these steps in a way that feels disorganized. For future courses, I believe the instructor could improve the experience by: Beginning each video with clear objectives: What will we accomplish in this lesson? Explaining not just what to do, but why it needs to be done. Providing an overview of key files involved—for example, explaining what a .toml file is and how it interacts with build.gradle.kts. This issue is not unique to this course—many technical videos are structured similarly. Many instructors are experienced programmers but not necessarily trained educators, which can lead to assumptions about the viewer's prior knowledge. Key Areas for Improvement: Don’t assume viewers already understand the purpose of various plugins and libraries—explain them. Don’t assume knowledge of the relationships between .toml, Gradle, and plugin classes—clarify how they connect. Don’t assume background knowledge unless explicitly stated in the course prerequisites. This is not meant as a negative review. I appreciate the effort the author put into creating this course, and it provides a solid guide to working with modules. However, with a few structural improvements, it could be even more effective and accessible for learners.

It was understandable,and easy. Thank you :)