Android functional clean architecture

Clean architecture separates your project into well defined layers: data, domain and presentation.
It enables easy testability and keeps your design adaptable to change.
Nowadays developing in Kotlin using functional types we can make it even more concise and boilerplate-less while clearly demonstrating our intent.

Transcript

1. Android functional clean architecture Lukasz Kalnik grandcentrix, Köln
2. Reasons • Separation of concerns: data - business logic - presentation • High cohesion & loose coupling • Easy exchange of data sources and view dependency in presentation layer • This leads to easy testability • Code reuse
3. Clean architecture Presentation layer Android UI Framework (Activity/Fragment) Domain layer Data layer Android data sources - REST API, Bluetooth, Shared Prefs Library API layer Library consumer (Android app data layer) Android application Android library
4. Gateway SDK example • Gets/sends data to a gateway • Converts the data in use cases to domain model • Presentation layer = library API layer
5. Data layer
6. Data layer - REST API
7. Domain layer
8. Domain layer - use case factory
9. Domain layer - Either type
10. Domain layer - test setup
11. Domain layer - example test
12. Library API layer
13. Library API layer - interface definition
14. Library API - instance creation & dependency injection
15. Library API - implementation