A demonstration of MVVM pattern using the trending libraries of the android world and Android Architecture Components.
App is based on the Google TODO MVVM pattern, this pattern was choosed to make the business logic easily testable.
The styleguide used is the Google CodeStyle
##Some Notes
- I created a exclusive module exclusively to demonstrate a way to let the service be complete decoupled from the app. That helps when the service is the same in multiple front ends.
- Unit tests aren`t made in this project due to difficulties utilizing AndroidX components, if a sample of unit tests are needed i have a sample in another project. That repository have Unit and instrumentation tests using JUnit and Espresso.
-
Unit tests under test folder.
-
Instrumentation test under androidtests folder.
Las capas de la aplicación (por ejemplo capa de persistencia, vistas, red, negocio, etc) y qué clases pertenecen a
- R: Persistence are made using room and the parttern utilizing the RepositoryPattern under the MovieDbService module
All bussiness logic are under the viewModel classes
- R: Repository class decides if the data comes from remote or local datasource. ViewModels are responsibles to bussiness logic and View classes are responsible to show the data on the screen.
- R: Basically it consists in giving classes a single responsability, that make easier to change the dependencies, reduce coupling and encapsulate the roles of each class. In this project we have three separated major roles: Data, Bussiness logic and views.
- R: Low coupling, high coesion, a strong guideline and code as documentation.
- I would add genres and some more information to details screen, figure out why I was having problemas with room and Rxjava in mockito(Unit Tests) and add some Instrumentation tests.
- I would use android navigation components that is still in alpha
Copyright (c) GibranLyra 2018
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
See LICENSE.md