Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/alejandrolagosr/moviedb-android
MovieDB client example app 🍿
https://github.com/alejandrolagosr/moviedb-android
android coroutines coroutines-android jetpack jetpack-android kotlin kotlin-android mvvm mvvm-android mvvm-architecture navigation-architecture-component single-activity-pattern
Last synced: 5 days ago
JSON representation
MovieDB client example app 🍿
- Host: GitHub
- URL: https://github.com/alejandrolagosr/moviedb-android
- Owner: alejandrolagosr
- Created: 2021-06-09T01:26:26.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2021-06-29T15:42:10.000Z (over 3 years ago)
- Last Synced: 2024-08-21T00:28:30.723Z (3 months ago)
- Topics: android, coroutines, coroutines-android, jetpack, jetpack-android, kotlin, kotlin-android, mvvm, mvvm-android, mvvm-architecture, navigation-architecture-component, single-activity-pattern
- Language: Kotlin
- Homepage:
- Size: 282 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# MovieDB Example App 🍿
For this exercise I decided to use the Single Activity principle, additionally Clean Architecture as a pattern through modules, MVVM, Jetapck (view bindings, nav component, list adapter) so in the project structure it looks as follows:
- App: Everything related to the graphical interface such as Fragments, Activity, ViewModels, Adapters, ViewHolders
- Domain: Everything related to business logic, data conversions and connection with the data source
- Framework: Practically a domain extension, necessary for the use of Paging and its dependency with Android APIs
- Data: Data sources, endpoints
## Important Notes
* About the caching requirement for images: I delegated that behavior directly to Glide, so no implementation was necessary.
* It was also not necessary to create a custom RatingView component as the similar Material component is now stable.
## Gradle
Dependencies are centralized inside the [dependencies.gradle](buildsystem) file in the `buildsystem` folder. This provides convenient centralization. It will allow us to update any dependency in a single place without the necessity to go manually to each gradle file where is used to change it, avoiding possible conflicts between versions if someone forgets to update one of these dependencies.
## Clean Architecture
The objective of [**Clean Architecture**](https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html) is the separation of concerns. Using a layers architecture like this one, allow us to be more independent of frameworks and limit proper boundaries. It also provide more benefits as higher testability and the possibility to scale well.
The project will start growing keeping in mind this, for now we don't have many modules but instead we'll handle the layer by using packages referencing them as such.
## Third Party libraries used
- Glide: Image loading and caching
- Retrofit: HTTP Client
- Retrofit Gson Converter: GSON converter for JSON responses
- MockitoKotlin: Mockito for Kotlin unit testing
- Hamcrest: Matchers for unit testing, make it more readable and efficient
## Screenshots
| Movie Detail | Home |
| ----------- | ----------- |
|  |  |