Kotlin-coroutines were used for blocking operations(fetching restaurants list from the file,..)

Added some nice animation for the search view in the actionbar

Used LiveData and ViewModels as well

Koin was used to glue the different components together in the application

Included some few number of unit tests as well.

I am using the MVVM architecture and some state machine concept on top of it. Every screen has a view, a model, and a ViewModel. The ViewModel contains a state that represents the properties of the View. This state will be emitted using LiveData to the observer(view).

The ViewModel state is represented using a simple kotlin data class with different fields.

I also use sealed classes to model some repetitive behaviors. Like, when fetching data in an asynchronous fashion, the usual states are Loading, Failed(with the failure), or Success(with the actual data).

Repository is the single source of truth that is used to fetch data(either from the restaurants file data source or from the local database)

Here is a gif demonstrating this super mini app:

I created a small animation for the search bar expansion and collapse.

Search behavior and animation:

NY articles listing and details