This is a sample application 📱 built to demonstrate use of Clean Architecture tools. Dedicated to all Android Developers with ❤️.
You can Install and test latest app from below 👇
It simply loads repos and pull request list from GITHUB-API
- Modular approach followed
- It is heavily implemented by following standard clean architecture principle.
- Dependencies injection using dagger 2
- S.O.L.I.D principle followed for more understandable, flexible and maintainable.
Note: The use of clean architecture may seem over-complicated for this sample project. However, this allows us to keep the amount of boilerplate code to a minimum and also demonstrate the approach in a simpler form. Clean Architecture will not be appropriate for every project, so it is down to you to decide whether or not it fits your needs 🙂
- Kotlin - First class and official programming language for Android development.
- Rx-Java - For composing asynchronous and event-based programs by using observable sequences.
- Android Architecture Components - Collection of libraries that help you design robust, testable, and maintainable apps.
- Dagger 2 - Dependency Injection Framework
- Retrofit - A type-safe HTTP client for Android and Java.
- OkHttp - HTTP client that's efficient by default: HTTP/2 support allows all requests to the same host to share a socket
- Picasso - image loading framework for Android
- Gson - used to convert Java Objects into their JSON representation and vice versa.
- photo by: raywenderlich
Architecture means the overall design of the project. It's the organization of the code into classes or files or components or modules. And it's how all these groups of code relate to each other. The architecture defines where the application performs its core functionality and how that functionality interacts with things like the database and the user interface.
- Separation of code in different layers with assigned responsibilities making it easier for further modification.
- High level of abstraction
- Loose coupling between the code
- Testing of code is painless
Clean code always looks like it was written by someone who cares. - by Michael Feathers”
- Domain - Would execute business logic which is independent of any layer and is just a pure kotlin/java package with no android specific dependency.
- Data - Would dispense the required data for the application to the domain layer by implementing interface exposed by the domain.
- Presentation / framework - Would include both domain and data layer and is android specific which executes the UI logic.
It uses the all the components and class releated to Android Framework. It gets the data from presentation layer and shows on UI.
This module helps to list and manage all the dependencies of the app at one place. It has list of dependencies and versions of that dependencies.
The Data layer is our access point to external data layers and is used to fetch data from multiple sources (the cache and remote in our case).
The domain layer responsibility is to simply contain the UseCase instance used to retrieve data from the Data layer and pass it onto the Presentation layer.
This layer's responsibility is to handle the presentation of the User Interface, but at the same time knows nothing about the user interface itself. This layer has no dependence on the Android Framework, it is a pure Kotlin module. Each ViewModel class that is created implements the ViewModel class found within the Architecture components library. This ViewModel can then be used by the UI layer to communicate with UseCases and retrieve data.
The Remote layer handles all communications with remote sources, in our case it makes a simple API call using a Retrofit interface.
This app uses MVVM (Model View View-Model) architecture.
Please fork this repository and contribute back using pull requests.
Any contributions, large or small, major features, bug fixes, are welcomed and appreciated but will be thoroughly reviewed .
MIT License
Copyright (c) 2020 Happy Singh
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.```