PropertyApp is a sample Android application developed using Jetpack Compose and follows the Modern App Architecture, incorporating modern design principles and development practices to create a robust and maintainable codebase.
| Light | Dark | Loading and Error |
|---|---|---|
 |
 |
 |
 |
 |
 |
The app follows a well-defined and organised architecture to ensure scalability and maintainability. Key architectural principles include:
- Reactive and Layered
- Unidirectional Data Flow
- Flows
- Dependency Injection
The data layer plays a crucial role in exposing data to the rest of the app. It consists of two main components:
-
Property API (Remote Datasource): This component handles interactions with the remote data source and fetches property data.
-
Property Repository: Responsible for abstracting the data source implementation details from the domain layer, the Property Repository provides a clean interface to access property data within the app.
The domain layer encapsulates the business logic of the application, enhancing reusability and testability. It includes the getPropertiesUseCase, which is responsible for converting the data received from the API into a format that is more view-friendly. Additionally, it efficiently handles and emits success and error cases through appropriate flow data, ensuring a smooth data flow throughout the app.
The UI layer serves as the front-end of the application, consuming data from the domain layer. It consists of two main components:
- ViewModel: plays a central role in the UI layer, publishing data to be observed and consumed by the UI elements, following the UDF (unidirectional data flow) pattern.
- UI Elements: responsible for presenting the data to the users, and sending events/ user actions to the ViewModel.
The UI layer establishes a clear separation of concerns, with the ViewModel solely responsible for publishing data, while the UI elements interact with the ViewModel by sending events, forming a unidirectional data flow.
Dagger-Hilt
- Although Koin DI is more appropriate for an app of this size, Hilt is a subjective preference.
Retrofit
- It makes networking so much easier.
Moshi
- I think Moshi is a better JSON processor than Gson. Also, I’m more familiar with it.
Coil
- Image loading library that is light, fast, modern and easy to use (according to https://github.com/coil-kt/coil)
Accompanist Navigation with Compose
- Deprecated because all the functionalities will be in
androidx.navigation.compose(Still in Alpha release as of now).
Google Truth
- Personal preference purely due to readability and expressiveness.
