[Android Advanced] Topic #2 - Architecture

A good software architecture allows the system to be easy to understand, to develop, to maintain and to implement.
The most important principle to follow is separation of concerns. It's a common mistake to write all your code in an Activity or a Fragment. These UI-based classes should only contain logic that handles UI and operating system interactions. By keeping these classes as lean as possible, you can avoid many lifecycle-related problems.

Together with you at a lecture, we will consider:

1. Introduction to Architecture as meaning

• History

• What problems we have in app development

• Architecture matters

• Solutions

2. Main principles

• Create app (maybe our own app for fundamentals) which violates good architecture

• Introduce SOLID (A brief overview)

• Introduce KISS, DRY, YAGNI (Optional)

• Fix app with those principles

3. Clean Architecture overview

• Explain main points

1. History and author of approach

2. Basic principles

3. Mention original structure and linear structure

• Layers and dependencies (how dependency go from one layer to another)

1. Layers and Dependency Rule

2. Transfer to linear structure

3. Description about layers and entities

4. Description of Domain layer (UseCase/Interactor, Entities)

5. Description of Data layer (Repository Impl, Gateaway)

6. Description of Presentation layer (Presenter/ViewModel, UI)

• Start rework app to separate on layers and introduce it one by one by putting all logic in different classes and ui logic leave in ui

• Introduce MVVM as a relationship between UI and logic

• New business requirement

• Develop new requirement

• Show design code, how to include it into current architecture

Info partner