Code architecture for Android apps

Talk given at Devfest Romania 2015. (http://devfest.ro)

Transcript

1. Code architecture for complex apps Catalin Morosan
2. In the beginning
3. In the beginning
4. After x client change requests
5. After x client change requests
6. Architecture
7. Architecture • achieve a high-level separation of concerns by layering
8. Architecture • achieve a high-level separation of concerns by layering • group of best practices in code
9. Architecture goals
10. Architecture goals • high maintainability
11. Architecture goals • high maintainability • low technical debt
12. Architecture goals • high maintainability • low technical debt • independent of frameworks ◦ UI, database, network
13. Architecture goals • high maintainability • low technical debt • independent of frameworks ◦ UI, database, network • testable ◦ loose coupling
14. Architecture goals • high maintainability • low technical debt • independent of frameworks ◦ UI, database, network • testable ◦ loose coupling • not over-engineered
15. Architectures
16. Architectures • Clean Architecture ◦ Uncle Bob
17. Architectures • Clean Architecture ◦ Uncle Bob • Hexagonal Architecture (Ports & Adapters) ◦ Alistair Cockburn
18. Architectures • Clean Architecture ◦ Uncle Bob • Hexagonal Architecture (Ports & Adapters) ◦ Alistair Cockburn • Flux Architecture ◦ Facebook
19. Architectures • Clean Architecture ◦ Uncle Bob • Hexagonal Architecture (Ports & Adapters) ◦ Alistair Cockburn • Flux Architecture ◦ Facebook • VIPER Architecture ◦ mutual mobile (iOS)
20. Design Patterns (Mini Architectures)
21. Design Patterns (Mini Architectures) • MVC ◦ Model View Controller
22. Design Patterns (Mini Architectures) • MVC ◦ Model View Controller • MVP ◦ Model View Presenter
23. Design Patterns (Mini Architectures) • MVC ◦ Model View Controller • MVP ◦ Model View Presenter • MVVM ◦ Model View ViewModel
24. Design Patterns (Mini Architectures) • MVC ◦ Model View Controller • MVP ◦ Model View Presenter • MVVM ◦ Model View ViewModel • Repository
25. The architecture proposal
57. Package by feature vs by layer
58. Package by feature vs by layer • Horizontal slicing ◦ activities, views, presenters
59. Package by feature vs by layer • Horizontal slicing ◦ activities, views, presenters • Vertical slicing ◦ per feature / user story
60. Sample project github.com/kaciula/archiman
64. Balance • abstract complexity • over-engineering VS • YAGNI • KISS
65. Thanks google.com/+CatalinMorosan