There is no Java trace on this project, all parts have been developed using Kotlin and trying to use as much of it's features as possible.

No fragments have been used for this project, only one activity containing the list, since it didn't seem worth the overhead and anyway an activity was needed to contain the fragment.

The chosen pattern has been an MVVM approach, since Google it's really pushing for it with its architecture components.

LiveData has been chosen for this project since one of it's greatest feature is being "lifecycle aware" and therefore no need on keeping track of subscribing and unsubscribing.

Repository pattern is used to be able to quickly "swap" the datasource if necessary (even though now it only loads the content from a server API) and to make it as testable as possible.

Any class dependency is injected using dagger.

• Databinding: Used to easily deal with setting "properties" to the UI components (text, images, etc), for this list the ViewModel itself is passed, so if it were necessary to set properties to a new View of the list item could be easily done.
• Cardview: Used for each list item to give that "card" (as the library name suggests) look.
• RecyclerView: This View holds all items and display them, also it's "relatively" easy to append items for the lazy load.
• Constraintlayout: Used for each RecyclerView item to be able to have a strong looking UI (say goodbye to RelativeLayout and nested LinearLayouts).
• BaseRecyclerViewAdapter: Library to help deal with the RecyclerView lazy load and adapter itself.
• Glide: Library to help loading images from a url (even though it can do much more it's only used to deal with that here).

• JUnit: Very popular and useful library to test anything Java related.
• Espresso: Library to help with UI testing.
• MockitoKotlin: Similar library to mockito but made for Kotlin, since mockito doesn't always play well with Kotlin.
• MockWebserver: Great helper library to mock server responses.