Developing Clean Architecture Apps

Till 2017 Android developer's biggest worry was surviving configuration change but things changed in 2017 when Google introduced Architecture components.

Using architecture components even beginners can now easily implement "Clean Architecture" in their apps.

Transcript

1. DEVELOPING CLEAN ARCHITECTURE APPS ASHESH BHARADWAJ
2. Architecture is the “Jimmy Shergill” of the Software Industry src: imdb
3. Why is Software Architecture underrated/overlooked?
4. Because… life goes on even without a good architecture src: giphy
5. Bad architecture is like a deal with the Devil. src: giphy
6. Basics • High / Low level class: Lower, closer to the app boundary. Higher, less dependency and more abstract. • Business rules: It’s the logic WE CREATE to influence the behavior of the app. • Use case: An interaction with the app. • Layers: A virtual boundary to organize a group of classes. • Entity: The Entity objects hold the data used by the system and all the behaviour naturally coupled to this data - Ivar Jacobson.
7. Are we ready to talk Architecture? src: memegenerator
8. What is Software Architecture? • The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution – IEEE • Software architecture is the art of drawing lines that I call boundaries - Robert C. Martin a.k.a. Uncle Bob
9. 1. Dependency flows in one direction 2. Dependency Inversion Principle (DIP) src: cleancode
10. Dependency Inversion Principle High-level modules should not depend on low-level modules. Both should depend on abstractions. Abstractions should not depend on details. Details should depend on abstractions.
14. Code Organization By Layer By Feature By Module Layer + Feature
15. Benefits of Clean Architecture • Separation from UI • Separation from DB • Testing • Maintainability
16. MVC / MVP / MVVM are not Architecture src: tenor
17. • Domain layer missing • Dependency Inversion Principle not followed Google App Architecture
18. Android Developer Evolution src: kisspng
19. This needs to change… Architecture doesn’t require special technical knowledge • Android Architecture Components • Room • LiveData • ViewModel • Self-discipline • A little extra work which pays for itself
20. That’s it! Thank You linkedin.com/in/asheshb twitter.com/asheshbt medium.com/@asheshb Ashesh Bharadwaj